PW.8.1 Executable Testing for Security
Test executable software to detect vulnerabilities using dynamic application security testing, fuzz testing, and penetration testing on a defined cadence. Tie test scope to risk and feature changes.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- DAST integration in CI or scheduled scans · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Annual penetration test reports · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Fuzz testing harnesses for critical parsers · Document repository
- Remediation tracker tied to test findings · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- DAST run only against pre production with no realistic data
- no fuzz testing despite parsing untrusted input
- penetration test findings tracked separately from product backlog
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 sheetPW.7.2 Perform Code Review and Analysis · PW.8.2 Execute Security Testing