A.5.36 Organizational
Compliance with policies, rules and standards for information security
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 (15)
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).
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).
Related OWASP ASVS 5.0 requirements (5)
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 (3236)
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-263partialfinds — A.5.36's compliance review process checks whether configurations match the organization's security policies and standards, so a password aging setting that deviates from a stated policy (e.g., policy says 90 days, system set to 5 years) is surfaced as non-compliance and recorded; however, the review is periodic and bounded by which systems and which policy items are in scope, and instances where the policy itself permits an excessively long expiration are not flagged because there is no standard to deviate from.
- CWE-284partialfinds — Periodic compliance reviews and corrective-action tracking detect and close gaps where access-control rules are not enforced, reducing the window in which improper access control can be exploited.
- CWE-695partialfinds — Compliance monitoring verifies adherence to coding rules but does not prevent the weakness itself.
Mitigated MITRE ATT&CK techniques (3341)
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).
Why these map — rationale
- T1578.003mostlyresponds — A.5.36 requires identifying non-compliance (including via automated tools), determining causes, implementing corrective actions, verifying effectiveness, recording results, and timely completion — which directly maps to containment/eradication response once the deletion technique has run and left detectable non-compliance or evidence gaps on IaaS platforms.
- T1685mostlyresponds — A.5.36 requires managers to detect non-compliance via reviews (including of security tools and mechanisms), identify causes, implement corrective actions, verify effectiveness, record results, and ensure timely remediation — directly addressing an in-flight or realized T1685 instance by containing/eradicating the tampering and restoring defensive capability.
- T1685.005mostlyresponds — A.5.36 requires managers to identify non-compliance (including via automatic tools that can surface log-clearing), then contain/eradicate by identifying causes, implementing corrective actions such as restoring logs or re-enabling logging, and verifying effectiveness — which matches the `responds` definition of acting on an event once underway.
- T1556.006partialdetects — A.5.36's compliance reviews and optional automated measurement can surface unauthorized MFA disabling or policy deviations as non-compliance, but they are periodic and may miss T1556.006 variants such as hosts-file redirects or patched MFA programs that leave configuration appearing compliant.
- T1578.005partialdetects — A.5.36's compliance review process can identify non-compliance with security policies that mandate secure cloud configurations, and the clause explicitly contemplates automatic measurement tools to support this — so unauthorized modifications to cloud compute settings are within what the review surfaces. But the mechanism is periodic managerial review rather than continuous monitoring, and the detection depends on the review actually examining the relevant configurations, so what is caught is a slice of the technique's instances rather than the bulk.
Prevented OWASP Web Top 10 (2025) risks (11)
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
- A02mostlyfinds — A.5.36 explicitly requires reviews (including automated measurement/reporting tools) that discover non-compliance with security policies/standards, which directly surfaces weak defaults, incomplete hardening and exposed settings that constitute the A02 misconfiguration class.
- A01partialfinds — A.5.36 explicitly requires reviews (including automated measurement/reporting tools) that surface non-compliance with security policies/standards, which would discover many Broken Access Control violations when those policies mandate proper authorization enforcement.
- A02partialremoves — A.5.36 requires identifying non-compliance (including misconfigurations against policy/standards), then evaluating/implementing/reviewing corrective actions that remove the insecure defaults or exposed settings; this directly remediates instances of the weakness, but only for those surfaced by the organization's chosen review process rather than all instances or root causes like missing automation.
- A08partialfinds — A.5.36 explicitly requires reviews (including automated measurement/reporting tools) that discover non-compliance with information security policies/standards, which surfaces many integrity failures (e.g. unsigned updates or missing verification) when they violate applicable rules; it does not address all members such as certain CI/CD pipeline compromises or deserialization flaws that may not be caught by policy-compliance reviews.
- A09partialfinds — A.5.36 requires reviews (including automated measurement/reporting tools) that surface non-compliance with any security requirements, which would discover missing or ineffective logging/alerting when those are mandated by policy or standards; it is not specific to this weakness and the clause's primary focus is compliance verification rather than incident detection.
- A10partialfinds — A.5.36 explicitly requires reviews (including automated measurement/reporting tools) that surface non-compliance with security policies/standards, which would discover mishandled exceptions that violate those policies; however, it is governance-oriented and does not itself perform technical discovery of the code-level defects in the OWASP class.
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.