Labels
Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 3,714
-
InfraSecReestimatedGitLab.comThis is used by the InfraSec team when an issue is estimated wrong. `InfraSecEffort` label should be updated and this label should be added.
-
InfraSecbacklogGitLab.com / GitLab Security Division / Security Operations Department
-
InfraSecmisconfigurationGitLab.com / GitLab Security Division / Security Operations DepartmentFor security misconfigurations (e.g., overly-permissive scopes, etc.)
-
InfraSecmisconfigurationGitLab.comFor security misconfigurations (e.g., overly-permissive scopes, etc.)
-
InfraSecon-holdGitLab.com / GitLab Security Division / Security Operations Department
-
InfraSecprioritisedGitLab.com / GitLab Security Division / Security Operations Department
-
InfraSecthis-quarterGitLab.com / GitLab Security Division / Security Operations Department
-
InfraSecunsupported-versionGitLab.com / GitLab Security Division / Security Operations DepartmentFor outdated components (e.g., GKE) without a known owner
-
InfraSecvulnerabilityGitLab.com / GitLab Security Division / Security Operations DepartmentFor vulnerabilities whose mitigation is owned by InfraSec
-
InfraSecEffortLargeGitLab.comThis is used to track InfraSec effort when the estimated effort is around 1-2 weeks.
-
InfraSecEffortMediumGitLab.comThis is used to track InfraSec effort when the estimated effort is more than 2 days but less than a week.
-
InfraSecEffortSmallGitLab.comThis is used to track InfraSec effort when the estimated effort is 1-2 days.
-
InfraSecEffortToo LargeGitLab.comThis is used to track InfraSec effort when the estimated effort is more than 2 weeks. This needs to be broken down into smaller issues or promoted to an epic.
-
InfraSecEffortTrivialGitLab.comThis is used to track InfraSec effort when the estimated effort is less than 1 day.