Skip to main content
Guide, 8 minute read

Ransomware Recovery Plan: How to Test That Your Backups Will Restore

How to build a ransomware recovery plan from CISA and NIST guidance: offline and immutable backup copies, recovery time and recovery point objectives, what to test and how often, a restore test runbook, and CISA's first steps after an attack.

Planning guidesIT managers, operations leads, and owners at organizations that run backups but have not recently proven they can restore from themBy , Founder and CEO, Days Dynamics. Published November 10, 2026.

A recovery plan rests on backups ransomware cannot reach and restores you have proven

A ransomware recovery plan depends on backups an attacker cannot reach and restores you have already proven. CISA advises keeping offline, encrypted backups of critical data and regularly testing their availability and integrity in a disaster recovery scenario. Set a recovery time objective and a recovery point objective for each critical system, restore to an isolated network on a schedule your business sets, write down the results, and fix what failed.

What CISA and NIST say about backups and recovery

The public guidance agrees on the basics: keep copies that ransomware cannot reach, test them, and check that a backup is clean before you restore from it. Each source below was checked November 2026 and is linked in Sources.

SourceOn backup copiesOn testing and recovery
CISA #StopRansomware GuideKeep offline, encrypted backups of critical data, and keep golden images of critical systems up to dateRegularly test backup availability and integrity in a disaster recovery scenario, and regularly exercise an incident response plan
CISA: Back Up Business DataThe 3-2-1 rule: three copies of important files, two different types of storage media, one copy stored off siteRun scheduled recovery tests, restore data both fully and partially, and be able to roll back data at least seven days if needed
NIST Cybersecurity Framework (CSF) 2.0, February 26, 2024PR.DS-11: backups of data are created, protected, maintained, and testedRC.RP-03: verify the integrity of backups before using them for restoration
NIST SP 800-184, Guide for Cybersecurity Event Recovery, December 2016Use a staging system to validate the integrity of data recovered from backupsPractice a realistic scenario in a tabletop exercise, and test at a frequency that makes sense for the organization

Offline and immutable backup copies

CISA warns that many ransomware variants try to find and then delete or encrypt accessible backups. That is why CISA says it is important that backups are maintained offline, and why many teams also use storage that cannot be changed. CISA also cautions that immutable storage does not meet compliance criteria for certain regulations, and that misconfiguration can impose significant cost. Check both before you choose.

Copy typeHow it protects the backupWhat to decide
Offline copyIt is not connected to the production network, so ransomware on that network cannot reach itHow often it is refreshed, and who is allowed to reconnect it
Immutable on-premises repository, for example a Veeam hardened repositoryVeeam says backup files cannot be moved, modified or deleted for the period you set, but can be copiedAn immutability period that covers how far back you may need to restore
Immutable cloud vault, for example an Azure Backup immutable vaultMicrosoft says it blocks operations that could lead to loss of recovery points, and you can lock the setting so it cannot be disabledWhether to lock it, since Microsoft says immutability locking is irreversible
Soft delete, for example in Azure BackupMicrosoft keeps deleted backup data for 14 days by default, and you can extend that up to 180 daysA retention period long enough for someone to notice a deletion
Cloud-to-cloud backup of SaaS dataA copy of cloud application data kept outside that applicationCISA suggests considering a multi-cloud setup in case all accounts under the same vendor are impacted

See the Rubrik vs Veeam and the Veeam vs Microsoft 365 Backup.

Set recovery time and recovery point objectives first

Recovery objectives tell you what a passing restore test looks like. NIST defines the recovery point objective (RPO) as the point in time to which data must be recovered after an outage. The recovery time objective (RTO) is how long a system's components can be in recovery before the outage harms the organization's mission or business processes. CISA ties both targets to business needs.

Set them per system

A payroll server and a shared file folder rarely need the same targets. Agree each target with the people who run that part of the business, not only with IT.

Map the dependencies

NIST SP 800-184 notes that it is frequently necessary to recover an identity or authentication server before recovering files. Build that order into the plan.

Match backup frequency to the RPO

Hypothetical example: if the billing system can lose at most a morning of work, a backup that runs once a night does not meet its RPO.

Prove the RTO with a timed restore

Time every full restore test. If the restore takes longer than the RTO, change the backup design or agree a new target with the business.

What to test, and how often

No source sets one test frequency for every organization. CISA calls for scheduled recovery tests and for testing backup procedures on a regular basis. NIST SP 800-184 says to test at a frequency that makes sense for the organization. Set your schedule from your RTO and RPO targets and how often your systems change, and retest after any change to backup software or storage.

