When to use this
Use this checklist to verify code against the applicable secure coding standard.
Related controls
Checklist
- Applicable coding standard identified.
- Developer knows the applicable standard.
- Automated checks completed.
- Manual review completed where required.
- Secrets scanning completed.
- Dependency risks reviewed.
- High-risk functions/patterns checked.
- Findings are risk-rated.
- Exceptions are documented.
Review record
| Component | Standard | Reviewer | Tool evidence | Findings | Action owner | Status |
|---|---|---|---|---|---|---|
| TBD | TBD | TBD | TBD | TBD | TBD | TBD |
- Template
- Iso27001
- Technological controls
- Secure coding
Note Metadata
Aliases: Secure Coding Review Checklist
Source: 90 Templates/Secure Coding Compliance Review Checklist.md
Related Notes
- A.8.28 Audit Evidence Pack
- ISO 27001 A.8.28 - Secure Coding
- A.8 Technological Controls MOC
- A.8 Technological Controls Implementation Guide
- A.8 Technological Controls Audit Guide
- A.8 Technological Controls Implementation Audit Risk Mapping
- A.8.28 Audit Checklist
- Secure Code Review Record
- Secure Coding Standard
- Templates MOC