Ransomware Mitigation: Prevention and Recovery Steps

Ransomware mitigation means three things: stopping the attack before it starts, limiting how far it spreads if it gets in, and recovering without paying the ransom. No single product does all three. The organisations that survive ransomware do a small set of unglamorous things well — multi-factor authentication, prompt patching, backups attackers cannot reach — and they have a written plan for the first hours after an attack, made before they ever need it.

Ransomware is malware built for extortion. It encrypts your files or locks your device and demands payment, usually in cryptocurrency, for the key. Many modern variants also steal your data first, then threaten to publish it — so even a perfect backup does not fully undo the damage. The FBI and CISA, the US cybersecurity agency, both advise against paying: payment does not guarantee your files back, and it marks you as a payer for the next attack.

The scale is worth knowing. In Sophos’s 2026 survey of IT and security leaders, 56% of ransomware attacks succeeded in encrypting data — and 66% of organisations whose data was encrypted got it back from backups rather than from the attacker. The difference between those two groups is, almost entirely, mitigation done in advance.

How ransomware gets in

Almost every attack enters through one of three doors. Malicious email and phishing are the most common — Sophos’s 2026 survey put malicious email at 26% of attacks and phishing at 24%. A stolen password is the second: a VPN, email, or remote-desktop login with no second factor, bought or phished, and the attacker simply logs in. The third is an unpatched flaw in internet-facing software — a firewall, a VPN appliance, a web server — where the vendor published a fix and nobody applied it.

Notice what is not on that list: a genius hacker breaking encryption. Ransomware is, overwhelmingly, an ordinary-access problem. It succeeds because a door was left open, not because a wall was climbed. That is good news, because doors can be closed.

Prevention, in order of impact

Work through these in order. Each one closes a door; together they make an attack unlikely, and make a successful attack survivable.

1. Multi-factor authentication on every access point. Email, VPN, remote desktop, cloud admin panels, backup systems — all of them, with no exceptions for executives or IT staff. Phishing-resistant methods such as passkeys are best; app-based codes are good; text-message codes are better than nothing. One honest warning from the Sophos data: in 2026, multi-factor authentication was enabled in some form in 97% of incidents that started with compromised credentials — but it was often partial, misconfigured, or missing on exactly the account the attacker used. “MFA is on” is not the same as “MFA is on everywhere it matters.” Check every access point, including the backup console and the old VPN account nobody uses.

2. Patch promptly, starting with what faces the internet. Keep operating systems, applications, firewalls, and VPN appliances updated, and prioritise anything reachable from the internet. When a vendor publishes a critical patch, apply it within days, not months — attackers scan for newly published flaws within hours, because the patch announcement tells them exactly where to look. End-of-life software that receives no patches at all should be replaced or isolated; every flaw found in it is permanent.

3. Endpoint protection that watches behaviour. Modern endpoint detection and response tools watch for suspicious behaviour — a program encrypting files at speed, a process disabling backups — and can isolate an infected device automatically. Traditional antivirus that only matches known file signatures is not enough against ransomware, which changes constantly. If you run a small business, this is the one paid product in the list that is genuinely worth budgeting for.

4. Segment the network. A user device should not be able to reach your critical servers directly. Separate your network so that an infection on one laptop cannot walk to the file server, the backups, and the domain controller. The test is the same as for IoT devices: if this machine were fully compromised tomorrow, what could the attacker reach? The answer should be as small as possible.

5. Backups attackers cannot reach — and test them. Keep several copies of your data, including one offline or unchangeable copy that ransomware cannot encrypt or delete, and test that you can actually restore from it. The 3-2-1 rule is the standard: three copies, on two different types of media, with one copy off-site or isolated. The untested backup is the classic ransomware tragedy — organisations discover during an attack that their backups were connected to the same network, encrypted along with everything else, or had silently stopped working months ago. A restore test every quarter is not optional; it is the control that decides whether you pay.

6. Train people on the one email. Security awareness training helps, but keep it focused: the phishing email with a malicious attachment or link is the single most common entry point. Teach the team to treat unexpected attachments, urgent payment requests, and password-reset emails as suspicious by default, and give them a one-click way to report a suspicious message. Training that tries to cover everything covers nothing; the phishing email is the threat that matters most here.

If you are hit: the first hours

Speed matters, but panic makes it worse. Work this sequence, in order, and do not skip ahead to restoring files — restoring onto a system the attacker still controls just re-encrypts them.