TestWhat it provesWhen to run it
File, folder, or mailbox restoreSingle items can be found and restored; CISA asks teams to restore data both fully and partiallyOn your regular schedule
Full server or virtual machine restoreA whole system comes back, and how long it takes compared with its RTOOn your regular schedule, and after changes to backup software or storage
Automated recovery verification, for example Veeam SureBackupVeeam says it runs machines in an isolated environment directly from backup, as a recovery verification taskOn your regular schedule, as a supplement to hands-on restores
Restore to a clean, isolated networkRestored systems come back without reconnecting to anything that may still be infectedDuring each full recovery exercise
Tabletop exercisePeople know their roles, who makes decisions, and the recovery orderAt a frequency that makes sense for the organization, as NIST puts it

A restore test runbook

Write the runbook once and follow it on every test, so results can be compared from one test to the next.

  • Pick the scope. Name the systems in this test, their RTO and RPO, and the recovery point you will restore from.
  • Restore somewhere safe. Use an isolated network or lab so the restored system cannot touch production.
  • Check the backup before you restore. NIST CSF 2.0 calls for verifying backup integrity before using a backup for restoration. Veeam's SureBackup job, for example, offers a backup verification and content scan mode.
  • Restore in dependency order. Bring back identity and authentication services before the file servers and applications that rely on them.
  • Time it. Record when the restore started and when the system was usable, and compare the result with the RTO.
  • Check the data. Open files, run a report, or sign in to the application, and confirm the newest data meets the RPO.
  • Test a partial restore too. Restore a single file, folder, or mailbox, since CISA asks teams to be able to restore both fully and partially.
  • Write down the result. Note what worked, what failed, how long it took, and who ran the test. Fix each failure and retest it.
  • Update the plan. Refresh contacts, the recovery order, and the incident response plan, which CISA recommends you regularly exercise along with a communications plan.

See the Backup and disaster recovery and the Veeam Backup & Replication 12 end of support.

What CISA says to do first after a ransomware attack

CISA's ransomware response checklist puts isolation and analysis before restoring data, and it warns to take care not to reinfect clean systems during recovery. Key early steps from that checklist:

  • Isolate. Determine which systems were impacted and immediately isolate them. If several systems or subnets appear impacted, take the network offline at the switch level.
  • Power down only if you must. CISA says to power down devices if you cannot disconnect them from the network, to avoid further spread, and notes that this step prevents keeping infection artifacts and potential evidence in volatile memory, so do it only if other means of disconnecting fail.
  • Triage. Triage impacted systems for restoration and recovery, and identify and prioritize critical systems for restoration on a clean network.
  • Report. Report the incident to CISA, your local FBI field office, the FBI Internet Crime Complaint Center (IC3), or your local U.S. Secret Service field office, and consider asking for their help.
  • Preserve evidence. Take a system image and memory capture of a sample of affected devices.
  • Find the way in. Identify the systems and accounts involved in the initial breach. Once the environment has been fully cleaned and rebuilt, issue password resets for all affected systems.
  • Restore in priority order. Reconnect systems and restore data from offline, encrypted backups based on a prioritization of critical services.

See the Managed detection and response and the MDR vs EDR vs antivirus.

Frequently asked questions

What is the 3-2-1 backup rule?

CISA describes it as three copies of important files, on two different types of storage media, such as a hard drive and the cloud, with one copy stored off site, away from your business location.

How often should we test our backups?

No single frequency fits every organization. CISA calls for scheduled recovery tests, and NIST SP 800-184 says to test at a frequency that makes sense for the organization. Base the schedule on each system's RTO and RPO and how often it changes, and retest after changes to backup software or storage.

What is the difference between RTO and RPO?

The recovery point objective (RPO) is the point in time to which data must be recovered after an outage, which sets how much recent data you can lose. The recovery time objective (RTO) is how long a system can be in recovery before the outage harms the business.

Are immutable backups enough on their own?

No. Immutable storage keeps backup files from being changed or deleted for a set period, but you still need to test restores and check a backup's integrity before using it. CISA also cautions that immutable storage does not meet compliance criteria for certain regulations and that misconfiguration can be costly.

Should we restore from backup as soon as ransomware is found?

Not first. CISA's checklist starts with isolating impacted systems, triage, and identifying the systems and accounts involved in the initial breach. Restore from offline, encrypted backups on a clean network, in order of critical services, and take care not to reinfect clean systems.

Plan how you will prove your backups restore before you need them

Send us what you back up today, where the copies live, and when a restore was last tested. We will help you set recovery targets for each system and plan a restore test schedule that fits them. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.

Sources

Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.

Planning this project now?

Turn the checklist into a plan

The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.