Disaster recovery and compliance: what HIPAA, PCI-DSS, SOC 2, and GDPR require

Disaster recovery for compliance means proving you can restore critical systems and data within the limits set by HIPAA, PCI-DSS, SOC 2, and GDPR.

—

10 minutes
Doctor and nurse bedsite speaking with a patient

Key takeaways:

  • PCI-DSS requires an annual test, SOC 2 requires tests across an audit window, and HIPAA and GDPR leave the schedule to you.
  • Recovery Point Objective (RPO) and Recovery Time Objective (RTO) turn vague requirements into numbers you can validate.
  • Auditors want a written plan, dated test records, and a documented responsibility split with your host.
  • Backups need separate credentials and immutable copies to survive ransomware.

If your business must comply with HIPAA, PCI-DSS, SOC 2, or GDPR regulations, disaster recovery is part of your obligations. This obligation isn’t obvious because the frameworks don’t include a clearly-labeled disaster recovery section. HIPAA puts it in a contingency planning standard, PCI-DSS in a requirement about testing your incident response, SOC 2 in a criterion about availability, and GDPR in an article about restoring access to personal data.

Backups are one piece of it, but they aren’t the same thing. A backup is a copy of your data, while disaster recovery is the tested plan and infrastructure that bring your systems back online.

What is disaster recovery for compliance?

Disaster recovery for compliance is the practice of meeting the recovery requirements set by the laws, regulations, and industry standards that apply to your business. It requires a written plan for restoring critical systems and data, proof that you tested it, and records an auditor can review. The HIPAA, PCI-DSS, SOC 2, and GDPR frameworks describe the outcome and leave the method and recovery targets to you.

Core metrics: RPO and RTO

RPO and RTO are the core metrics disaster recovery is built on.

  • Recovery point objective (RPO) is the most data you can afford to lose, measured in time.
  • Recovery time objective (RTO) is the longest a system can stay down before it has to be running again.

Regulations don’t give you these numbers. HIPAA, GDPR, and SOC 2 expect you to set targets for each system, record why, and show test results that meet them. Set them with whoever runs your servers, so you don’t accidentally set a target your infrastructure can’t hit. Each framework then adds its own rules on top.

Disaster recovery requirements by compliance framework

How often you test a disaster recovery plan differs by compliance framework. PCI-DSS gives you an annual deadline, SOC 2 wants tests spread across a period you agree on with an auditor in advance, HIPAA doesn’t set a frequency, and GDPR expects you to set numbers and then defend it.

Passing one regulation doesn’t guarantee you’ll pass the next, and they all ask for different proof.

FrameworkWhere DR sitsTest frequencyEvidence to hand over
HIPAAContingency plan standard, 45 CFR 164.308(a)(7)Not setContingency plan, ranked list of critical systems, test and revision records
PCI-DSSRequirements 12.10.2, 9.4.1.1, and 9.4.1.2At least every 12 monthsDated test result and backup location review
SOC 2Trust Services Criterion A1.3Spread across the audit windowDated test records across the reporting period
GDPRArticles 32 and 33You set it and defend itWritten recovery windows and test results against them

Here’s what each framework expects from your disaster recovery plan, and what you’ll need to hand over to an auditor:

HIPAA: if you handle patient records

HIPAA applies if you handle patient records, and it treats backup and recovery as two separate obligations. Its contingency plan standard has five parts (45 CFR 164.308). Three are required:

  • A data backup plan
  • A disaster recovery plan
  • An emergency mode operation plan, which keeps critical processes running while you recover

Two other obligations are addressable, meaning you either implement them or document why the alternative you chose is reasonable for your business:

  • Testing and revision procedures
  • An analysis of which applications and data are most critical

Rank your systems by which ones stop patient care and which ones can wait a day, and the RTO for each one. This gives you the order you’ll follow to get them back online. Your disaster recovery plan is written around that order. Keep the ranked list with the plan and hand over both, since the list is what shows you decided the order before anything happened.

PCI-DSS: if you take card payments

PCI-DSS applies if you take card payments, and it puts a clock on your testing (PCI DSS v4.0.1).

  • Requirement 12.10.2. Your incident response plan has to be reviewed and tested at least once every 12 months. You can do a tabletop exercise, which is a run-through in a room instead of an actual restore, as long as you keep the attendance list, the scenario you ran, and what you recorded afterwards
  • Requirement 9.4.1.1. Offline media backups holding cardholder data have to be stored in a secure location.
  • Requirement 9.4.1.2. The security of that location has to be reviewed at least once every 12 months.

During an audit, you supply the dated result of your test and the record of the location review. This documentation and your media backups should be stored on a system separate from the live systems it covers. Ransomware follows the credentials and network paths it finds, so a backup sitting on the same network behind the same logins gets encrypted alongside the systems it was there to protect.

