- CFO
- CISO
What Will Your Cyber Insurer Ask You to Prove?
THE SHORT ANSWER
Most cyber insurers now set specific security controls as conditions of cover, such as multifactor authentication, endpoint detection and response, offline or immutable backups, and an incident response plan. At renewal, be ready to show that each control covers the whole business, with dated evidence, before you tick "yes" on the application.
On this page
A finance director is completing the cyber insurance renewal. One question reads: "Is multifactor authentication enforced for all remote access and email?" The IT manager says yes, and the box gets ticked.
Two months later, a review finds that an old remote access gateway and several shared service accounts were never covered. The application said "all."
Which controls do insurers usually ask about?
A September 2026 law firm review of carrier requirements says "The overwhelming majority of cyber insurers condition coverage on some combination" of these controls:
- Multifactor authentication (MFA)
- Endpoint detection and response (EDR)
- Immutable and offline backups
- Incident response plans
- External vulnerability scanning
- Privileged access management
- Email authentication (DMARC, DKIM and SPF)
- Security awareness training
- Network segmentation
- Patch management
The same review notes that "Requirements vary by carrier, industry, and policy form." It also says carriers ask policyholders to run recurring restore tests and keep dated records showing that recovery worked.
Why does a partial "yes" matter?
In 2022, Travelers asked a federal court in Illinois to rescind a cyber policy it had issued to International Control Services. Travelers alleged that the company had stated it required MFA for employees and third parties to access email, when MFA was in fact only used on its firewall. The two parties then agreed that the policy was "null and void, from its inception."
The lesson for anyone signing an application: a control that covers most of the business is not the same answer as a control that covers all of it.
What evidence should you have ready?
| Control | What the application usually asks | Evidence to have ready |
|---|---|---|
| MFA | Is it enforced for email, remote access and admin accounts? | An export of your sign-in policies, plus a written list of any exceptions and who owns them |
| EDR | Is it on every laptop and server? | A coverage report from the EDR console, with unprotected devices named |
| Backups | Are they offline or immutable, and tested? | The backup configuration and a dated record of your last successful restore test |
| Incident response plan | Do you have one, and has it been exercised? | The current plan and the date of the last exercise |
| Privileged access | Are admin accounts limited and monitored? | A list of admin accounts and how they are controlled |
| Email authentication | Are DMARC, DKIM and SPF in place? | Your published DMARC, DKIM and SPF records |
| Patching | How fast are critical patches applied? | A patch compliance report |
An incident response plan is stronger evidence when it also names which services come back first and how long the business can be without them.
Who should answer the application?
The person signing is often in finance, but the evidence sits with IT and security. Collect the evidence first, then complete the application. Where a control has exceptions, describe them instead of answering a blanket yes, and talk to your broker about how to word it.
Three checks you can run
| Check | What a pass looks like | What a fail looks like |
|---|---|---|
| For each "yes" on last year's application, can you produce dated evidence today? | A folder of current evidence, one item per control | Answers based on what IT believes is in place |
| Does MFA cover email, remote access and every admin account, with exceptions listed? | Exceptions written down, each with an owner and an end date | Unknown exclusions, such as old gateways or shared service accounts |
| Do you have a dated record of a successful restore test from the last 12 months? | A test record showing what was restored and how long it took | Backup job success reports only |
Questions we hear
Do all insurers require the same controls?
No. The law firm review notes that requirements vary by carrier, industry and policy form. Most carriers ask about the same core controls, such as MFA, EDR, backups and an incident response plan, but the detail and the evidence they expect differ. Read each question exactly as it is worded on your application.
What happens if we answer yes and the control only partly covers us?
You risk a dispute about cover when you most need it. In the Travelers case, the insurer alleged that MFA covered less than the application stated, and the policy was rescinded by agreement. Where a control has gaps, describe them accurately and ask your broker how to present them.
Who should own the evidence?
IT or security should hold the evidence for each control and refresh it before every renewal. Finance should not sign until that evidence exists. Keeping one folder per renewal year, with dated reports and screenshots, also makes the next application much faster to complete.
How does this connect to backup testing?
Directly. Carriers increasingly ask for proof that recovery works, not just that backups run. A dated record of a timed restore of a critical service is the strongest evidence you can give for the backup questions on most applications.
Sources
- National Law Review, The Tightening Gate: how cyber insurance carriers are raising the bar (September 29, 2026) (opens in a new tab)
- Reed Smith, Lessons from Travelers v. ICS (July 2022) (opens in a new tab)
- Insurance Journal, Travelers and ICS agree to rescind policy (August 30, 2022) (opens in a new tab)
- Marsh, Cyber resilience: twelve key controls (opens in a new tab)
