How to transform compliance observation management with GitLab
Jul 24, 2025Madeline Lake

Summary
This post details how the GitLab Security Team uses GitLab issues and issue boards to manage compliance observations, transforming them into actionable work items. It outlines the observation lifecycle (Identification, Validation, In-progress, Remediated, Resolution), the use of labels for organization (workflow, department, risk severity, system, program), and the creation of various issue boards for visualization. It also highlights the use of the triage bot for automation of issue hygiene and the key metrics used to measure success, such as resolution efficiency, risk assessment, and compliance readiness. Advanced strategies like integrating with security tools and applying predictive analytics are also discussed.
More from the Bug Triage and Reporting trail
- Shai-Hulud copycat campaign targets Python developers through PyPI typosquatting
- Manage vulnerability noise at scale with auto-dismiss policies
- Self-service security alert handling with GitLab's UAM
- How GitLab measures Red Team impact: The adoption rate metric
- Introducing GitLab Advanced Vulnerability Tracking