ISO 27001:2022
Technological controls – ISO 27001:2022

ISO 27001:2022 8.13: Information backup

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.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 98 controls across 30 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 8 controls

  • CP-10 System Recovery and Reconstitution
  • CP-10(2) System Recovery and Reconstitution | Transaction Recovery (CP-10(2))
  • CP-6 Alternate Storage Site
  • CP-9 System Backup
  • CP-9(1) Testing for Reliability and Integrity
  • CP-9(8) System Backup | Cryptographic Protection (CP-9(8))
  • IR-3 Incident Response Testing
  • SI-7(1) Integrity Checks

FedRAMP Moderate · 8 controls

  • CP-10 System Recovery and Reconstitution
  • CP-10(2) System Recovery and Reconstitution | Transaction Recovery (CP-10(2))
  • CP-6 Alternate Storage Site
  • CP-9 System Backup
  • CP-9(1) Testing for Reliability and Integrity
  • CP-9(8) System Backup | Cryptographic Protection (CP-9(8))
  • IR-3 Incident Response Testing
  • SI-7(1) Integrity Checks

ISO 22301:2019 · 8 controls

  • 7.1 Resources
  • 7.5.3 Control of documented information
  • 8.2.2 Business impact analysis
  • 8.3 Business continuity strategies and solutions
  • 8.3.5 Implementation of solutions
  • 8.4 Business continuity plans and procedures
  • 8.4.4 Business continuity plans
  • 8.4.5 Recovery

NIST Cybersecurity Framework 2.0 · 7 controls

  • NIST-CSF-GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
  • NIST-CSF-PR.DS-11 Backups of data are created, protected, maintained, and tested
  • NIST-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
  • NIST-CSF-RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process
  • NIST-CSF-RC.RP-03 The integrity of backups and other restoration assets is verified before using them for restoration
  • NIST-CSF-RC.RP-05 The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed

NIST SP 800-53 Rev 5 · 6 controls

Azure Security Benchmark · 5 controls

  • ASBv3-BR-3 Monitor backups
  • ASBv3-BR-4 Regularly test backup
  • ASBv3-GS-8 Define and implement backup and recovery strategy
  • BR-1 Ensure regular automated backups
  • BR-2 Protect backup and recovery data

CIS Controls v8 · 5 controls

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • CIS-11.2 Perform Automated Backups
  • CIS-11.3 Protect Recovery Data
  • CIS-11.4 Establish and Maintain an Isolated Instance of Recovery Data
  • CIS-11.5 Test Data Recovery

HIPAA Security Rule · 5 controls

ISO/IEC 42001:2023 · 5 controls

  • 7.5 Documented information
  • 7.5.3 Control of documented information
  • 8.4 AI system impact assessment
  • A.7 Data for AI systems
  • A.7.4 Quality of data for AI systems

SOC 2 · 5 controls

  • SOC2-A1.2 A1.2 Environmental protection, backup and recovery infrastructure
  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information
  • SOC2-PI1.1 PI1.1 Quality information about processing objectives, data definitions and specifications
  • SOC2-PI1.5 PI1.5 Controls over stored inputs, work in process and outputs

C5 (Germany) · 4 controls

  • C5-OPS-06 Data Backup and Recovery - Concept
  • C5-OPS-07 Data Backup and Recovery - Monitoring
  • C5-OPS-08 Data Backup and Recovery - Regular Testing
  • C5-OPS-09 Data Backup and Recovery - Storage

NIST SP 800-66 Rev 2 · 4 controls

PCI DSS 4.0 · 4 controls

  • 10.3.3 10.3.3 Audit logs promptly backed up to central secure storage
  • 12.3.1 12.3.1 Targeted risk analysis for flexible-frequency requirements
  • 9.4.1.1 9.4.1.1 Secure storage location for offline backups
  • 9.4.1.2 9.4.1.2 Annual review of offline backup location security

ACSC Essential Eight · 3 controls

  • E8-BACKUP-ML1 Regular Backups (ML1)
  • E8-BACKUP-ML2 Regular Backups (ML2)
  • E8-BACKUP-ML3 Regular Backups (ML3)

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

  • ASD37-34 Regular backups (Essential)
  • ASD37-36 System recovery capabilities (Very Good)

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

  • CFTC-SS-11 Testing and Review of Business Continuity and Disaster Recovery Capabilities
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources

COBIT 2019 · 2 controls

  • APO14.10 APO14.10 Manage data backup and restore arrangements
  • DSS04.07 DSS04.07 Manage backup arrangements

ISO 27002:2022 · 2 controls

  • 5.29 Information security during disruption
  • 8.13 Information backup

ISO 27701:2019 · 2 controls

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-37 Define and Apply a Backup Policy for Critical Components

APPI · 1 control

APRA CPS 230 Operational Risk Management · 1 control

  • CPS230-19 Tolerance Levels for Each Critical Operation

CMMC 2.0 · 1 control

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

DORA · 1 control

  • DORA-Art.12 Backup policies and procedures, restoration and recovery

GDPR · 1 control

ISO 27001:2013 · 1 control

NIS2 Directive · 1 control

  • Art.21.2.c Business continuity, backup management, disaster recovery and crisis management

NIST SP 800-171 Rev 3 · 1 control

  • 03.08.09 System Backup - Cryptographic Protection

NIST SP 800-218 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Technological controls – ISO 27001:2022

You are reading one control. How much of ISO 27001:2022 have you already done?

ISO 27001:2022 8.13 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

If you hold NIST SP 800-53 Rev 584.9% covered · 14 gapsIf you hold ISO 27001:201383.9% covered · 15 gapsIf you hold FedRAMP Moderate80.6% covered · 18 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.2% covered · 24 gapsIf you hold C5 (Germany)69.9% covered · 28 gapsIf you hold NIST Cybersecurity Framework 2.063.4% covered · 34 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 98 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll ISO 27001:2022 controls