RANSOMWARE GOES AFTER YOUR BACKUPS FIRST. HAVE YOU TESTED YOUR RESTORES RECENTLY?
The ransom note is on every screen when the office manager comes in Tuesday morning. The IT manager’s first thought is the backups. Restore last night’s copy, lose a day of work, and move on. Then he opens the backup console. The last three weeks of backups are encrypted too, and the job that was supposed to copy them offsite has been failing quietly since August.
The short answer: Ransomware goes after backups because backups are what let you recover without paying. Attackers look for backup systems they can reach from your network and delete or encrypt them. The defense is at least one copy they can’t touch, either immutable (locked so it can’t be changed or deleted) or air-gapped (disconnected from your network), and regular restore tests that prove you can actually get your data back.
Most businesses have backups. Far fewer have restored from them recently, and that’s the gap attackers count on. Here’s how to close it.
Why does ransomware go after your backups first?
Because your backups are the reason you might not pay. If you can restore your systems, the ransom note is a bad week, not a business decision. So attackers look for backups first and try to delete or encrypt any copy they can reach before they lock up everything else.
CISA, the federal government’s cybersecurity agency, warns that many ransomware variants try to find and delete accessible backups. That’s why its ransomware guide recommends keeping backups offline and encrypted, and regularly testing “the availability and integrity of backups.”
IT teams know this is a risk. In Enterprise Strategy Group’s 2025 survey of 400 IT and data protection professionals in the U.S. and Canada, more than 8 in 10 said they were concerned their backup copies could be infected or corrupted by ransomware.
The problem usually isn’t awareness. It’s a backup that sits on the same network, uses the same administrator passwords, and can be reached the same way as everything else.
What is an immutable backup?
An immutable backup is a copy that can’t be changed or deleted for a set period of time, even by someone with administrator access. If an attacker gets your passwords, they still can’t wipe it out.
That’s what makes immutability valuable. Many attacks succeed because the attacker logs in as an administrator and deletes backups the normal way. An immutable copy doesn’t care who’s asking. Until the lock expires, it stays put.
One caution from CISA’s guide: immutable storage doesn’t meet compliance criteria for certain regulations, so check your requirements before you rely on it for regulated data.
What is an air-gapped backup, and do you need both?
An air-gapped backup is a copy that’s disconnected from your network, so an attacker on your network can’t reach it at all. Traditionally that meant tapes or drives taken offsite. Today it can also mean a copy that’s logically isolated, with no standing connection to your systems.
Immutable and air-gapped backups solve related problems in different ways, and many organizations use both.
|
Type |
What it protects against |
The tradeoff |
|
Standard backup on your network |
Deleted files, failed hardware |
Attackers can often reach and destroy it |
|
Immutable backup |
Attackers deleting or encrypting backups, even with admin passwords |
Locked copies can’t be cleaned up early, and some regulations don’t accept it |
|
Air-gapped backup |
Anything that spreads across your network |
Slower to restore from, and someone has to keep it current |
A common setup is an immutable copy for fast restores and an air-gapped copy as the last resort if everything else fails.
What is the 3-2-1 backup rule?
The 3-2-1 rule is a common way to structure backups: keep three copies of your data, on two different types of storage, with one copy stored offsite. It’s simple, and it protects against most hardware failures and local disasters.
Many IT teams now extend it to 3-2-1-1-0. The extra “1” is one copy that’s immutable or offline, and the “0” means zero errors when you test a restore. That last number is the one most businesses skip.
When did you last test a restore?
If you can’t name the date, it’s been too long. A backup job that reports “success” tells you the copy was made. It doesn’t tell you the copy is complete, readable, or fast enough to restore before the damage piles up.
The numbers on recovery are sobering. In the same ESG survey, only 1% of organizations hit by ransomware recovered all of their lost data. Forty-five percent recovered half or less.
There are plenty of ways a backup fails quietly. A job stops running after a change and nobody notices. A critical folder was never included. The backup works, but restoring a full server takes three days when you assumed it would take three hours. A restore test is how you find these problems on a quiet afternoon instead of in the middle of an attack.
What does a real restore test look like?
Start small, work up to a full system, and time every step. The goal isn’t just to prove the data is there. It’s to learn how long getting it back actually takes.
|
Test |
What it proves |
|
Restore a single file from last week |
The basics work, and someone knows how to do it |
|
Restore a mailbox or shared folder |
You can recover the things people lose most often |
|
Restore a full server to a separate environment |
You can rebuild a whole system, and how long it takes |
|
Restore your most critical system, like your ERP or ticketing system |
Whether your recovery time matches how long you can really be down |
|
Write down the results |
Your next test starts from a known baseline, not memory |
Restore to a separate environment, not on top of your live systems, so a test never causes the outage it’s meant to prevent.
How often depends on how much change your systems go through, but at minimum, test before your busiest season and after any major change. For co-ops coming off harvest and manufacturers heading into a new year, the winter months are a good time to do it.
What about IBM i and AS/400 backups?
The same questions apply, and they’re easy to overlook on a system that has run reliably for decades. Whether you back up to tape, virtual tape, or a second system, ask whether at least one copy is offline or can’t be changed, whether you’ve restored to a separate partition recently, and how long a full system restore would really take.
IBM i environments often hold the most important data a business has, like orders, inventory, and financial history. A recovery plan that covers your Windows servers but not your IBM i system has a big hole in it.
Where to start
You don’t need to rebuild your backup strategy from scratch. You need to know where your copies live, whether an attacker could reach them, and how long a restore actually takes.
That’s work we do every day. Disaster recovery planning is part of our cybersecurity services, and it starts with exactly these questions. Every one of our managed IT packages includes Microsoft 365 backup. Our ARMOR and FORTRESS packages add 24/7 managed detection and response through Arctic Wolf, and high and critical alerts trigger a live call to a Koltiv technician at any hour, which matters when an attacker is looking for your backups at 2 a.m.
- Talk with our cybersecurity team about your backups and recovery plan.
- Get an assessment of where your weak spots are.
Every backup looks fine until the day you need it. The businesses that get through ransomware in days instead of weeks are usually the ones that found out, on a quiet afternoon, what was actually in their backups and how long it took to get it back. If you can’t remember the last time you tested a restore, that’s a good reason to schedule one this winter. And if you’d like help, give us a call.
Ready to GET STARTED?
Frequently asked questions
Why does ransomware target backups?
Backups let you recover without paying the ransom, so attackers try to delete or encrypt any backups they can reach from your network before they lock up your other systems. CISA recommends keeping backups offline and encrypted for that reason.
What is an immutable backup?
An immutable backup is a copy that can’t be changed or deleted for a set period of time, even by someone with administrator access. If an attacker steals your passwords, they still can’t wipe it out until the lock expires.
What is an air-gapped backup?
An air-gapped backup is a copy disconnected from your network, either physically, like a tape stored offsite, or logically, with no standing connection to your systems. An attacker on your network can’t reach it.
What is the 3-2-1 backup rule?
The 3-2-1 rule means keeping three copies of your data, on two different types of storage, with one copy offsite. Many IT teams now extend it to 3-2-1-1-0, adding one immutable or offline copy and zero errors on restore tests.
How often should you test a backup restore?
At minimum, test before your busiest season and after any major change to your systems. Start with a single file and work up to restoring a full critical system in a separate environment, timing each step so you know how long recovery really takes.
Sources
CISA and MS-ISAC: “#StopRansomware Guide.” Offline, encrypted backups; testing availability and integrity; ransomware variants that find and delete backups; caution on immutable storage and compliance
Enterprise Strategy Group (Omdia): “The Ransomware Reality: Cyber Resilience, Data Resilience, and Data Protection” (September 2025). Survey of 400 IT and data protection professionals in North America; more than eight in 10 concerned about backup copies; 1% recovered all lost data; 45% recovered half or less