← ISO 27001 · A.8 — Technological
A.8.25 — Secure development life cycle
high
sdlcsecure-development
Requirement
Rules for the secure development of software and systems shall be established and applied.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Required element 1 — any one of
secure developmentsdlcdevelopment lifecyclesecure coding
Supporting terms — specificity signals
threat modelcode reviewsastdastdependency scanowasptrainingbranch protection
Contradiction markers
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
no code review
no security testing
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| PCI DSS 4.0.1 | 6.2 | Bespoke and custom software is developed securely | secure-development sdlc |
| GLBA | 314.4(c)(4) | Secure development and assessment of applications | secure-development sdlc |
| NIST CSF 2.0 | PR.PS-06 | Secure software development practices are integrated | sdlc secure-development |
| GDPR | Art.25 | Data protection by design and by default | sdlc |
| SOC 2 | CC8.1 | Authorised change management | sdlc |
| PCI DSS 4.0.1 | 6.4.3 | Payment page scripts are authorised, inventoried and integrity-checked | secure-development |
| NDPA 2023 | s.24(2)-(3) | Technical and organisational measures, accountability and privacy by design | sdlc |