PW.7.1 Code Review
Review the human readable source code to identify vulnerabilities. Use a combination of manual code review and automated static analysis tools tuned to the language and framework.
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
- Metrics on findings closed per release · Source control / CI pipeline
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Code review policy · Policy repository / GRC workspace
- Static analysis tool inventory with tuning notes · Policy repository / GRC workspace
- False positive triage process · Policy repository / GRC workspace
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
- static analysis runs but findings are never triaged
- code review approval limited to functional concerns
- false positive rate so high that engineers ignore reports
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.6.2 Configure Build Tool Security Features · PW.7.2 Perform Code Review and Analysis