Cyber insurance applications have turned into security audits. Here’s what underwriters typically ask, what each question really means, and how to answer honestly so your coverage holds up when you need it.
Jump to the checklistA few years ago, a cyber policy application was a page or two of general questions. After a wave of ransomware claims, carriers tightened underwriting considerably. Today’s applications, and the supplemental ransomware questionnaires that often come with them, ask specific technical questions. Weak answers can mean higher premiums, lower limits, exclusions, or a declined application. Every carrier’s form is different and requirements change from year to year, so treat this as a general map, not a guarantee of what any particular insurer will require.
Insurers learned from claims data which weaknesses tend to lead to expensive incidents: stolen passwords without MFA, exposed remote desktop, unpatched systems, and backups that ransomware could reach and destroy. The questionnaire is essentially a list of those lessons. That’s useful for you too, because the controls insurers care about are the same ones that most reduce the odds of a business-ending incident. We covered the background in why cyber insurance got harder.
Expect questions about MFA on email, on all remote access (VPN, remote desktop, remote-support tools), on cloud applications, and on administrator or privileged accounts. Also expect questions about backups: can someone reach the backup console with just a password? “MFA on email only” is usually not enough anymore.
Many carriers now ask whether you run EDR (behavior-based detection and response, not just traditional antivirus) on every workstation and server, and sometimes whether it’s monitored around the clock. See EDR vs. antivirus for the difference.
Questions typically ask how often you back up, whether at least one copy is offline, air-gapped, or immutable (unchangeable for a set period), whether backups are encrypted, whether backup credentials are separate from your normal network login, and when you last tested a restore.
How quickly are critical patches applied? Do you run any end-of-life software or operating systems? Is anything like remote desktop exposed directly to the internet?
Do you filter inbound email for malicious links and attachments, tag external senders, and use SPF, DKIM, and DMARC? Do you have a verification procedure for payment and banking changes to stop funds-transfer fraud?
Is training done at least annually? Do you run phishing simulations? Some forms ask what percentage of staff completed it.
Do users work day-to-day without local admin rights? Are admin accounts separate from everyday accounts, protected with MFA, and limited to the people who need them? Some carriers ask about privileged access management tools or how service accounts are handled.
Do you have a written incident response plan, and has anyone walked through it? Does it name who calls the insurer, the breach coach, and your IT provider? Most policies require prompt notice, and many require you to use the carrier’s approved vendors.
Here’s how common questionnaire items translate into things you can actually implement and prove:
| If the application asks… | What you need in place | Evidence to keep |
|---|---|---|
| “Is MFA required for all remote access and email?” | Conditional access or MFA enforced for every user in Microsoft 365 or Google Workspace, VPN, and remote tools, with legacy authentication blocked | Screenshot or export of MFA policy and user enrollment status |
| “Do you use EDR on all endpoints?” | An EDR agent on every PC and server, with alerts reviewed promptly | Console device count matched against your asset inventory |
| “Are backups offline, immutable, or segregated?” | An immutable cloud copy or offline copy, with separate backup credentials protected by MFA | Backup job reports and a dated restore-test record |
| “How quickly are critical patches applied?” | Managed patching with a defined window (for example, critical within days) and no unsupported OSes | Patch compliance report |
| “Do you filter email and verify payment changes?” | Advanced email filtering, DMARC, and a call-back procedure for bank or wire changes | Filtering configuration and a written payment-verification policy |
| “Do users have local admin rights?” | Standard user accounts, with separate MFA-protected admin accounts | Admin group membership list |
| “Do you have an incident response plan?” | A written plan with contacts, roles, and your insurer’s claim line | The plan document and a record of an annual review or tabletop exercise |
The application is typically part of the policy. If answers turn out to be materially inaccurate, the carrier may dispute or deny a claim, or even seek to rescind the policy. There has been at least one widely reported case in which an insurer sought to rescind a policy after a claim, arguing that the applicant’s MFA answers were inaccurate. A few practical rules:
We’re not insurance brokers and can’t advise on coverage terms. Work with a licensed broker who specializes in cyber, and have counsel review policy language if you have questions.
Start 60 to 90 days before renewal. Pull last year’s application, confirm every “yes” is still true, and look at what this year’s form adds. Closing a gap before you apply almost always goes better than explaining it afterward. Our cyber insurance requirements post walks through a renewal-prep conversation, and the checklist below doubles as a pre-application review.
We help businesses close the gaps a questionnaire exposes and pull together the evidence behind each answer. We can walk through the technical questions with you and your broker, but the application and its answers remain yours, and coverage decisions are the carrier’s.
We're a locally owned managed IT provider serving Pinellas and Pasco County businesses since 2010. We handle the technical safeguards and the documentation that shows they're in place; your attorney, auditor, or compliance advisor handles the legal judgment calls. See all of our compliance guides.
For most carriers today, MFA on email, remote access, and privileged accounts is a baseline expectation, and without it you may be declined or offered reduced terms. Requirements vary by carrier and change over time, so check your specific application.
Many applications now ask specifically about endpoint detection and response (EDR), and some ask whether it’s monitored 24/7. Traditional signature-based antivirus alone may not satisfy those questions.
An immutable backup can’t be changed or deleted for a set retention period, even by an administrator account. An offline or air-gapped backup isn’t reachable from your network. Either way, the goal is a copy that ransomware and stolen admin credentials can’t destroy.
Material misstatements can give an insurer grounds to dispute a claim or seek to rescind the policy. Have IT verify technical answers, disclose partial implementations honestly, and keep evidence. For questions about your policy terms, talk to your broker or an attorney.
We can review the technical questions with you, verify what’s actually in place, and provide supporting evidence. The application must be completed and signed by your business, and we don’t provide insurance or legal advice.
It can improve your insurability and terms, but pricing depends on the carrier, your industry, revenue, claims history, and market conditions. Strong controls mainly make you eligible for better options and reduce the chance you’ll ever need to file a claim.
Our free security assessment reviews the technical controls this guide covers and gives you a plain-English list of gaps, in priority order. No obligation and no sales pressure.
Prefer email? Reach us at info@pinellasit.com.