Backups are not about convenience.
They are about survival when something goes wrong.
Annex A 8.13 exists to ensure organisations implement, manage, and test information backups, so data and systems can be recovered following loss, failure, or disruption.
This control is about recoverability and resilience, not just copying data.

Annex A 8.13 of ISO 27001:2022 focuses on information backup.
At a practical level, this means:
The control does not define a single backup method. It expects topic-specific, risk-based backup arrangements aligned with business and operational requirements.
Information loss occurs through:
Without effective backups:
Annex A 8.13 ensures organisations plan for failure, rather than assuming systems will always be available.
This control replaces ISO 27001:2013 Annex A 12.3.1 and expands guidance to reflect modern environments, including cloud services and encryption.
A pragmatic approach to Annex A 8.13 typically includes the following elements.
Organisations should define how backups are managed, including:
Backup policies should reflect:
Generic “one-size-fits-all” backups are rarely effective.
Organisations should identify:
Backup scope should include:
Cloud-hosted data is still organisational risk.
Backup arrangements should align with agreed:
These define:
Recovery objectives should be driven by business impact, not technical convenience.
Backups often contain the most complete copy of information.
Organisations should ensure backups are:
Backup data should be protected at least as well as live data.
Annex A 8.13 explicitly supports separation.
Backups should be:
Separation reduces the risk of:
ISO 27001:2022 places additional emphasis on validation.
Organisations should:
Silent failure is one of the most common backup weaknesses.
Backups that are never tested are assumptions, not controls.
Organisations should:
Testing should be realistic and documented.
Operational awareness is essential.
Organisations should ensure:
Backups are only effective if someone notices when they fail.
Backup retention should align with:
Retaining backups indefinitely increases:
Retention should be defined, not accidental.
Backup storage locations should be:
Whether on-site, off-site, or cloud-based, backup locations remain a critical security dependency.
Annex A 8.13 supports:
Backups are a core recovery mechanism — not a standalone IT task.
Annex A 8.13 does not require:
It does require organisations to:
Backups are not proven when they run.
They are proven when they restore.
Most backup failures are discovered during incidents — far too late.
Annex A 8.13 is about being able to recover when prevention fails.
When information backup is implemented effectively:
Security controls try to stop incidents.
Backups ensure the organisation survives them.
That is the real purpose of Annex A 8.13.
We can help you understand your actual security needs and even if we cant help we can point you in the right direction
Talk to a security expert today