ISO 27001:2022 · Technological controls
ISO 27001:2022 8.13: Information backup
ISO 27001:2022 8.13 covers Information backup. The held text names 5 evidence records for it, the first being Statement of Applicability entry for control A.8.13, showing inclusion or justified exclusion, implementation status and the risks it.... The common gap an assessor flags is Backups run but full system restores have never been tested.
Backups of information, software and systems are to be kept and tested regularly as the agreed topic-specific backup policy requires. Purpose (stated in ISO/IEC 27002:2022): makes it possible to recover lost data or systems. 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 8.13.
What evidence supports 8.13?
- Annex A technological controlStatement of Applicability entry for control A.8.13, showing inclusion or justified exclusion, implementation status and the risks it treats
- Annex A technological controlThe topic-specific backup policy and backup plans stating scope, extent, frequency and retention per system aligned with RPO
- Annex A technological controlBackup job monitoring reports with evidence that failed jobs were investigated and rerun
- Annex A technological controlRestore test records onto test systems, checked against the recovery time in the continuity plan
- Annex A technological controlEvidence of off-site or geographically separate backup storage with suitable physical protection
Where this requirement comes from
This is our own statement of ISO 27001:2022 8.13, 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
- Backups run but full system restores have never been tested
- Backups are stored in the same site or cloud region as production
- Cloud SaaS data is assumed to be backed up by the provider
- Backup failures are logged but not followed up, leaving gaps
How it maps to SOC 2
- A1.2 high Information backup is the data backup limb of this criterion.
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.