A cyber-insurance application is a signed claim about your security controls. Every “yes” is a representation: that multi-factor authentication is enforced, that backups are tested, that endpoints are covered. At least one carrier has gone to court to rescind a policy over a multi-factor-authentication answer that didn’t hold up. Almost nobody lies on an application. The failure is answering from intent — “we’re rolling MFA out” — instead of from what is deployed today.
This article walks through what underwriters and claims adjusters accept as proof for the answers applications ask most, and which answers most often fail under scrutiny. We are not an insurer, a broker, or an agent, and we never advise on coverage, limits, or carriers. We review the evidence. You answer. You sign.
What counts as proof
Underwriters and claims adjusters don’t accept policies as proof. They accept evidence of controls in operation. For each common application area, the proof looks like this:
| Application area | What proves it |
|---|---|
| MFA on email, remote access, and privileged accounts | Configuration exports showing enforcement, plus an inventory of privileged accounts — not a policy stating MFA is required |
| Endpoint protection (EDR) on every endpoint | A coverage report from the EDR console showing every endpoint, including the ones that haven’t checked in |
| Backups offline or immutable, with restore tests | A dated record of a successful restore, not just a backup job log |
| Patching within a stated target | Patch reports showing time-to-patch for critical vulnerabilities against the target you claimed |
| Email security (DMARC, SPF, DKIM) | DNS records and enforcement status, not the intent to configure them |
| Incident response plan, exercised | The plan plus a record that it was walked through — a date, attendees, and notes |
| Training | Completion records, not a training policy |
| Vendor review | A record of reviews actually performed, with dates |
The answers that most often don’t hold up
- “MFA is enforced on all privileged accounts.” The usual gap: a handful of admin accounts — service accounts, break-glass accounts, a vendor’s account — that were never enrolled. The application asked about every admin account. The evidence has to cover every admin account.
- “EDR is deployed on all endpoints.” The usual gap: endpoints that exist but never check in — a warehouse PC, a laptop in a drawer, a server nobody patched. A coverage report that shows 94% is a “no” with an explanation, not a “yes.”
- “Backups are tested regularly.” The usual gap: backups run, but nobody has restored from them. A restore test is a dated event with a result. A backup job completing is not a restore test.
- “We have an incident response plan.” The usual gap: a plan exists but was never walked through, and nobody knows who calls whom. An unexercised plan is a document, not a capability.
How to approach the renewal
- Answer from evidence, not from memory. For each question, find the artifact before answering. If the artifact doesn’t exist, the honest answer is “no” or “partially” — and the fix list starts there.
- Fix the quick wins first. MFA enrollment gaps and stale endpoints are usually fixable in days. The ranked fix list separates quick wins from projects so the renewal isn’t held hostage by the longest item.
- Keep the file. The evidence you gather for this renewal is the starting point for the next one. A dated file, kept current through the year, turns next year’s application from a scramble into a review.
