A.5.31 Organizational
Legal, statutory, regulatory and contractual 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 (30)
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-4partialcovers — A.5.31 addresses identifying and ensuring compliance with all external requirements (including those flowing into contracts), which covers a slice of sa-4's mandate to explicitly include security/privacy functional, assurance, and control requirements in acquisition documents, but leaves the bulk of sa-4's acquisition-process mechanics, solicitation, and evaluation activities untouched.
- CA-6domain mandategoverns — A.5.31's governance objective of ensuring compliance with all legal/statutory/regulatory/contractual requirements directly includes the RMF authorization process (CA-6) as a core regulatory compliance control within the security authorization domain.
- SC-12domain mandategoverns — A.5.31's governance mandate for compliance with all legal/statutory/regulatory/contractual requirements directly encompasses the subject of cryptographic key management requirements (a regulatory and contractual domain), without naming the specific control.
Aligned NIST CSF 2.0 outcomes (18)
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
- GV.OC-03fullcovers — The ISO control's explicit mandate to identify, document, and maintain compliance with all legal, regulatory, and contractual cybersecurity obligations directly fulfills the CSF outcome of understanding and addressing those same requirements.
- GV.PO-01partialcovers — A.5.31 addresses the slice of policies and processes needed to identify and comply with external legal/regulatory/contractual obligations (including those that may drive cybersecurity policy), but the bulk of GV.PO-01's requirements around organizational context, internal strategy, risk priorities, communication, and enforcement sit outside that compliance focus.
- GV.RM-03impliedgoverns — GV.RM-03 names an enterprise risk management outcome that must incorporate cybersecurity activities; A.5.31's mandate to identify and comply with all legal/regulatory/contractual requirements (which explicitly include risk-management obligations in most jurisdictions) reaches this outcome through subject-area membership rather than by naming enterprise risk integration.
Related OWASP ASVS 5.0 requirements (6)
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 (1)
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 (434)
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 (2)
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).
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.