Azure Security Benchmark
Governance and Strategy

Azure Security Benchmark ASBv3-GS-8: Define and implement backup and recovery strategy

Define and implement a backup and recovery strategy with documented guidance, policy and standards including recovery time and recovery point objectives.

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

What else in your programme already covers this

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

  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • 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-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms
  • NIST-CSF-RS.MA-05 The criteria for initiating incident recovery are applied
  • CPS230-19 Tolerance Levels for Each Critical Operation
  • CPS230-26 Critical Operations Register, Continuity Plan and Activation
  • CPS230-P40 Required Content of the Business Continuity Plan

C5 (Germany) · 3 controls

  • C5-BCM-01 Top management responsibility
  • C5-BCM-02 Business impact analysis policies and instructions
  • C5-OPS-06 Data Backup and Recovery - Concept
  • CFTC-SS-22 Business Continuity and Disaster Recovery Planning Category
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources
  • CFTC-SS-9 Next Business Day Recovery Time Objective

ISO 27001:2022 · 3 controls

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity
  • 8.13 Information backup

ISO 27002:2022 · 3 controls

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity
  • 8.13 Information backup

FedRAMP High · 2 controls

  • CP-1 Policy and Procedures
  • CP-2 Contingency Plan

FedRAMP Moderate · 2 controls

  • CP-1 Policy and Procedures
  • CP-2 Contingency Plan

HIPAA Security Rule · 2 controls

ISO 22301:2019 · 2 controls

  • 6.2.1 Establishing business continuity objectives
  • 8.3.1 General

NIST SP 800-53 Rev 5 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

SOC 2 · 2 controls

  • SOC2-A1.2 A1.2 Environmental protection, backup and recovery infrastructure
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption
  • E8-BACKUP-ML1 Regular Backups (ML1)
  • ANSSI-HYG-37 Define and Apply a Backup Policy for Critical Components
  • ASD37-35 Business continuity and disaster recovery plans (Very Good)

CIS Controls v8 · 1 control

  • CIS-11.1 Establish and Maintain a Data Recovery Process

ISO 27701:2019 · 1 control

  • 6.14.1 Information security continuity

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 Governance and Strategy

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark ASBv3-GS-8 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

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