Security Operations
anti-ransomware backup solutions To keep the bugs away
Ransomware encrypts your data for ransom, and many variants try to delete or encrypt any backups they can reach. An immutable backup cannot be altered or deleted for a set period. We set up immutable or isolated backups, test restores on a schedule and agree on what comes back first.
- Who it is for
- Law, health care, schools, accounting and critical infrastructure
- How it runs
- Monthly backup reviews and scheduled restore tests
- What you get
- Backup job reports, restore test evidence and recovery records
Many ransomware strains go after your backups
The #StopRansomware Guide from the Cybersecurity and Infrastructure Security Agency (CISA), the Federal Bureau of Investigation (FBI) and their partners warns that "many ransomware variants attempt to find and subsequently delete or encrypt accessible backups."
In Verizon's 2026 Data Breach Investigations Report, ransomware was involved in 48% of breaches. Where the victim's size was known, about 96% of ransomware victims had fewer than 1,000 employees.
In its 2025 report, the FBI's Internet Crime Complaint Center (IC3) broke down more than 1,400 ransomware complaints from organizations outside critical infrastructure. Legal services were reported most, then contracting services such as electricians, then engineering and architectural services. Inside critical infrastructure, the FBI calls ransomware "among the highest reported cyber threats."
This page covers getting ready before an attack. If one is underway now, the FBI says to file a report with IC3 at ic3.gov.
Immutable backup, offline copies and the 3-2-1 rule
An immutable copy cannot be changed, an offline copy cannot be reached from your network, and the 3-2-1 rule keeps copies in more than one place.
The FBI recommends backups that are encrypted and immutable and that cover the organization's entire data infrastructure. Ask what a product means by the word. Microsoft, for example, says its own backup product for Microsoft 365 follows the immutability definition "except for disallowing deletion," which means it does not block deletion.
For offline copies, the FBI advises keeping backups "not connected to the computers and networks they are backing up," and CISA's guide calls for "offline, encrypted backups of critical data."
For small and medium businesses, CISA's guidance sums up where copies should live as the 3-2-1 rule:
- 3 copies of important files
- 2 different types of storage media, like a hard drive and the cloud
- 1 copy stored off-site, away from your business location
Our backup and disaster recovery services
Fully managed, alongside your in-house team, or for a single project.
- Backup and Ransomware RecoveryImmutable or isolated backups of the systems and data you approve, with protected repositories, monitored backup jobs and scheduled restore tests.
- Microsoft 365 Backup and SaaS Data ProtectionSoftware as a service (SaaS) backup for your Microsoft 365 email, OneDrive, SharePoint and Teams, and a review of retention limits.
- Backup and Recovery Architecture DesignA one-time project that sets recovery objectives with you, plans what is protected and where copies live, and designs the restore tests.
- Business Continuity PlanningA plan for what comes back first when something goes down.
How we set up and run your backups
- 01 DesignWhere your setup needs it, we start with the design project.
- 02 Set upWe set up or review the backups and protect where they are stored.
- 03 ReviewEvery month we review the backup jobs, and you receive a backup job report.
- 04 TestScheduled restore tests show whether data comes back, and each one is documented.
- 05 PlanEach year and after major changes, continuity planning reviews the plan and the recovery priority list.
Backup and restore records you receive
- 01Backup job reportWhich backup jobs ran and which need attention.
- 02Restore test evidenceWhat each scheduled restore test covered, and the result.
- 03Recovery validation recordHow restore paths were checked, and what the checks found.
- 04Repository evidenceHow the storage that holds your copies is protected.
- 05Recovery objective summaryFrom the design project: your recovery time and recovery point targets.
- 06Retention limitation summaryFrom the Microsoft 365 backup: what built-in retention does not cover.
Recovery time, recovery point and restore tests
How fast you get back depends on targets you set before an attack, and on restore tests that show whether you can meet them.
The National Institute of Standards and Technology (NIST) defines both targets. Your recovery time objective (RTO) is how long systems can stay in recovery before the business is harmed. Your recovery point objective (RPO) is "the point in time to which data must be recovered after an outage," or how much recent work you can afford to lose.
Then set the order. CISA's guide says to restore based on "a predefined critical asset list," and NIST's Cybersecurity Framework (CSF) 2.0 says recovery actions are "selected, scoped, prioritized, and performed." Continuity planning puts the order in a recovery priority list, and you approve it with the targets.
For testing, CISA says to "perform scheduled recovery tests to verify backup integrity" and to make sure your team can restore data both fully and partially. Under CSF 2.0, backups are "created, protected, maintained, and tested" (PR.DS-11), and their integrity is verified before they are used (RC.RP-03). The FBI also says to double-check that each backup completed.
Our backup and restore work is aligned with the Protect and Recover functions of CSF 2.0 and with Center for Internet Security (CIS) Control 11, Data Recovery. Our NIST CSF 2.0 program and CIS Controls program cover the rest of each framework.
Microsoft 365 retention is not a full backup
Microsoft says Exchange Online, the email service in Microsoft 365, "does not provide a way to perform a traditional backup of mailboxes." Microsoft replicates your data so the service can fail over to live copies, and it says those disaster recovery copies keep "the current state of content, not any historical versions."
Microsoft also describes the limits of the built-in features: point-in-time restore of mailbox items is out of scope for Exchange Online, file versions do not scale well for large ransomware attacks, and legal holds are built for export, not mass restore.
That gap is what our Microsoft 365 backup is for, with restore validation where included. For safer sign-ins and email protection, see our Microsoft 365 security service.
What we run for you, What you choose and approve
CyberBlip
- Design or review your backup setup
- Monitor backup jobs and review them each month
- Protect the repositories that store your copies
- Run scheduled restore tests and validate restore paths
- Match technical recovery to your business priorities
You
- Choose which systems and data are protected
- Set how long copies are kept
- Approve recovery priorities and restore targets
- Approve storage purchases and backup tool licensing
- Name the business processes that matter most
What backups can and cannot do
Backups bring data back. They cannot undo a theft. In ransomware attacks on small businesses, Verizon describes attackers taking non-public data and then trying to extort the victim with it. For that, our data breach readiness program maps the breach laws that may apply and builds a response plan your team has practiced.
A restore only returns what was in the agreed backup scope, and copies on storage that fails can be lost with it. No continuity plan keeps every operation running through every disaster.
Backups are one control among several. The FBI lists them alongside multi-factor authentication (MFA), least privilege, network segmentation and patching. For the protection around your backups, see our managed security layers.
Questions about backup and ransomware recovery
What is the difference between backup and disaster recovery?
A backup is a copy of your data. Disaster recovery is the plan and the work of getting systems and data back after an outage, in the order the business needs them. You need both, since copies without a tested plan can still leave you down.
We already have backups. Do we need this?
Maybe not all of it. Ask three things: can an attacker reach or change your copies, when did anyone last restore from them, and is the recovery order written down? Our Backup and Recovery Architecture Design project starts by assessing your current backup environment, then designs, implements and documents the changes and validates the restore paths.
How far back should our backups go?
CISA says to make sure you can roll back data at least seven days. Beyond that, retention is your decision, based on how far back you might need to restore and any rules your industry sets. We configure the retention you approve and record it with the backup evidence.
Does HIPAA require backups?
Yes, the Health Insurance Portability and Accountability Act (HIPAA) Security Rule requires a data backup plan (45 CFR 164.308(a)(7)). The Department of Health and Human Services (HHS) has also proposed, but not finalized, a rule that would require written procedures to restore certain systems and data within 72 hours, and HHS says the current Security Rule remains in effect. For the rest of the rule, see our HIPAA compliance services.
What does NERC CIP require for backups?
NERC CIP, the North American Electric Reliability Corporation's Critical Infrastructure Protection standards, handles this in CIP-009-6. It requires registered entities to have processes to back up the information needed to recover their high and medium impact Bulk Electric System (BES) Cyber Systems. For high impact systems and medium impact systems at control centers, it also requires checking that backups completed and testing a representative part of that information at least once every 15 calendar months. Our NERC CIP program is IT-scoped and does not take over a registered entity's own compliance.
Should we pay the ransom to get our data back?
The FBI does not support paying a ransom in response to a ransomware attack, and it says "Paying a ransom doesn't guarantee you or your organization will get any data back." That decision, and any legal questions around it, belongs with your leadership and your attorney.
Sources
Show all 15 sourcesHide sources
- Ransomware Risk Management: A Cybersecurity Framework 2.0 Community Profile (NIST IR 8374r1) NIST, 2026-06
- #StopRansomware Guide CISA, 2023-09
- Back Up Business Data CISA
- 2025 IC3 Annual Report FBI Internet Crime Complaint Center (IC3), 2026-04-16
- Ransomware FBI
- 2026 Data Breach Investigations Report Verizon, 2026
- The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29 NIST, 2024-02-26
- Glossary: recovery time objective (RTO), from NIST SP 800-34 Rev. 1 NIST Computer Security Resource Center
- Glossary: recovery point objective (RPO), from NIST SP 800-34 Rev. 1 NIST Computer Security Resource Center
- Back up email in Exchange Online Microsoft Learn, 2023-02-22
- Overview of Microsoft 365 Backup Microsoft Learn, 2026-11-04
- Frequently asked questions about Microsoft 365 Backup Microsoft Learn, 2026-11-04
- 45 CFR 164.308, Administrative safeguards (HIPAA Security Rule) eCFR, 2026-11-13
- HIPAA Security Rule Notice of Proposed Rulemaking Fact Sheet HHS, 2024-12-27
- CIP-009-6, Cyber Security, Recovery Plans for BES Cyber Systems NERC, 2014-11-13
Next step
Find out where you stand
Tell us how we can best support you.
Icons: Tabler Icons, MIT License. License text: /licenses/tabler-icons.txt