Isolate, do not switch off. Disconnect affected devices from the network and Wi-Fi immediately, so the ransomware cannot spread to other machines. Avoid switching them off unless your IT team or incident responders advise it — a powered-off machine loses evidence in memory, and some ransomware encrypts faster on restart. If several machines are affected, take the network offline at the switch level.

Protect the backups. Disconnect backup systems and lock their admin accounts before the attacker finds them. This is the step people forget, and it is the step that decides whether recovery is possible without paying. Check that backups are intact before you touch anything else.

Call for help and report it. Contact your IT team or an incident-response provider, and report the attack to law enforcement — in the US, the FBI’s Internet Crime Complaint Center (IC3), and CISA. Reporting is not just paperwork: it connects you to guidance, and in some jurisdictions it is a legal requirement. Preserve the ransom note and do not delete files or wipe devices yet — both are evidence, and the note identifies the ransomware variant, which determines whether a free decryption tool exists.

Do not pay yet — and probably not at all. CISA and the FBI advise against paying. Payment does not guarantee decryption, does not guarantee stolen data will be deleted, and in some cases paying an attacker on a sanctions list is itself illegal. Before any payment is even considered, check whether a free decryption tool exists for your variant (the No More Ransom project, run by Europol with security vendors, is the place to check) and whether your backups actually work. Most organisations that recover without paying do so because of the backups in step 5 above — which is why that step comes first in this article and last in most people’s priorities.

Recovery: the sequence that actually works

Once the attack is contained, recovery follows a clear order. Rushing it lets the attacker straight back in.

1. Investigate. Work out how the attackers got in, what they touched, and whether data was stolen. This is not optional curiosity — if you do not know the entry point, you cannot close it, and the same attacker can return through it next week.

2. Remove. Delete the malware, remove hidden accounts and tools the attacker planted, and fix the weakness they used. Check for persistence mechanisms — scheduled tasks, new admin accounts, remote-access tools installed during the attack. A machine that has not been properly cleaned will be re-encrypted.

3. Restore — only after the entry point is closed. Restore from clean backups, starting with the most critical systems, and verify the restored data before bringing systems back online. Only 16% of organisations in the Sophos 2026 survey fully recovered in less than a day, and 55% within a week — recovery is measured in days, not hours, and anyone promising faster is selling something.

4. Review and harden. After recovery, do the post-incident review: which control failed, what would have stopped it, and what changes now. Every ransomware attack is a free audit of your security, paid for in the worst possible currency — use the findings.

The readiness checklist

If you do nothing else this week, answer these ten questions honestly. Every “no” is a mitigation task.

  1. Is multi-factor authentication on every access point, including backups and VPN?
  2. Are critical patches applied within days, especially on internet-facing systems?
  3. Do you have an offline or immutable backup copy, and was a restore tested in the last three months?
  4. Can a compromised laptop reach your file server and backups directly?
  5. Does your endpoint protection watch behaviour, or only match known files?
  6. Is there a written incident plan, and does everyone know the first three steps?
  7. Can staff report a suspicious email in one click?
  8. Are former employees’ and vendors’ accounts disabled?
  9. Do you know whether a free decryption tool exists for the common ransomware variants?
  10. Has anyone practised the recovery — not just written the plan, but run it?

Ten yeses will not make ransomware impossible. They will make it survivable, which is the honest goal of mitigation: the attack may still happen, but it will not decide whether your business continues.

FAQ

What is ransomware mitigation?

Mitigation means reducing the risk and impact of ransomware: preventing attacks with controls like multi-factor authentication and patching, limiting how far an attack spreads with network segmentation, and recovering without paying through tested, offline backups. No single product provides it — it is a combination of controls plus a plan.

Can ransomware be prevented completely?

No — no organisation can guarantee it will never be hit. The honest goal is to make an attack unlikely and survivable: close the common entry points, and make sure that if encryption happens, you can restore from backups the attacker cannot reach.

Should I pay the ransom?

CISA and the FBI advise against paying. Payment does not guarantee your files back or that stolen data will be deleted, and it marks you as a payer. Check for a free decryption tool first (the No More Ransom project) and restore from clean backups after closing the attacker’s entry point.

What should I do first if ransomware hits?

Isolate the affected devices from the network without switching them off, protect your backups by disconnecting them and locking their admin accounts, then call for help and report the attack. Do not delete files, wipe devices, or start restoring until the entry point is found and closed.

How long does ransomware recovery take?

In Sophos’s 2026 survey, only 16% of organisations fully recovered in less than a day, while 55% did so within a week. Recovery is measured in days, not hours — which is why tested backups and a written plan matter more than any single security product.

Similar Posts