What a recovery wallet actually is
People use the phrase two ways. Some mean a cryptocurrency wallet, funded in advance, so you can pay a ransom quickly. Others mean a pool of money and access you can draw on the day files start renaming themselves.
I'll cover both, but I'll say up front which one I think is worth your time. It's the second.
Why I wouldn't pre-fund a crypto wallet
Keeping a few Bitcoin parked "just in case" sounds practical. In most cases it isn't.
First, you don't know the price. Demands vary enormously with the size of the victim and the gang, and there's no fixed figure I can hand you. A wallet funded for $20,000 is useless against a $400,000 demand and overkill against a small one.
Second, the coin itself moves. Hold crypto for two years and you carry price swings the business never asked for. Your accountant will also have opinions about how it's recorded.
Third, and most important, paying doesn't get you back to normal. Decryption tools handed over by criminals are often slow and sometimes corrupt large files. You still have to rebuild, because you can't trust machines the attacker has been inside. Paying can also leave you exposed to a second demand, since the attackers may have copied your data before encrypting it.
Fourth, there's the legal side. The US Treasury's Office of Foreign Assets Control (OFAC) has published advisories warning that paying a sanctioned group can create liability, even if you didn't know who they were. Other countries have their own rules. You want a lawyer and a negotiator involved before any payment, not a wallet that makes it feel like a casual option.
If a board member insists on holding crypto for this purpose, keep it small and treat it as the last line of a plan, not the first.
What to fund instead
Here's what I'd put money into, in order.
1. Backups the attacker can't touch. This is the thing that makes a ransom irrelevant. Cloud object storage with object lock (immutability) runs roughly $6–$25 per terabyte per month depending on the provider. A small business with 2 TB of important data is looking at about $12–$50 a month. That's the best return on this whole list.
2. Cyber insurance. For a small company, a policy with around $1 million in coverage often lands in the low thousands of dollars per year. Treat that as a rule of thumb, not a quote. Premiums swing with your industry, revenue and security controls. Insurers now ask about multi-factor authentication and backups, and they'll decline or raise rates if you lack them.
3. An incident response retainer. A retainer with a firm that does forensics and negotiation means someone answers the phone at 2 a.m. Many are structured as prepaid hours, commonly 20–40 hours, and some insurers include one. If yours does, find out who it is and save the number somewhere that isn't your own network.
4. A cash reserve. Even with insurance there are deductibles, and not everything is covered. A rule of thumb I like: enough to cover two to four weeks of operating costs for the systems you can't live without. It's not a measured figure, it's a way of forcing you to decide what "can't live without" means.
The backup numbers that matter
Some specifics you can act on this week.
- Frequency: Daily for file servers and most business systems. Hourly, or continuous log shipping, for databases where losing half a day of orders would hurt.
- Retention: Keep at least 30 days, ideally 60–90. Attackers often sit in a network for days or weeks before triggering encryption. If your oldest backup is seven days old, it may already contain their tools.
- Copies: The 3-2-1 rule is the standard: three copies, on two kinds of storage, one offsite. Add one more condition: one copy must be immutable or offline.
- Restore tests: Restore a sample of files monthly. Restore a whole critical system at least twice a year. A backup you've never restored is a hope.
- Recovery time: Time the restore. If bringing back your main server takes 36 hours and the business can survive 8, you've found the gap before an attacker did.
Don't bother with a backup system that's reachable with the same admin password as your everyday network. Attackers go after backup consoles first. Use separate credentials with multi-factor authentication.
Build the recovery kit
The other meaning of "wallet" is more literal. Put together a folder, paper and offline, that you can pick up when the network is gone.
It should hold:
- The incident response firm's phone number and your policy number
- The insurer's claims hotline (many require notice before you hire anyone)
- Contact details for your lawyer, and for IT staff or your managed provider
- A list of your critical systems in restore order
- Admin credentials for backup storage, kept offline
- Contact details for the local FBI field office or your national cybersecurity agency
- A printed copy of your network diagram
Print it. Put a copy in a sealed envelope in a safe place. When ransomware hits, the shared drive with your response plan is probably encrypted too.
Check for free decryptors first
Before anyone discusses money, check No More Ransom (nomoreransom.org), a project run by Europol, the Dutch police and security companies. It hosts free decryption tools for a number of ransomware families. It won't cover every strain, and newer ones often aren't there, but it takes ten minutes and sometimes ends the problem.
Don't delete the encrypted files either. Even if no tool exists today, one can appear later.
If you do end up considering payment
Some businesses will face a situation where backups failed and the choice is pay or close. I won't pretend that never happens. If you're there, the order matters:
- Call your insurer and your lawyer.
- Bring in a negotiator, normally through the response firm, who will also check sanctions exposure.
- Ask for proof of decryption on a few files.
- Let the professionals handle the purchase. Buying crypto takes time, often a day or more at a regulated exchange, since the exchange will have identity checks and limits for large amounts.
A pre-funded wallet shaves a day off that last step. It does nothing for the other three, and those are where the costs pile up.
A sensible starting plan
If you've done none of this, spend your first month like so:
- Week 1: Turn on multi-factor authentication for email, remote access and backup consoles.
- Week 2: Set up an immutable backup copy and run a first restore test.
- Week 3: Get insurance quotes, and ask what each insurer requires.
- Week 4: Sign an incident response retainer or confirm the one that comes with your policy, then print the recovery kit.
Total cost for a small organization is often well under $500 a month, plus the insurance premium. That's a rough range. A larger one will be higher.
The best recovery wallet is the one you never have to open for a criminal. Spend the money on being able to say no.