Security News

Cyber Insurers Now Want Proof You Can Recover, Not Just a Green Backup Light

The Register · 19 Nov 2026
Key Takeaway Run a documented test restore with business owner sign-off, so you can show an insurer that recovery works rather than relying on a green backup status.

Cyber insurance pricing has cooled. Marsh's Global Insurance Market Index shows global cyber rates falling for a 13th consecutive quarter. Part of the reason is that carriers are imposing stricter requirements that decide whether a business qualifies at all. One major global carrier recently stopped writing law firms because of claims volume, and brokers expect healthcare and managed service providers to be next.

The familiar requirements still apply: multifactor authentication on external access and privileged accounts, endpoint detection and response on every endpoint, a staffed 24/7 team where managed detection and response is required, and timely patching. Backup is now joining that list. Attackers target backup systems to make ransomware more effective, and an untested restore can re-infect the network. Insurer Beltex described an MSP that restored a client straight from backup without involving the insurer. The attackers were still present, and the ransom reportedly doubled. Some carriers now want evidence of a successful restore within the last six months, and some applications must be signed by a C-level executive.

Speed matters too. In one example, an 85-person firm hit through a zero-day firewall flaw had the intrusion contained in about 20 minutes and was fully functional within 36 hours, with a claim of around $85,000. By contrast, a firm billing $10,000 a day that is offline for a week loses $70,000 in income, and large servers can take four to 24 hours to restore. Breach counsel treats the first 72 hours as critical, so restoring into production too early risks reintroducing the threat and disturbing forensic evidence. A clean, separate place to recover to is part of the bar.

The advice is to run a test restore, confirm everything that matters is protected (including servers labelled "not in production"), have the business owner confirm recovery time and recovery point objectives were met, and keep logs, screenshots and sign-off. The article is partner content from N-able, which promotes its Cove cloud disaster recovery product.

Why it matters

The assumption that a successful backup job equals recoverability is being broken by claims experience, and underwriters now treat untested restores as a lack of reasonable care. Businesses that restore straight into production risk reinfection and lost forensic evidence, so a clean recovery location becomes a planning decision rather than an afterthought. Leaders also face personal accountability, as some applications must be signed by a C-level executive.

What to do

  • Run a test restore and record logs, screenshots and business owner sign-off in your ticketing system.
  • Set recovery time and recovery point objectives for the systems you could not lose for 72 hours.
  • Check that every server is backed up, including any labelled "not in production".
  • Disconnect affected machines from the network rather than powering them off during an incident, so forensic data survives.
cyber insurance backup and recovery ransomware incident response SMB
Regulated in financial services? APRA CPS 220, 230 and 234, in plain language ->

Summarised by CISO AI from The Register, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.