Most cyber insurance applications look like paperwork. At claim time, that paperwork becomes evidence. Carriers and breach coaches go back to what you said you were doing, then compare it to what your tools, logs, and vendors show in reality.

This is where many organizations get surprised. The issue isn’t just “Do you have cyber insurance?” It’s: Can you prove you ran your environment the way your application says you did?

From “We’re Covered” to “We’re Conditionally Covered”

Cyber insurance in 2026 is closer to a performance‑based contract than a blanket safety net. Coverage depends on two things:

  • Having baseline controls in place (MFA, backups, EDR, patching, email security, IR, vendor oversight).
  • Being able to demonstrate that those controls were actually enforced when the incident occurred.

If your environment has drifted from the story the application tells—especially around MFA, backups, and privileged access—you’re carrying hidden claim risk.

The Controls Carriers Actually Check

When a claim is filed, investigators typically focus on a short list of control areas. Expect questions and evidence requests around:

1. Multi‑Factor Authentication (MFA)

They’ll want to know:

  • Which systems require MFA: email, VPN, remote access tools, admin interfaces, financial apps.
  • Whether the specific users involved in the incident were protected by MFA.
  • How MFA was configured and enforced (policies, groups, exceptions).

Evidence usually includes MFA policy screenshots, enforcement reports, and sign‑in logs.

2. Backups and Recovery

It’s not enough to say “we have backups.” Carriers care about:

  • Backup frequency and scope for critical systems.
  • Protection of backups (immutable, off‑network, or otherwise isolated).
  • Whether restore tests are performed, and how recently.

Expect to provide backup job reports and documentation from your last restore tests.

3. Endpoint Detection and Response (EDR)

Modern endpoint protection is assumed. Investigators will ask:

  • Which endpoints and servers are covered by EDR/AV.
  • Whether alerts were generated before or during the incident.
  • How those alerts were triaged and handled.

Coverage reports and basic alert histories are often requested.

4. Patching and Vulnerability Management

Unpatched, internet‑facing systems are a common root cause. Carriers look for:

  • Regular vulnerability assessment of external and critical internal assets.
  • Reasonable timelines for patching critical and known‑exploited vulnerabilities.
  • Evidence that high‑risk issues are tracked and closed.

Reports from patching or vulnerability tools become part of the file.

5. Email Security and Phishing Controls

Because so many incidents start in inboxes, you’ll get questions like:

  • What filters and advanced protections (URL/attachment scanning, impersonation detection) are in place.
  • How users report suspicious messages.
  • How malicious messages are removed across the tenant.

These controls show you took reasonable steps to manage a primary entry point.

6. Incident Response Planning and Testing

Your incident response (IR) process matters as much as your tools. Carriers ask:

  • Is there a written IR plan with roles, contacts, and escalation paths?
  • Does the plan define when and how to notify the insurer and broker?
  • Has the plan been exercised in a tabletop or live event?

IR plans and test notes help show the incident was handled responsibly.

Policy Promises vs. Operational Reality

The biggest risk isn’t having no controls; it’s overstating what you do.

Common gaps:

  • The application says “MFA everywhere,” but executives or legacy systems were excluded.
  • Backups are configured, but jobs have failed for weeks or never include specific systems.
  • EDR is deployed, but high‑risk laptops or servers were never onboarded.
  • Vendors gained access to data without updated security review or contracts.

These discrepancies tend to surface under pressure—during the claim, not during renewal.

Turning Carrier Expectations into an Operational Checklist

You don’t need a giant governance program to improve. Start with:

  • Extract your policy’s control language. Highlight everything tied to MFA, backups, EDR/AV, patching, IR, and vendors.
  • Map requirements to systems and owners. Decide who is responsible for each control and which systems are in scope.
  • Define what “proof” looks like. For every control, specify the report, log, or screenshot that demonstrates it’s enforced.
  • Review quarterly. Treat this like a financial review: confirm controls, review exceptions, and update evidence.

Where Inceptus Fits

Inceptus helps translate dense policy language into a short, actionable controls list. Then we help you operationalize it so you’re not scrambling for proof during a claim.

If you want an executive‑level view of how your real posture compares to what your policy assumes, book a 15‑minute Policy Review call and we’ll walk through it with you and your leadership team.