A.8.27 Technological
Secure system architecture and engineering principles
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 (24)
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
- PL-8domain mandateimplements — PL-8 is the technical control that directly operationalizes the secure architecture and engineering principles required by A.8.27 within the system development life cycle.
- SA-17domain mandateimplements — A.8.27 directly requires secure architecture and engineering principles throughout the development life cycle, which sa-17 operationally enacts by mandating developer-produced security/privacy architecture and design specifications consistent with the organization's enterprise architecture.
- SA-8explicit mandateimplements — ISO A.8.27 mandates the establishment and application of security engineering principles across all architecture layers, directly encompassing the intent of SA-8 to embed security and privacy principles into system design and development.
Aligned NIST CSF 2.0 outcomes (19)
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.IR-01mostlycovers — The control's emphasis on embedding security architecture principles such as defense-in-depth, least privilege, and zero-trust directly produces the outcome of protecting networks and environments from unauthorized logical access.
- PR.PS-06domain mandateimplements — A.8.27 operationalizes secure design/engineering principles across the development life cycle, which directly gives effect to integrating and monitoring secure software development practices within PR.PS-06's domain (same-layer technical pair treated as implements per lane-B rule).
Related OWASP ASVS 5.0 requirements (15)
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).
Why these map — rationale
- V8.2.4mostlycovers — Requiring dynamic access control based on contextual attributes such as user identity, device posture and data classification satisfies the ASVS expectation that authorization adapt to environmental and contextual factors.
- V8.3.1mostlycovers — The ISO control's mandate to enforce authorization at a trusted service layer and integrate controls into the security architecture directly implements the ASVS requirement that authorization decisions must not rely on untrusted client-side enforcement.
Related weaknesses / CWE (1487)
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 (832)
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 (22)
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
- A06mostlyblocks — A.8.27 mandates establishing and applying security-by-design, defence-in-depth, least-privilege, fail-securely, zero-trust and other principles plus explicit design reviews against threats and attack patterns, which directly stops most classes of insecure design from being baked into the architecture.
- A01partialblocks — A.8.27 mandates security-by-design, least privilege, default-deny, zero-trust verification and secure architecture principles that directly stop many authorization failures (missing checks, IDOR, function-level bypasses), but does not reach path traversal or CSRF which sit outside the authorization-decision core of the category.
- A04partialblocks — A.8.27 mandates establishing and applying security engineering principles (including security by design, defence in depth, least privilege, zero-trust verification, end-to-end encryption of requests, and hardening) that directly address the design and implementation gaps causing absent/weak/misused cryptography for sensitive data.
- A05partialblocks — A.8.27 mandates security-by-design, defence-in-depth, least-privilege, distrust-input, fail-securely and explicit data validation/sanitisation principles that, when applied during architecture and engineering, stop untrusted data from reaching an interpreter unneutralised; the coverage is only a slice because the clause is a process that depends on how rigorously those principles are followed in each project, and it does not itself insert the neutralisation code.
- A07partialblocks — A.8.27 mandates security-by-design principles (least privilege, default deny, distrust external input, secure session control, authentication techniques, zero-trust verification) that directly block many authentication-failure defects when applied in the SDLC; it does not guarantee complete or correct implementation of those principles across all entry points, flows or supplier code, leaving a genuine residual slice.
- A08partialblocks — A.8.27 mandates security-by-design, defence-in-depth, least privilege, fail-securely, distrust-external-input, hardening, and explicit design reviews that surface integrity gaps; these directly block many root causes of unsigned updates, insecure deserialization and CI/CD tampering, but the clause is a process that still depends on implementation rigour and does not reach every member (e.g. supply-chain signing of third-party binaries).
- A10partialblocks — A.8.27 mandates security-by-design, fail-securely, defence-in-depth, least-privilege, security-oriented design reviews and hardening that directly target fail-open behaviour, inconsistent states and information leakage in error paths; this prevents a genuine slice of the class but leaves real remainder (e.g. application-specific logic flaws, runtime exception paths not caught in design review, outsourced code whose error handling deviates from the mandated principles).
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.