A.5.37 Organizational
Documented operating procedures
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 (20)
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
- AU-2impliedgoverns — A.5.37's requirement to document operating procedures for secure operation of facilities directly implies that the procedures must cover how event logging is identified, coordinated, and specified per au-2
- CM-2domain mandategoverns — A.5.37's mandate for documented operating procedures directly encompasses the requirement to develop, document, and maintain baseline configurations as a core operational procedure for secure system operation.
- CM-3domain mandategoverns — A.5.37's requirement for documented operating procedures directly encompasses the procedural domain of determining, reviewing, documenting, and implementing configuration changes, which is the core of CM-3.
- CM-6domain mandategoverns — A.5.37's requirement to document operating procedures directly supplies the governance layer that mandates establishing, documenting, and enforcing secure/restrictive configuration baselines as named in CM-6
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
- ID.IM-03impliedgoverns — A.5.37 mandates documented operating procedures whose execution supplies the operational data from which ID.IM-03 improvements are identified; the governance link is present by subject-area membership in operational processes but the control does not name improvement identification.
- ID.IM-03impliedimplements — A.5.37's documented operating procedures give operational effect to the improvements-from-execution outcome in ID.IM-03 within the shared operational-processes domain, but without either naming the other
- PR.PS-01domain mandategoverns — The ISO control requires documented, authorized, and consistently applied procedures for secure system installation, configuration, maintenance, and error handling, which directly fulfills the CSF outcome of establishing and applying configuration management practices.
Related OWASP ASVS 5.0 requirements (10)
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 (3242)
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).
Why these map — rationale
- CWE-1112mostlyblocks — Documented operating procedures directly require complete specification of program execution mechanisms.
- CWE-1118partialblocks — Documented operating procedures must describe error handling and exception processing.
- CWE-276partialprevents — A.5.37 mandates documented operating procedures that explicitly include 'secure installation and configuration of systems,' so a well-implemented procedure specifying correct file permissions during installation prevents many instances of CWE-276; however, the procedures are fallible human practice, and many observed instances arise from vendor installer defaults the organization's procedure does not reach, leaving a nameable remainder — the same practice-not-mechanism boundary that graded A.8.28 partial.
Mitigated MITRE ATT&CK techniques (467)
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 (3)
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.