A.5.33 Organizational
Protection of records
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 (18)
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
- SI-12mostlycovers — A.5.33's focus on protecting records to meet legal/societal expectations accounts for the bulk of SI-12's retention-and-management obligations under laws and policies, but leaves a residual on pure availability/operational retention aspects not centered on protection.
- AU-11partialcovers — A.5.33's broad requirement to protect records (including availability) to meet all legal/regulatory/contractual obligations accounts for only a slice of AU-11's specific audit-record retention period and investigative-support purpose; the bulk of AU-11's operational retention mechanics and audit-specific focus sit outside A.5.33.
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).
Why these map — rationale
- GV.OC-03domain mandateimplements — A.5.33 operationalizes the protection and availability of records to meet exactly the legal/regulatory/contractual obligations that GV.OC-03 requires an organization to understand and manage; the link is by shared subject domain rather than explicit citation of one by the other.
- PR.DS-01domain mandateimplements — A.5.33 operationalizes protection and availability of records (a form of data-at-rest) to meet legal and societal requirements, which directly serves the PR.DS-01 outcome within its data-protection domain without the outcome naming this specific control
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).
Mitigated MITRE ATT&CK techniques (3218)
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
- T1565partialprevents — A.5.33 mandates guidelines on storage, handling, chain of custody and disposal that explicitly include 'prevention of manipulation of records,' which constrains T1565 at the governance layer; however, the control issues guidelines and retention schedules rather than implementing the technical mechanisms (access control, integrity verification, audit) that actually stop manipulation, so the constraint is a mandate whose effect depends on downstream implementation.
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.