CIS Controls v8
CIS Control 11: Data Recovery

CIS Controls v8 CIS-11.4: Establish and Maintain an Isolated Instance of Recovery Data

Set up and keep a copy of recovery data that is isolated, for example by version-controlling backup targets held off site, in the cloud or offline, whether as systems or as services.

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

What else in your programme already covers this

This control maps to 52 controls across 22 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 · 6 controls

  • CM-2(3) Retention of Previous Configurations
  • CP-10 System Recovery and Reconstitution
  • CP-2(3) Resume Mission and Business Functions
  • CP-6 Alternate Storage Site
  • CP-6(1) Alternate Storage Site | Separation from Primary Site (CP-6(1))
  • CP-9 System Backup

FedRAMP Moderate · 6 controls

  • CM-2(3) Retention of Previous Configurations
  • CP-10 System Recovery and Reconstitution
  • CP-2(3) Resume Mission and Business Functions
  • CP-6 Alternate Storage Site
  • CP-6(1) Alternate Storage Site | Separation from Primary Site (CP-6(1))
  • CP-9 System Backup

ISO 22301:2019 · 6 controls

  • 8.3.2 Identification of strategies and solutions
  • 8.3.3 Selection of strategies and solutions
  • 8.3.4 Resource requirements
  • 8.3.5 Implementation of solutions
  • 8.4.4 Business continuity plans
  • 8.4.5 Recovery

ISO 27001:2022 · 5 controls

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity
  • 7.10 Storage media
  • 8.13 Information backup
  • 8.14 Redundancy of information processing facilities

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-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.4 CC6.4 Restricting physical access to facilities and assets
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • 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-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms
  • CFTC-SS-10 Geographic Dispersal of Backup Infrastructure and Personnel
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources

HIPAA Security Rule · 2 controls

ISO 27002:2022 · 2 controls

  • 5.30 ICT readiness for business continuity
  • 8.13 Information backup

NIST SP 800-66 Rev 2 · 2 controls

PCI DSS 4.0 · 2 controls

  • 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
  • E8-BACKUP-ML3 Regular Backups (ML3)
  • ISM-1811 Secure and resilient retention of backups
  • BR-2 Protect backup and recovery data

C5 (Germany) · 1 control

CMMC 2.0 · 1 control

DORA · 1 control

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

ISO 27701:2019 · 1 control

NIS2 Directive · 1 control

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

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 CIS Control 11: Data Recovery

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-11.4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

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. 240 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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