Cyber Insurance Requirements 2026: What Your Policy Actually Demands
BJ Pote
CEO, eTop Technology
Here’s something that keeps me up at night on behalf of our clients. Businesses paying $15,000 to $50,000 a year for cyber insurance, thinking they’re covered, and then finding out after an incident that their claim is denied because they weren’t actually meeting the policy requirements.
This is not theoretical. It’s happening right now. Cyber insurers got burned badly in 2020 and 2021 paying out massive ransomware claims. They responded by getting extremely specific about what security controls you need to have in place. And in 2026, they’re enforcing those requirements aggressively.
What Changed with Cyber Insurance
Five years ago, getting cyber insurance was like getting any other business policy. Fill out an application, answer some basic questions, write a check. The application might ask “Do you have antivirus?” and you’d check yes and move on.
Those days are gone. Today’s cyber insurance applications look more like security audits. They’re 10 to 15 pages long, and they ask very specific technical questions. And here’s the critical part: your answers become warranties. If you say you have MFA on all remote access and you don’t, that’s not an oversight. That’s grounds to deny your claim.
Insurers have hired cybersecurity experts. When you file a claim, they don’t just take your word for it. They bring in forensic investigators who will check exactly what controls were in place at the time of the incident. If reality doesn’t match what you attested to on your application, you’re on your own.
The Core Requirements in 2026 Policies
While every insurer is slightly different, here’s what nearly all of them are requiring this year.
Multi-Factor Authentication (MFA)
This is the number one item. Every major cyber insurer requires MFA on:
- All remote access (VPN, remote desktop, cloud applications)
- All email access
- All privileged/administrative accounts
- Any system accessible from the internet
Note what they’re saying here. Not “we recommend MFA.” Not “MFA on some systems.” They want MFA on all remote access and all admin accounts. If your domain admin account doesn’t require MFA, you have a gap that could sink a claim.
We had a prospect come to us after their claim was denied. They had MFA on their email. But their remote desktop server, which is how the attacker got in, was accessible with just a username and password. Their insurer pointed to the application where they attested to MFA on “all remote access points” and denied the $400,000 claim. That business nearly didn’t survive.
Endpoint Detection and Response (EDR)
Traditional antivirus is no longer sufficient for most policies. Insurers are specifically asking whether you have EDR deployed across all endpoints and servers. Some are even asking which EDR product you use, because they know certain products are more effective than others.
EDR requirements typically include:
- Deployed on all workstations and servers
- Managed by a qualified team (not just installed and ignored)
- Connected to a monitoring service or SOC (Security Operations Center)
- Capable of automated isolation and response
If your “endpoint protection” is Windows Defender or an outdated Norton subscription, that will not satisfy a 2026 cyber insurance policy.
Backup and Recovery
Insurers know that good backups are the difference between a business surviving ransomware and a business paying the ransom (or closing). Requirements typically include:
- Regular backups of all critical systems and data (daily minimum)
- Offsite or cloud backups that are physically separate from your network
- Immutable backups that can’t be modified or deleted by ransomware (this is newer and increasingly required)
- Tested recovery with documented proof that you’ve actually restored from backup successfully
That last point trips up a lot of companies. You have backups running. Great. Have you ever tested a full restore? Can you prove it? Insurers want documentation showing regular recovery testing, not just backup job success logs.
Privileged Access Management
Insurers are asking how you control administrative access. They want to see:
- Separate admin accounts (not using your regular email account as a domain admin)
- Limited number of people with elevated access
- Regular access reviews
- No shared credentials or generic admin accounts
Patch Management
You need to demonstrate a consistent process for applying security patches. Most policies require:
- Critical and high-severity patches applied within 14 to 30 days
- A documented patch management policy
- Evidence of patch compliance across your environment
Security Awareness Training
Nearly all policies now require employee security awareness training. This means:
- Regular training (at least annually, quarterly preferred)
- Phishing simulation testing
- Documented completion records
Incident Response Plan
This is the one most small businesses don’t have, and it’s a requirement. You need a written incident response plan that covers:
- Who to call and in what order
- How to contain an active breach
- Communication protocols (internal and external)
- Regulatory notification requirements
- Your insurance carrier’s notification requirements (there’s usually a specific hotline and a time limit)
We have a full breakdown of how to build one in our incident response planning guide.
How Claims Get Denied: Real Scenarios
Scenario 1: The MFA Gap. A logistics company had MFA on email but not on their VPN. Attackers came in through the VPN, deployed ransomware, and encrypted everything. The insurer reviewed the application where the company attested to “MFA on all remote access” and denied the claim. Total loss: $750,000 in ransom, recovery costs, and lost business.
Scenario 2: The Unmanaged EDR. A medical practice purchased an EDR product but never configured it properly and had no one monitoring the alerts. The EDR actually detected the initial stages of the attack and generated alerts. Nobody saw them. The insurer argued that having EDR deployed but unmonitored was equivalent to not having it, since the policy required “managed endpoint detection and response.” Claim denied.
Scenario 3: The Untested Backup. A construction company had backups. On paper, everything looked great. When ransomware hit and they needed to restore, they discovered their backup jobs had been failing for three months. Nobody had checked. The insurer’s forensic team found this during their investigation. While the claim wasn’t fully denied, the payout was reduced by 60% due to “failure to maintain adequate backup systems as attested.”
What You Should Do Right Now
Step 1: Read Your Actual Policy
Not the summary. Not the certificate. The actual policy document with the security requirements and warranties. If you don’t have it, call your broker and get it. Specifically look for the “Security Controls” or “Minimum Requirements” section.
Step 2: Do a Gap Analysis
Take every requirement in your policy and honestly assess whether you meet it. Not “we’re working on it.” Not “we plan to.” Do you meet it today, right now, in a way that would survive a forensic investigation?
Common gaps we find:
- MFA not enforced on all admin accounts
- EDR not deployed on servers (only on workstations)
- Backups not immutable or not tested
- No written incident response plan
- Security training done once and never repeated
- Patches more than 30 days behind
Step 3: Fix the Gaps Before Renewal
If you find gaps, fix them before your policy renews. If you’re mid-policy and discover you attested to something you’re not actually doing, get it in place immediately. The worst outcome is filing a claim and discovering the gap during the investigation.
Step 4: Document Everything
Insurers want proof. Keep records of:
- MFA enrollment status for all users
- EDR deployment reports showing coverage across all endpoints
- Backup job logs and recovery test results
- Patch compliance reports
- Training completion certificates
- Your incident response plan with a revision date
Step 5: Partner with an IT Provider Who Understands Insurance Requirements
This is where a good managed IT services partner makes a massive difference. We align our security stack and documentation to what insurers require because we’ve been through enough claim investigations to know exactly what they look for. When our clients file claims, they get paid, because we can produce the evidence that the controls were in place.
The Cost of Getting This Wrong
Let me put some numbers on it. A mid-size business might pay $20,000 a year for cyber insurance. A ransomware incident could easily cost $500,000 to $1 million in ransom, recovery, lost revenue, legal fees, and regulatory fines.
If your claim gets denied because you weren’t meeting the policy requirements, you just spent $20,000 a year on a policy that gave you nothing when you needed it most. That’s not insurance. That’s an expensive piece of paper.
The security controls insurers require aren’t arbitrary. They’re the same controls that actually prevent and limit breaches. Meeting your insurance requirements and having genuinely good cybersecurity aren’t two different things. They’re the same thing.
Get Ahead of This
If you’re not sure whether your current security posture meets your cyber insurance requirements, we can help. Our security assessment maps directly to the controls insurers require and shows you exactly where you stand. No guessing, no surprises, and no denied claims down the road.
Schedule a free assessment today. Your future self, and your insurance carrier, will thank you.
BJ Pote
CEO, eTop Technology
eTop Technology has spent over 15 years in IT and over 12 years serving the Inland Empire as a trusted managed IT provider. We host the Business Tech Playbook podcast and are passionate about helping business leaders make smarter technology decisions.