6.2.3 Custom software reviewed prior to production
Bespoke and custom software is reviewed prior to release into production or to customers to identify and correct potential coding vulnerabilities, by knowledgeable individuals other than the originating developer using b
5
artefacts
1
held by a system
2
at each review
hard
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
- SAST scan results per release · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Pull request review evidence with reviewer name · Source control / CI pipeline
- Code review checklist · Source control / CI pipeline
governing documentDocuments that govern the control
- Issue tracker showing remediation · Policy repository / GRC workspace
- Approval gate before deployment · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Vulnerability scanner / patch tooling on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Self-approval of pull requests
- SAST not blocking on findings
- No manual review evidence
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 sheet6.2.2 Software development personnel working on bespoke and custom software are trained at least once every 12 months as follows: • On software security relevant to their job function and development languages. • Including secure · 6.2.3.1 Code review findings corrected