A.8.25 Technological
Secure development life cycle
Structured attributes from ISO/IEC 27002:2022 — control type · CIA properties · cybersecurity concept · operational capability · security domain. What do these mean?
Mapped NIST 800-53 r5 controls (25)
Our reading (mostly llm_verified) of how this ISO control and each NIST 800-53 control relate. Not an ISO or NIST product.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- SA-11partialcovers — A.8.25 requires security to be designed and implemented within the SDLC (including testing/evaluation activities), which addresses a slice of SA-11's post-design testing, assessment-plan, and evidence requirements, but leaves the bulk of SA-11's specific developer obligations, parameters, and ongoing assessment details uncovered.
- SA-15explicit mandateimplements — A.8.25 directly requires a secure SDLC that incorporates security into development processes, which SA-15 operationalizes by mandating a documented development process that explicitly addresses security/privacy requirements, standards, tools, and configuration management.
- SA-17domain mandateimplements — A.8.25 requires secure development practices including design-phase security architecture; SA-17 directly operationalizes that by mandating developer-produced security architecture consistent with the enterprise architecture.
- SA-3domain mandateimplements — Both controls establish a secure development life cycle that integrates security requirements, testing, and controls across all phases of system creation.
- SA-8domain mandateimplements — A.8.25's mandate to embed information security throughout the SDLC directly operationalizes the application of security engineering principles across the identical set of lifecycle phases that SA-8 names; the link is by shared subject domain rather than explicit citation of the principles themselves.
Aligned NIST CSF 2.0 outcomes (20)
NIST CSF 2.0 outcomes this ISO control aligns with — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- PR.PS-06fullcovers — The ISO control mandates embedding security requirements, testing, and developer training throughout the software development lifecycle, which directly fulfills the CSF outcome of integrating and monitoring secure development practices.
Related OWASP ASVS 5.0 requirements (14)
Application-security verification requirements (OWASP ASVS 5.0) this ISO control aligns with; links open the ASVS chapter. Our analysis (mostly llm_verified) — many ISO controls have no ASVS counterpart.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Related weaknesses / CWE (1311)
Weakness classes this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Mitigated MITRE ATT&CK techniques (382)
Adversary techniques (MITRE ATT&CK Enterprise) this ISO control helps mitigate; links open attack.mitre.org. Our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Prevented OWASP Web Top 10 (2025) risks (25)
OWASP Web Top 10 (2025) risk categories this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- A01partialblocks — A.8.25 mandates security requirements, checkpoints, secure coding, testing (incl. pen tests) and developer training in the SDLC, which prevents many Broken Access Control defects (e.g. missing checks, IDOR) when followed; it does not address all members such as CSRF or path traversal that sit outside its direct mechanisms.
- A02partialblocks — A.8.25 mandates security requirements, checkpoints, secure coding, testing and developer training in the SDLC, which directly prevents many classes of misconfiguration (e.g. weak defaults, exposed cloud settings) from being introduced during design and implementation; it does not reach post-deployment runtime configuration drift or incomplete hardening of already-deployed systems.
- A03partialblocks — A.8.25 explicitly requires secure SDLC practices (secure coding, security requirements, testing, developer training, secure repositories/version control) that reduce the chance of introducing vulnerable/outdated dependencies or insecure build practices, but does not guarantee their absence and leaves build-pipeline/signing-infrastructure failures largely untouched.
- A04partialblocks — A.8.25 mandates security requirements, checkpoints, secure coding guidelines, testing (including scans/pen tests) and developer training in the SDLC, which directly lowers the chance that absent/weak/misused cryptography is introduced; it does not itself implement or enforce cryptography so the effect is a genuine but minority slice of the class.
- A06partialblocks — A.8.25 mandates security requirements, checkpoints, secure design guidance and testing in the SDLC which directly targets design-level weaknesses, but leaves a large remainder (flawed business logic, missing controls chosen by architects, threat modeling gaps) that the clause's listed mechanisms do not close.
- A07partialblocks — A.8.25 mandates security requirements, checkpoints, secure coding, testing (including scans/pen tests) and developer training in the SDLC, which directly lowers the chance that authentication defects (weak flows, session mistakes, credential handling) are introduced; it does not guarantee their absence.
- A08partialblocks — A.8.25 mandates secure SDLC practices (secure requirements, checkpoints, testing, secure coding, version control, developer training) that directly reduce the chance of introducing code/data integrity defects such as unsigned updates or insecure deserialization during development.
- A10partialblocks — A.8.25 mandates security in the SDLC including secure coding, requirements, checkpoints, testing (scans/pen tests) and developer training, which directly lowers the chance of introducing error-handling defects that leak info, fail open or create inconsistent states.
Control IDs, short titles and the structured attribute table (control type, CIA properties, cybersecurity-concept, operational capability, security domain) are facts from ISO/IEC 27001:2022 Annex A / ISO/IEC 27002:2022. The full implementation guidance prose lives in ISO/IEC 27002:2022 — not reproduced here. Cross-walks to NIST 800-53, NIST CSF 2.0, OWASP ASVS, CWE, MITRE ATT&CK and OWASP Web Top 10 are our own analysis (mostly llm_verified), not an ISO, NIST, MITRE or OWASP product — how ours compare.