SOC 2: if you handle data on behalf of your customers

SOC 2 applies if you handle data on behalf of your customers. It requires that you prove you have internal security controls that operate effectively over a sustained period of time, usually 3 to 12 months.

  • The reporting period. A Type 2 report covers a window you agree with your auditor in advance and says whether your security controls operated effectively across the entire window of time. The report requires a detailed write up of your company’s infrastructure, software, data, security and disaster recovery procedures. It must provide the evidence of direct testing via access logs that your onboarding steps, backup/recovery and firewalls are all working as intended.  It includes a formal statement, where senior leadership confirms the system’s controls are accurately presented and effective.
  • Criterion A1.3. The AICPA Trust Services Criteria asks you to test your recovery procedures. You will not pass the audit if you have the written plan, but don’t have a copy of your recovery test. 
  • The record. Each test needs a dated record, and those records have to fall across the window instead of clustering at the end of it.

SOC 2 is also the report customers ask for by name, because their auditor will treat your SOC 2 as the evidence covering the part of their operation you run.

Testing against an isolated copy of your environment is how you keep to that schedule without disrupting customers. An isolated test boots your systems somewhere separate, confirms they come up and the data is usable, and leaves the systems your customers are on untouched. You hand over the dated record from each test across the window.

GDPR: if you hold data on people in the EU

GDPR applies if you hold data on people in the EU, and it sets three obligations that touch recovery.

  • Article 32(1)(c). You need the ability to restore availability and access to personal data in a timely manner after an incident (Article 32).
  • Article 32(1)(d). You need a process for regularly testing, assessing, and evaluating whether your measures work.
  • Article 33(1). You have 72 hours from becoming aware of a breach to notify a supervisory authority, and a notification made later has to carry the reasons for the delay (Article 33).

“Timely manner” is left to you, so you set the number and then have to defend it. That number is your RTO. Decide an acceptable recovery window for each system holding personal data, write it down with the reasoning behind it, and use your tests to show you meet it.

The 72-hour clock starts when you become aware of a breach, which is before recovery ends, so your plan needs to name which systems hold personal data before you’re working that out mid-incident. You hand over your written recovery windows and the test results against them.

Additional frameworks with disaster recovery requirements

Additional frameworks with disaster recovery requirements apply to financial institutions and international suppliers.

The same plan, test records, and responsibility split carry across all of them.

What HIPAA, PCI-DSS, SOC 2, and GDPR have in common

HIPAA, PCI-DSS, SOC 2, and GDPR want the same three things underneath their own wording:

  • A recovery plan that exists as a document
  • A dated record showing somebody tested it
  • Clarity on which parts of recovery are yours and which belong to whoever hosts your systems

For the ownership split, ask your host for their half in writing. They will own the storage, the replication, and the facility.  You are responsible for an incident, setting your recovery order, and keeping the documentation current. Every regulatory framework requires division of responsibilities between you and any service provider is written down somewhere.

Key components of a disaster recovery plan

Key components of a disaster recovery plan include:

  • Risk assessment: Threats, single points of failure, and the RTO and RPO for each critical system.
  • Runbooks: Step-by-step recovery procedures with named owners, escalation paths, and checks that confirm a service is back.
  • Testing schedule: Tabletop exercises plus technical restore tests, run in dependency order so identity, DNS, and databases come up first.
  • Communication plan: Contacts for staff, customers, vendors, and regulators.
  • Data residency: Where backups and recovery sites sit, so regulated data stays within required geographic limits.

When a test fails, auditors look for the cause, the owner of the fix, and the retest.

Ransomware and protected backups

Ransomware and protected backups are now part of disaster recovery compliance, since an attacker who encrypts your recovery copies breaks every availability requirement at once. You can protect backups by:

  • Keeping at least one immutable copy
  • Using backup admin accounts separate from production, with multi-factor authentication
  • Storing copies on a separate network from the systems they protect
  • Testing a clean restore from a known-good restore point
  • Matching retention to your legal and privacy obligations.

Requirements for your hosting provider

Requirements for your hosting provider start with your plan: if you host your servers with a third party provider, you will need to include them in your backup and disaster recovery plan.  How much you do and how much they do will be determined during your purchase of services. Auditors expect this division of labor to be documented and may test it during a recovery simulation.

Disaster recovery compliance FAQs

At least every 12 months covers PCI-DSS and DORA. SOC 2 needs tests across your audit window, and HIPAA and GDPR expect a schedule you can justify.

No. Auditors want proof you can restore data within your RTO, which only a dated recovery test provides.

No. A provider can run recovery infrastructure and testing, but the compliance obligation stays with your business. To see how Nexcess runs the infrastructure side of recovery, explore Nexcess disaster recovery.