SEC11-BP02 Automate testing throughout the development and release lifecycle
Embed SAST, SCA, IaC scanning, container image scanning and DAST into CI CD pipelines so vulnerabilities are caught and blocked before deployment.
4
artefacts
1
held by a system
0
at each review
moderate
to go live
Source control / CI pipeline
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Pipeline configuration with security gates · Source control / CI pipeline
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Scanner findings dashboards · Policy repository / GRC workspace
- Build failure on critical findings policy · Policy repository / GRC workspace
- Exception process · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Source control / CI pipeline); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- scans run but do not block
- no IaC scanning
- container images deployed without scan
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetSEC11-BP01 Train for application security · SEC11-BP03 Perform regular penetration testing