How GitLab measures Red Team impact: The adoption rate metric
Mar 5, 2025Chris Moberly

Summary
Introduces a new metric for measuring Red Team impact: the adoption rate of recommendations. Details the implementation using GitLab issues, labels for classification (RTRec::Detection, RTRec::Control, RTRec::Process) and lifecycle tracking (RecOutcome::UnderReview, RecOutcome::InProgress, RecOutcome::Backlogged, RecOutcome::Blocked, RecOutcome::Adopted, RecOutcome::PartiallyAdopted, RecOutcome::NotAdopted). Leverages GitLab Query Language (GLQL) to create dynamic dashboards for monitoring recommendation status and trends. Discusses lessons learned regarding early metric implementation and cross-team collaboration.
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
- How to transform compliance observation management with GitLab
- Self-service security alert handling with GitLab's UAM
- Introducing GitLab Advanced Vulnerability Tracking