Cyber Insurance Application Evidence-Pack Builder
Underwriters no longer take your word for it — they ask for evidence: EDR coverage reports, MFA enforcement exports, the last backup-restore date, a pentest summary. Mark what you have, and get a submission-readiness read plus a copyable evidence-pack outline to take to your broker. Educational, not insurance advice; everything runs in your browser.
What this builder does
- Underwriters now ask for evidence, not just answers — EDR coverage reports, MFA enforcement exports, the last backup-restore date, a pentest summary, an EOL inventory.
- Mark what you have / partially have / are missing across ~13 evidence items and get a submission-readiness score plus how to obtain each missing artifact.
- Copy a ready-to-use evidence-pack outline (Markdown) to assemble with your broker before you submit the application.
- Educational checklist, not insurance advice. Everything runs in your browser.
Why this matters
The cyber application used to be a questionnaire; now it is an evidence request. Underwriters ask for the reports behind your answers, and the quality of that evidence pack shapes whether you are quoted, how fast, and on what terms. Just as important, the evidence is what protects you later — your answers are warranties, and the proof you kept is your defence if a claim is ever challenged as misrepresented.
Assemble the pack before you apply, not during a claim. This builder lists each artifact, scores your readiness, and tells you how to produce what is missing. Educational, not insurance advice.
Frequently asked questions
What evidence do cyber insurers ask for now?
Underwriting has shifted from "tick the box" to "show me." Common requests: an identity-provider export proving MFA is enforced on email, remote access and privileged accounts (with exceptions listed); an asset-vs-EDR report with the real coverage percentage; the date and result of your last backup-restore test plus proof of an immutable/offline copy; a recent penetration-test summary; an end-of-life inventory and external-exposure scan; measured patch-remediation times; a tested incident-response plan; awareness-training and phishing-simulation stats; logging/SIEM retention; privileged-access evidence; a segmentation diagram; and a reconciliation of prior incidents. This builder lists each artifact and how to produce it.
Why assemble an evidence pack before applying?
Three reasons. It speeds up underwriting and often improves terms, because a well-evidenced submission is a lower-uncertainty risk to price. It protects you at claim time: your application answers are warranties, and keeping the evidence that backs each one is your defence against a later misrepresentation challenge. And it surfaces your own gaps early — if you cannot produce the EDR coverage report, that is a control problem to fix before it becomes a decline or a denied claim. Preparing the pack turns the application from a guessing exercise into a documented one.
Does this collect or store my data?
No. It is a static, in-browser checklist. You mark each item have / partial / missing and it computes a readiness score and generates a Markdown outline locally. Nothing you enter is uploaded or stored. You then gather the actual evidence yourself and share it with your broker through whatever secure channel you normally use.
Is this insurance advice?
No. It is an educational checklist of the control evidence underwriters commonly request, to help you prepare a stronger, better-documented application. The exact evidence a given carrier wants varies. Confirm the specific requirements with your broker, and treat producing this evidence as good security hygiene regardless of insurance.
This tool is free and always will be. Would a Pro workspace — saved designs, team sharing and exports — be worth paying for?
Show me Pro →No account needed to use this tool — this just tells us whether Pro is worth building out.