A.8.26 Technological
Application security requirements
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 (23)
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-4domain mandateimplements — A.8.26's mandate to identify/address all security requirements when acquiring applications directly operationalizes the inclusion of those exact security/functional/assurance requirements in acquisition contracts that SA-4 requires
- SA-8domain mandateimplements — A.8.26's governance mandate to identify/address security requirements when developing/acquiring applications directly operationalizes the application of security engineering principles throughout the SDLC that sa-8 names, within the shared engineering domain (but without naming the specific principles).
Aligned NIST CSF 2.0 outcomes (22)
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).
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
- V14.1.1fullcovers — Requiring classification of information processed by the application and the associated protection levels satisfies the ASVS demand for documented identification and classification of all sensitive data into protection tiers.
- V2.1.1fullcovers — The ISO requirement to identify and document input validation rules and business-process expectations directly satisfies the ASVS mandate that application documentation define how data items are validated against expected schemas and business rules.
- V8.1.1fullcovers — Defining segregation-of-access and authorization rules for data and functions in the ISO control meets the ASVS requirement that authorization documentation explicitly state function-level and data-specific access restrictions based on consumer permissions.
- V6.1.1mostlycovers — Specifying authentication-related trust levels and controls in the application security requirements fulfills the ASVS need for documented rate-limiting, anti-automation, and adaptive-response measures that protect authentication functions.
Related weaknesses / CWE (1598)
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 (629)
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.26 requires identifying and specifying access-related requirements (segregation of access, levels of access to data/functions, authorization processes) that directly target the authorization-decision slice of A01; this is genuine but bounded, as the control does not address path traversal, CSRF, IDOR implementation flaws, or missing function-level checks once requirements are set.
- A02partialblocks — A.8.26 mandates identifying and specifying security requirements (including input validation, access segregation, resilience against injections/buffer overflows, output controls, encryption, and secure defaults for transactional/payment apps) that directly target many misconfiguration vectors when followed in development/acquisition; however, it is a requirements-gathering process whose effect depends on later implementation rigor, leaving residual gaps in runtime hardening, cloud settings, and incomplete enforcement.
- A04partialblocks — A.8.26 explicitly requires identifying and specifying requirements for encryption, protection of data in transit/at rest, input validation against injection, and use of cryptography where applicable, which directly prevents many (but not all) cryptographic failures when followed in development.
- A05partialblocks — A.8.26 explicitly lists identifying requirements for resilience against SQL injections, input validation, output controls, and related protections derived from risk assessment, which directly prevents injection flaws when those requirements are met; however, it only sets requirements rather than enforcing their implementation, leaving a substantial remainder of the broad A05 class (e.g., many template, LDAP, and command-injection variants) unaddressed.
- A06partialblocks — A.8.26 mandates identifying and specifying security requirements (including resilience against SQLi/buffer overflows, input validation, access segregation, crypto use, and other design-level protections) that directly address many root causes of insecure design when followed; however, it is a process of requirements identification rather than a guarantee that the resulting design will be free of all architectural weaknesses.
- A07partialblocks — A.8.26 mandates identification and specification of application security requirements (including authentication, identity trust, access segregation, input validation, and resilience against attacks), which when followed prevents many classes of authentication failures; however, it is a requirements-setting/governance control whose effect depends on downstream implementation rigor, leaving residual defects possible.
- A08partialblocks — A.8.26 requires identifying and specifying integrity-related requirements (e.g. input validation, output controls, integrity checks, non-repudiation, hashing/digital signatures, secure storage outside public environments) that directly target many software/data integrity failures when followed in development or acquisition.
- A10partialblocks — A.8.26 explicitly lists error message handling, input validation, resilience against attacks (incl. SQLi and buffer overflows), and several integrity/non-repudiation requirements that directly block classes of exceptional-condition weaknesses before they are coded; the control is a requirements-gathering process rather than an implementation mandate, so coverage is a genuine but incomplete slice of the broad A10 category.
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.