HIPAA Security Rule
Administrative

HIPAA Security Rule 164.308(a)(7)(ii)(B): Disaster Recovery Plan (Required)

Establish procedures to restore lost data and resume operations. NIST recommends documented recovery procedures, alternate site arrangements, and aligned dependencies.

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

What else in your programme already covers this

This control maps to 57 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.

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

  • CFTC-SS-10 Geographic Dispersal of Backup Infrastructure and Personnel
  • CFTC-SS-22 Business Continuity and Disaster Recovery Planning Category
  • CFTC-SS-26 Own Resources or Contractual Arrangements to Meet the Recovery Objective
  • CFTC-SS-29 Recovery Plan Accounts for Essential Service Providers
  • CFTC-SS-8 Business Continuity and Disaster Recovery Plan and Resources
  • CFTC-SS-9 Next Business Day Recovery Time Objective

ISO 22301:2019 · 5 controls

  • 7.5.1 General
  • 8.2 Business impact analysis and risk assessment
  • 8.3.2 Identification of strategies and solutions
  • 8.4.4 Business continuity plans
  • 8.4.5 Recovery

NIST Cybersecurity Framework 2.0 · 5 controls

  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-PR.DS-11 Backups of data are created, protected, maintained, and tested
  • 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-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms

NIST SP 800-53 Rev 5 · 5 controls

CIS Controls v8 · 4 controls

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

ISO 27001:2022 · 4 controls

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity
  • 7.5 Protecting against physical and environmental threats
  • 8.13 Information backup

FedRAMP High · 3 controls

  • CP-10 System Recovery and Reconstitution
  • CP-6 Alternate Storage Site
  • CP-7 Alternate Processing Site

FedRAMP Moderate · 3 controls

  • CP-10 System Recovery and Reconstitution
  • CP-6 Alternate Storage Site
  • CP-7 Alternate Processing Site

ISO 27002:2022 · 3 controls

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

NIST SP 800-161 Rev 1 · 3 controls

SOC 2 · 3 controls

  • SOC2-A1.2 A1.2 Environmental protection, backup and recovery infrastructure
  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC7.5 CC7.5 Recovering from security incidents

APRA CPS 230 Operational Risk Management · 2 controls

  • CPS230-20 Prevention, Adaptation and Return to Normal Operations
  • CPS230-26 Critical Operations Register, Continuity Plan and Activation

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

  • ASD37-35 Business continuity and disaster recovery plans (Very Good)
  • ASD37-36 System recovery capabilities (Very Good)

Azure Security Benchmark · 2 controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

ACSC Essential Eight · 1 control

  • E8-BACKUP-ML1 Regular Backups (ML1)

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

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

C5 (Germany) · 1 control

ISO 27701:2019 · 1 control

  • 6.14.1 Information security continuity

PCI DSS 4.0 · 1 control

  • 10.7.3 10.7.3 Respond promptly to critical security control failures

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 Administrative

You are reading one control. How much of HIPAA Security Rule have you already done?

HIPAA Security Rule 164.308(a)(7)(ii)(B) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of HIPAA Security Rule your existing evidence covers. Hold ISO 27001:2022 and 53 of 67 HIPAA Security Rule controls already carry evidence.

If you hold ISO 27001:202279.1% covered · 14 gapsIf you hold ISO 27002:202279.1% covered · 14 gapsIf you hold FedRAMP Moderate77.6% covered · 15 gapsIf you hold NIST SP 800-53 Rev 577.6% covered · 15 gapsIf you hold C5 (Germany)76.1% covered · 16 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.167.2% covered · 22 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. 64 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll HIPAA Security Rule controls