
As carriers tighten underwriting, a backup job marked green is no longer enough. Here’s the evidence underwriters expect
Cyber insurance pricing has cooled. Marsh’s Global Insurance Market Index shows global cyber rates falling for a 13th consecutive quarter, with US rates recently stabilizing after the ransomware-driven spikes of 2020 and 2021.
Part of the reason rates are lowering is because carriers are imposing stricter requirements that determine if you will qualify at all. A major global carrier recently stopped writing law firms altogether because of claims volume, and brokers expect healthcare and managed service providers (MSPs) to be next.
The newest requirement is the one many MSPs are least ready for: proof that you can actually recover. This is what insurers really want to see, and meeting the bar is harder than it sounds.
Why insurers stopped taking backups on faith
In a recent webinar with cyber insurance provider Beltex, the familiar list of requirements came up first:
-
Multifactor authentication (MFA) on external access and privileged accounts
-
Endpoint detection and response (EDR) on every endpoint
-
A staffed 24/7 team where managed detection and response (MDR) is required, and timely patching.
Backup is now joining that list, and for good reason. For years it was assumed that having backups and a green job status was good enough. Claims have shown otherwise.
Now, attackers go after backup infrastructure to make their ransomware more effective, and an untested restore can re-infect the production network. Beltex described an MSP that restored a client directly from backup without involving the insurer. The attackers were still in the environment, and the ransom reportedly doubled.
So, carriers are asking for proof. Some want evidence of a successful restore within the last six months, and some insurance applications must be signed by a C-level executive rather than the IT director to put ownership behind it.
Proof of speed matters as much as proof of recovery
Being able to recover is only half the question, because time is where claim costs balloon. Insurers, it turns out, don’t object to paying claims. They object to paying big ones.
Beltex’s favorite example involved an 85-person firm hit through a zero-day firewall flaw. Their MDR solution contained the intrusion in about 20 minutes, forensics confirmed two servers were touched, and clean backups had the firm fully functional within 36 hours. The claim came in at around $85,000.
Compare that with downtime and business interruption: a firm billing $10,000 a day that is offline for a week loses $70,000 in income before recovery costs and claim submission. Yet large servers can take four to 24 hours to restore. That is why underwriters care how fast you can come back and how successfully.
Where you recover is the other half
Speed raises a second problem: where do you restore to? Breach counsel treats the first 72 hours as the most critical window, and incident response (IR) teams need to isolate and investigate infected systems during it.
Restoring into production too early risks reintroducing the threat and disturbing the evidence investigators need. Waiting for a safe place has the clock running. Recovery that is fast but not safe doesn’t satisfy anyone.
Meeting all of this is harder than it looks
Put the pieces together and the bar is high:
-
Backups you have actually tested
-
Recovery times you can state and meet
-
And a clean, separate place to recover to
Underwriters want to know whether you exercised reasonable care, so a row of green checkmarks won’t do. Run a test restore. Confirm you’re protecting everything that matters, including the server someone labeled “not in production.” Have the business owner, not just IT, confirm the right systems came back within agreed recovery time objectives (RTO) and recovery point objectives (RPO), and keep the logs, screenshots and sign-off in your ticketing system. It doesn’t need to resemble a government audit; Beltex noted that this alone puts you ahead of most organizations.
Where cloud disaster recovery fits
Cloud-native disaster recovery changes the equation. Cove’s DRaaS solution lets teams stage a pre-recovered VM in the N-able cloud that can be failed over to in about 15 minutes, off the production network. That answers the speed question and the location question together. Forensic investigators can validate and hunt in the sandbox while the business keeps moving, with rollback to earlier points in time. Once everyone agrees the recovery point is clean, workloads can run from the cloud over VPN, and failback uses recovery agents to bring changes home.
Where to start
Insurance is a financial failsafe, not a substitute for a bad data protection posture. Start by listing what the business couldn’t lose for 72 hours, set recovery targets, test them and document the results. Check the policy itself: a standalone cyber policy rather than a small add-on to a general one, with a limit of at least $1 million, and $2 million as the business scales. And if an incident does hit, disconnect affected machines from the network rather than powering them off, so forensic data survives.
N-able Cove Data Protection, recognized as a Champion in the Infotech 2026 Enterprise Backup Data Quadrant, provides cloud-native data protection for organizations. Learn more at n-able.com/products/cove-data-protection.
Contributed by N-able.