A.8.28 Secure coding
Apply secure coding principles to software development.
15
artefacts
3
held by a system
5
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
- Sonarqube scan report · Vulnerability scanner / patch tooling
- Automated security test summary · SIEM / log platform
- Vulnerability ticket log · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Training attendance sheet · HR system / LMS
- Code review tracker jira · SIEM / log platform
- Peer review comments.zip · SIEM / log platform
- Review signoff checklist · SIEM / log platform
- Patch deployment record · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Company secure coding policy · Policy repository / GRC workspace
- Secure coding guidelines v2 · Policy repository / GRC workspace
- Policy approval minutes · Policy repository / GRC workspace
- Secure coding course certificate · HR system / LMS
- Training materials secure coding.pptx · HR system / LMS
- Dependency check report · Policy repository / GRC workspace
- Remediation verification report · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 3 system-held artefacts 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
- inconsistent application of coding standards
- lack of documented review evidence
- reliance on manual testing only
- missing tracking of remediation actions
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 sheetA.8.27 Secure system architecture and engineering principles · A.8.29 Security testing in development and acceptance