DS-4 Integrate static application security testing into DevOps pipeline
Integrate static application security testing into the delivery workflow as a gating control, so results can block vulnerable code from being committed, built or deployed.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Static analysis tool integrated in the pipeline · SIEM / log platform
periodic reviewEvidence produced at each review
- Finding triage and suppression records with justification · SIEM / log platform
governing documentDocuments that govern the control
- Gate thresholds and the action taken when exceeded · Policy repository / GRC workspace
- Coverage across repositories in scope · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- scanning runs but never blocks a build
- findings suppressed in bulk to clear the backlog
- only the main repository scanned
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 sheetDS-3 Secure DevOps infrastructure · DS-5 Integrate dynamic application security testing into DevOps pipeline