ISO 27001:2022 · Organizational controls
ISO 27001:2022 5.33: Protection of records
ISO 27001:2022 5.33 covers Protection of records. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.5.33, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is No retention schedule exists, so records are either kept forever or deleted early.
Records are to be safeguarded against being lost, destroyed, falsified, accessed without authorization or released without authorization. Purpose (stated in ISO/IEC 27002:2022): ensures compliance with legal, regulatory and contractual obligations and societal expectations for protecting and keeping records available. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 5.33.
What evidence supports 5.33?
- Annex A organizational controlStatement of Applicability entry for control A.5.33, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A organizational controlRecords handling guidelines covering storage, chain of custody, tamper prevention and disposal, aligned with the records management policy
- Annex A organizational controlA retention schedule listing record types, retention periods, legal basis and permitted storage media
- Annex A organizational controlEvidence of controlled destruction at the end of retention periods
- Annex A organizational controlProcedures and tests demonstrating that electronic records remain readable across format and technology changes
Where this requirement comes from
This is our own statement of ISO 27001:2022 5.33, read from the copy we hold (licensed complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- No retention schedule exists, so records are either kept forever or deleted early
- Encrypted archives cannot be opened because the keys were not retained
- Legacy formats can no longer be read and no migration was planned
- Records are held in systems that allow alteration without any audit trail
How it maps to SOC 2
No reviewed link is held for this control.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.