How Ransomware Recovery Services Work: What to Expect After an Attack

Photo of author

By Markus Winkelhock

What a ransomware recovery service actually does

Ransomware recovery services are outside specialists you hire after your files have been encrypted and a ransom note is on the screen. They do four jobs, usually in this order: contain the attack, work out how the attackers got in, restore your systems, and help you prove to regulators and insurers what happened.

Some firms do all four. Others do only one or two. Knowing which you're buying matters more than the brand name on the invoice.

The first 24 hours

Speed matters, and so does not panicking.

Disconnect affected machines from the network. Pull the cable or disable Wi-Fi. Don't power them off if you can avoid it, because memory can hold evidence of how the attackers got in, including encryption keys in some cases. Isolate, don't wipe.

Then call, in this order: your cyber insurer (if you have one), your lawyer, and then a recovery firm. Many policies require you to use their approved responders. If you hire your own first, you may not get reimbursed.

Don't reboot servers. Don't reinstall anything. Don't email the attackers from your regular account.

What the work looks like

Here's what a competent team will do over the following days.

Containment. They find every infected system and every account the attackers control. Attackers often sit inside a network for days or weeks before they encrypt anything, so the machine showing the ransom note is rarely the only compromised one.

Forensics. They determine the entry point. Common ones are stolen remote-access credentials, an unpatched VPN appliance, and a phishing email. If you skip this step and restore anyway, the attackers can walk back in through the same door.

Restoration. They rebuild from clean backups, in a sensible order: identity systems first (Active Directory or its equivalent), then the applications the business can't run without, then everything else.

Reporting. They produce a timeline you can hand to your insurer, your auditors, and, where required, regulators.

What it costs

These are rules of thumb from what the market commonly charges, not measured averages. Prices vary a lot by region and firm.

  • Hourly incident response rates: roughly $250 to $600 per hour per responder.
  • A small business with a handful of servers: often $15,000 to $75,000 all in.
  • A mid-sized company with dozens of servers and a domain compromise: $100,000 to $500,000 or more.
  • Retainers, which you pay before anything happens, often run $5,000 to $50,000 a year depending on the hours included.

Many insurance policies cover a large share of response costs, which is another reason to read yours before you need it.

Should you pay the ransom?

Recovery firms can negotiate with attackers and handle the payment, and some do it often. That doesn't mean paying is a good idea.

Payment doesn't guarantee a working decryptor. Even when you get one, it can be slow and may corrupt large files. You also have no assurance the attackers deleted the data they stole. And paying may be illegal if the group is on a sanctions list, which is something to check with a lawyer before any money moves.

My view: treat payment as a last resort for when backups are gone and the business can't survive without the data. If you have clean, tested backups, restoring is almost always faster and cheaper than waiting on criminals.

Backups decide everything

Your recovery bill is mostly a function of your backups.

Follow the 3-2-1 rule: three copies of your data, on two kinds of storage, with one copy offline or immutable. Attackers now go after backup servers first, so a backup sitting on the same network with the same admin password isn't really a backup.

Some practical numbers:

  • Back up critical systems at least daily. Databases that change constantly may need hourly.
  • Test a full restore at least twice a year. A backup you've never restored from is a guess.
  • Keep at least 30 days of retention, and ideally 90. Attackers can be inside long before they strike, and you may need a copy from before they arrived.

A restore test costs a few hours of staff time. Finding out your backups are corrupted in the middle of an attack costs far more.

How to choose a provider

Ask these questions before you need to ask them under pressure.

Are they on your insurer's panel? If yes, the paperwork is easier.

What's their response time? Good firms promise contact within one to four hours, around the clock. Ask for it in writing.

Do they do forensics and restoration, or just one? Splitting the work between firms is fine, but someone has to coordinate.

Can they name the kinds of cases they've handled? You want experience with your size of company and your type of systems, whether that's Windows domains, cloud environments, or medical or industrial equipment. Don't expect client names, since confidentiality is normal.

Who actually shows up? Some firms sell with senior people and staff with juniors.

I'd choose a firm that works with your insurer over a bigger name that doesn't. The coverage matters more than the logo. And I wouldn't bother with any provider who guarantees data recovery before looking at your systems. Nobody can promise that honestly.

A retainer is worth it for most mid-sized companies

If you have more than about 50 employees or hold data that would be costly to lose, a retainer pays for itself. You get a signed contract, agreed rates, and a phone number that gets answered. Without one, you may spend the first critical day negotiating terms while the attackers keep working.

Under that size, a retainer is harder to justify. A good insurance policy with a response hotline and solid backups gets you most of the benefit.

What to do this month

Don't wait for an incident to find the gaps.

  1. Find your insurance policy and note the incident hotline number.
  2. Print a one-page contact list: insurer, lawyer, recovery firm, key staff. Keep it offline, because your email may be down.
  3. Check that at least one backup copy can't be reached with your everyday admin credentials.
  4. Turn on multi-factor authentication for remote access and for all administrator accounts.
  5. Schedule a restore test.

None of this is exciting. It's also what separates a bad week from a business-ending one.

The short version

Ransomware recovery services contain the attack, find the cause, rebuild your systems, and document what happened. Their bill depends heavily on how well your backups hold up. Pick a provider before you need one, check what your insurer requires, and test your restores. Paying the ransom should be the exception.

Leave a Comment