SEC11-BP04 Conduct code reviews
Require peer review on every code change with explicit security review criteria, and use CodeGuru Reviewer or similar to augment human review.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Code review checklist · Source control / CI pipeline
- Review approval logs · SIEM / log platform
governing documentDocuments that govern the control
- Branch protection rules · Policy repository / GRC workspace
- CodeGuru Reviewer findings · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- solo commits to main
- review checkboxes not enforced
- security criteria absent
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-BP03 Perform regular penetration testing · SEC11-BP05 Centralize services for packages and dependencies