DS-5 Integrate dynamic application security testing into DevOps pipeline
Integrate dynamic application security testing into the delivery workflow as a gating control, so results can prevent vulnerable builds reaching production.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Gate configuration and threshold · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Finding remediation records · Document repository
governing documentDocuments that govern the control
- Dynamic testing tool and the environment it runs against · Policy repository / GRC workspace
- Coverage across externally reachable applications · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- dynamic testing run manually before major releases only
- tests point at a stub environment unrepresentative of production
- authenticated paths never tested
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-4 Integrate static application security testing into DevOps pipeline · DS-6 Enforce security of workload throughout DevOps lifecycle