ISO 27001:2022 Annex A 8.13 – Information Backup Explained

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.

ISO 27001

Quick Guide: Annex A 8.13 at a Glance

Annex A 8.13 of ISO 27001:2022 focuses on information backup.

At a practical level, this means:

  • Backing up information, software, and systems based on business need
  • Protecting backups against loss, damage, or unauthorised access
  • Ensuring backups can be restored within agreed timescales
  • Testing backups regularly
  • Managing backup retention deliberately

The control does not define a single backup method. It expects topic-specific, risk-based backup arrangements aligned with business and operational requirements.

In-Depth Guide to Annex A 8.13

What Is Annex A 8.13 and Why Does It Matter?

Information loss occurs through:

  • Hardware or storage failure
  • Human error
  • Malware and ransomware
  • System corruption
  • Cloud or supplier failure

Without effective backups:

  • Recovery may be impossible
  • Business interruption may be prolonged
  • Regulatory and contractual obligations may be breached
  • Incident response options are severely limited

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.

How to Implement Annex A 8.13 Effectively

A pragmatic approach to Annex A 8.13 typically includes the following elements.

1. Define a Topic-Specific Backup Policy

Organisations should define how backups are managed, including:

  • Scope of systems, data, and applications covered
  • Backup frequency and type
  • Retention periods
  • Roles and responsibilities

Backup policies should reflect:

  • Business criticality
  • Legal and regulatory requirements
  • Operational recovery needs

Generic “one-size-fits-all” backups are rarely effective.

2. Identify What Needs to Be Backed Up

Organisations should identify:

  • Business-critical data
  • Key systems and applications
  • Configuration and system state information

Backup scope should include:

  • On-premises systems
  • Cloud-based platforms
  • Data held by third-party services

Cloud-hosted data is still organisational risk.

3. Define Recovery Objectives

Backup arrangements should align with agreed:

  • Recovery Time Objectives (RTOs)
  • Recovery Point Objectives (RPOs)

These define:

  • How quickly systems need to be restored
  • How much data loss is acceptable

Recovery objectives should be driven by business impact, not technical convenience.

4. Protect Backup Data Appropriately

Backups often contain the most complete copy of information.

Organisations should ensure backups are:

  • Stored securely
  • Protected from unauthorised access
  • Encrypted where risk justifies it

Backup data should be protected at least as well as live data.

5. Separate Backups From Source Systems

Annex A 8.13 explicitly supports separation.

Backups should be:

  • Physically or logically separated from source systems
  • Protected from the same threats as production environments

Separation reduces the risk of:

  • Simultaneous loss
  • Ransomware propagation
  • Widespread corruption
6. Verify Backup Jobs Before and After Execution

ISO 27001:2022 places additional emphasis on validation.

Organisations should:

  • Check for data loss before backup runs
  • Monitor backup job completion and success
  • Identify and remediate partial or failed backups

Silent failure is one of the most common backup weaknesses.

7. Test Restoration Regularly

Backups that are never tested are assumptions, not controls.

Organisations should:

  • Test restoration of data and systems periodically
  • Measure actual recovery times
  • Validate backups against agreed recovery objectives

Testing should be realistic and documented.

8. Monitor and Report Backup Status

Operational awareness is essential.

Organisations should ensure:

  • Backup failures are reported promptly
  • Responsible personnel are notified
  • Remedial action is taken quickly

Backups are only effective if someone notices when they fail.

9. Manage Backup Retention Deliberately

Backup retention should align with:

  • Business need
  • Legal and regulatory requirements
  • Information deletion controls (Annex A 8.10)

Retaining backups indefinitely increases:

  • Exposure
  • Cost
  • Legal and privacy risk

Retention should be defined, not accidental.

10. Secure Backup Media and Locations

Backup storage locations should be:

  • Environmentally protected
  • Physically secure
  • Accessible only to authorised personnel

Whether on-site, off-site, or cloud-based, backup locations remain a critical security dependency.

11. Align Backup With Business Continuity and Incident Response

Annex A 8.13 supports:

  • Business continuity planning
  • Incident response and recovery
  • Ransomware resilience

Backups are a core recovery mechanism — not a standalone IT task.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Practical Considerations

Annex A 8.13 does not require:

  • A single backup technology everywhere
  • Continuous real-time replication by default
  • Elimination of all data loss risk

It does require organisations to:

  • Be able to restore what matters
  • Within timescales the business accepts
  • Using backups that are known to work

Backups are not proven when they run.
They are proven when they restore.

Common Challenges and How to Overcome Them

  • Backups assumed to work but never tested
  • Perform regular restoration tests
  • Cloud data excluded from backup scope
  • Include externally hosted platforms
  • Backup failures not noticed
  • Implement monitoring and reporting
  • Backups stored alongside production systems
  • Separate and protect backup locations

Most backup failures are discovered during incidents — far too late.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Final Recommendations

Annex A 8.13 is about being able to recover when prevention fails.

When information backup is implemented effectively:

  • Data loss impact is reduced
  • Recovery is faster and predictable
  • Ransomware resilience improves
  • Business continuity plans become credible

Security controls try to stop incidents.
Backups ensure the organisation survives them.

That is the real purpose of Annex A 8.13.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls