ISO 27001 Annex A 8.28: Secure coding

What auditors look for

Auditors check that 8.28 is either justified as not applicable in your Statement of Applicability or implemented and working. Typical evidence includes:

• Secure coding standard
• Code review records
• SAST and dependency scan results

How to implement 8.28 in practice

1. Base standards on OWASP guidance
2. Require peer review for changes
3. Fix high findings before release
4. Name an owner for 8.28, decide how often it runs and file evidence each time, so the control is audit-ready all year.

Recording 8.28 in the Statement of Applicability

List 8.28 with whether it applies, the reason (usually the risks it treats or a legal or contractual requirement), its implementation status and where the evidence lives. If you exclude it, explain why none of your risks or obligations require it.

Free resources

• ISO 27001 and GDPR readiness assessment
• 10 steps to implement ISO 27001
• Remote ISO 27001 consultant

More technological controls

• 8.24 Use of cryptography
• 8.25 Secure development life cycle
• 8.26 Application security requirements
• 8.27 Secure system architecture and engineering principles
• 8.29 Security testing in development and acceptance
• 8.30 Outsourced development
• 8.31 Separation of development, test and production environments
• 8.32 Change management