Cyber insurers used to ask a handful of questions. Today’s applications, and the ransomware supplements that often come with them, ask in detail about multi-factor authentication, endpoint detection and response, backups, patching, remote access and incident response. Someone at the client signs the answers. In practice it is usually their MSP who knows whether those answers are true. This free cyber insurance readiness checklist gives MSPs and in-house IT teams a structured way to prepare for a new application or a renewal. It scopes what the policy covers, checks each control that underwriters commonly ask about, collects the evidence that proves it, and closes any gaps before the application is signed. A conditional remediation phase appears when the review finds something missing, so the client’s signature is never the first time anyone notices.
Seven phases take the client from renewal notice to a signed, evidenced application. Phase 6 appears only when the review finds a control that is missing or only partly in place.
Start 60 to 90 days before the renewal date. Remediation takes longer than the application does.
Shown only when one or more controls are missing or partial. Conditional logic keeps it out of the way for a client who is already ready.
No two carriers use the same application, and requirements change with the size of the business, the industry and the limit being bought. The controls below come up on most applications and ransomware supplements. They are the ones broker and insurer guidance most often lists as expected, though no single carrier requires all of them in the same form. Treat the table as a preparation list, not as any carrier’s underwriting criteria, and always answer the questions on the actual form in front of you.
| Control | What applications commonly ask | Evidence to keep |
|---|---|---|
| Multi-factor authentication | Enforced for email, remote access and privileged accounts | Conditional access or MFA enforcement report; list of exceptions |
| Endpoint detection and response | Deployed on all endpoints and servers; whether it is monitored 24/7 | Agent count against the asset inventory; MDR or SOC contract if applicable |
| Backups | Frequency, an offline or immutable copy, restore testing | Backup job report; restore test record |
| Patching and end-of-life software | How quickly critical patches are applied; unsupported systems and how they are isolated | Patch compliance report; end-of-life register |
| Remote access | Remote desktop exposed to the internet; VPN with MFA | External scan; remote access inventory |
| Email security | Filtering, sender authentication, awareness training | DMARC record; training and phishing simulation reports |
| Privileged access | Separate admin accounts; who has domain or global admin rights | Privileged account inventory |
| Incident response | A written plan; whether it has been tested | Plan with version date; tabletop exercise record |
In the UK, the National Cyber Security Centre’s cyber insurance guidance suggests organisations should expect to give insurers information about their security controls, and notes that recognised certifications such as Cyber Essentials can help. UK organisations with a turnover under £20 million that certify their whole organisation to Cyber Essentials are also entitled to cyber liability cover through the scheme. The NCSC is also clear that insurance does not replace security controls: it pays for recovery, it doesn’t prevent the attack.
Each control is a task, and the MFA report, EDR export or restore test record is attached to the task it proves. When the broker, the carrier or a claims adjuster asks why an answer was given, the evidence and the date it was collected are already there.
Set a recurring schedule for each client’s renewal date, less 90 days. The checklist appears with the scoping phase assigned to the account manager and the evidence phases assigned to the engineers who can produce them, with no calendar reminder to miss.
When a control is marked missing or partial, conditional logic brings in the remediation phase, with owners and dates. The client sees the plan and approves the budget before signing, not after a claim.
Cyber insurance readiness is one of the most valuable recurring services an MSP can offer, because it connects your security stack to something the client’s finance director already cares about. See how MSPs run it alongside onboarding, monthly reviews and QBRs on the MSP process management software page.
Insurance applications are one of several attestations a client signs each year. CheckFlow’s compliance checklist software shows how to run recurring reviews, evidence and approvals across the whole compliance calendar, and the Client Cybersecurity Risk Assessment Checklist covers the wider annual posture review.
Client Cybersecurity Risk Assessment Checklist
EDR Rollout Checklist
Email Authentication (SPF, DKIM, DMARC) Setup Checklist
MSP Daily Backup Monitoring Checklist
Disaster Recovery Audit Checklist
Describe the process in a sentence and the AI checklist generator drafts the phases and tasks for you.
It is a structured check, done before a cyber insurance application or renewal, that confirms each security control the insurer asks about is really in place and collects the evidence that proves it. Gaps are either fixed before the application is signed or disclosed accurately. For MSP clients it is usually run by the MSP, with the client’s signatory reviewing the result.
It varies by carrier, industry, company size and the limit being bought, so always work from the actual application. The controls that come up most often are MFA on email, remote access and privileged accounts; endpoint detection and response; backups with an offline or immutable copy and tested restores; timely patching and control of end-of-life systems; no remote desktop exposed to the internet; email security and awareness training; and a written, tested incident response plan.
That depends on the policy wording and the law that governs it, and it is a question for the client’s broker or lawyer. The risk is real, though. In Travelers v. International Control Services (2022), the insurer sought to rescind a cyber policy after a ransomware attack, saying the application had overstated how MFA was used. The insured agreed and the policy was declared void. Accurate answers, with the evidence behind them, are the best protection.
Sixty to ninety days before the renewal date is a practical starting point. Collecting evidence takes a few days, but closing a gap such as rolling out MFA to every remote access route, or deploying EDR to servers, can take weeks. Starting early means the client can choose between fixing the gap and disclosing it, rather than facing that choice the week the form is due.
The MSP should supply the technical answers and the evidence behind them. The client’s authorised signatory should read and sign the application, because the representations are theirs. Keep a record of what you supplied and when. It is also worth checking your own MSP agreement and professional liability cover for how they treat this kind of advice.
No. The broker advises on cover, limits, carriers and policy wording, and the checklist doesn’t touch any of that. What it does is make sure the technical picture you give the broker is accurate and evidenced, which usually makes the broker’s job easier and the conversation with the underwriter shorter.
14-day free trial, no card required. The Business plan is $10 per user per month after the trial. Full details at checkflow.io/pricing.
14-day free trial, no credit cardFull refund in your first 30 daysUS hosting, EU on request
