Secrets Detection
Quick Reference
What & Why
Definition
>= 95% of commits scanned for leaked secrets (API keys, passwords) pre-commit and in CI.
Business Value
Reduces manual build time from 2 hours to 10 minutes and enables 3-5x more frequent integration testing through automated pipeline execution Achieving >= 95% commits scanned for secrets is a key milestone toward this goal.
Context
This capability is part of the Foundation milestone's focus on establish baseline practices (testable, releasable, monitorable). Essential for teams targeting DF, LT improvements.
Success Criteria
>= 95% commits scanned for secrets
Measurement
Secret scan execution rate + leak detection count
Evidence
- git-secrets or gitleaks config
- Pre-commit hook setup
- Secret leak incidents (should be 0)
In Practice
Real-World Implementation
Developers install pre-commit hook running gitleaks. CI also scans commits. Detected secrets block commit and trigger alert.
Concrete Example
Implementation Guide
Implementation Steps
Follow the measurement approach: Secret scan execution rate + leak detection count
For detailed step-by-step guidance, refer to the CI/CD & Build Automation Implementation Kit.
Resources
Implementation Kit
CI/CD & Build Automation KitTemplates
Browse all templatesRelated Resources
View learning pathsRelated Capabilities
Enables
What this unlocks
Complementary
Often adopted together, from the CI/CD & Build Automation epic
Troubleshooting & FAQs
Common Issues
Issue: Target metric not improving
Solution: Verify measurement is accurate, check if prerequisites are fully implemented, review evidence artifacts for completeness
Issue: Team resistance to adoption
Solution: Start with pilot team, demonstrate value with metrics, provide training and support during transition
Issue: Inconsistent implementation across teams
Solution: Create shared templates and guidelines, establish regular sync meetings, use automation to enforce standards
Frequently Asked Questions
Can we implement this before completing prerequisites?
While possible, it's not recommended. Prerequisites ensure foundational practices are in place, making this capability more effective and easier to adopt.
How long does implementation typically take?
Most capabilities can be implemented within 90 days when tackled as part of the Foundation milestone. Individual timelines vary based on team size and existing practices.