- Home
- Capabilities
- Code Sast Advanced
Advanced SAST Integration
Quick Reference
What & Why
Definition
100% of PRs scanned with SAST (Semgrep, SonarQube) blocking >= MEDIUM issues, custom rules for org-specific patterns.
Business Value
Detects security vulnerabilities 10x earlier (development vs production) and reduces critical security findings by 80% through shift-left security scanning Achieving 100% PRs scanned, MEDIUM+ blocks is a key milestone toward this goal.
Context
This capability is part of the Acceleration milestone's focus on scale automation, embed compliance, improve speed & reliability. Essential for teams targeting CFR, LT improvements.
Success Criteria
Target
100% PRs scanned, MEDIUM+ blocks
Measurement
SAST scan execution rate + block rate
Evidence
- SAST config with custom rules
- Scan result dashboards
- False positive tracking
In Practice
Real-World Implementation
Teams run Semgrep with org-custom rules: detect hardcoded secrets, insecure deserialization, SQL injection. MEDIUM+ findings block merge.
Concrete Example
Implementation Guide
Implementation Steps
Follow the measurement approach: SAST scan execution rate + block rate
For detailed step-by-step guidance, refer to the Secure Code & Advanced Review Implementation Kit.
Resources
Implementation Kit
Secure Code & Advanced Review KitTemplates
Browse all templatesRelated Resources
View learning pathsRelated Capabilities
Prerequisites
Implement these first
Enables
What this unlocks
Complementary
Often adopted together, from the Secure Code & Advanced Review 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 Acceleration milestone. Individual timelines vary based on team size and existing practices.