Compliance Guide

Cyber insurance: what applications ask for now

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 checklist

Last reviewed · For owners and office managers of small and midsize businesses applying for or renewing cyber coverage.

Not legal advice. This guide is general educational information from an IT provider, current to the best of our knowledge as of September 24, 2026. Regulations, standards, and official guidance change, and how they apply depends on your specific facts. Confirm your obligations with a qualified attorney, compliance professional, or the relevant regulator or standards body before relying on it. PinellasIT does not certify compliance.

A 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.

Why the questions got harder

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.

The controls insurers ask about

MFA everywhere

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.

Endpoint detection and response (EDR)

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.

Offline or immutable backups

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.

Patching and vulnerability management

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?

Email filtering and security

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?

Security-awareness training

Is training done at least annually? Do you run phishing simulations? Some forms ask what percentage of staff completed it.

Privileged access

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.

Incident response plan

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.

How questions map to controls

Here’s how common questionnaire items translate into things you can actually implement and prove:

If the application asks…What you need in placeEvidence 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 blockedScreenshot 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 promptlyConsole 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 MFABackup 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 OSesPatch compliance report
“Do you filter email and verify payment changes?”Advanced email filtering, DMARC, and a call-back procedure for bank or wire changesFiltering configuration and a written payment-verification policy
“Do users have local admin rights?”Standard user accounts, with separate MFA-protected admin accountsAdmin group membership list
“Do you have an incident response plan?”A written plan with contacts, roles, and your insurer’s claim lineThe plan document and a record of an annual review or tabletop exercise

Answering honestly (and why it matters)

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:

  • Answer for the whole business, not the best-case part. “MFA on all remote access” means every account and every method, including the old VPN account nobody uses.
  • Have IT verify technical answers rather than filling them in from memory. If the honest answer is “partially,” say so and describe your remediation plan and timeline. Brokers can often work with that.
  • Keep a copy of the submitted application and the evidence behind each answer.
  • Tell your broker if something changes mid-term, such as dropping a control or adding a new office, and check whether your policy requires you to disclose it.
  • Read the conditions: notice deadlines, required vendors, and exclusions (for example, for unpatched known vulnerabilities or war and state-sponsored attacks) vary by carrier.

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.

Preparing for renewal

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.

Pre-application checklist

  • MFA is enforced on email, every remote-access method, cloud apps, admin accounts, and the backup console.
  • Legacy authentication protocols that bypass MFA are disabled in Microsoft 365 or Google Workspace.
  • EDR is installed on every workstation and server, and the device count matches your inventory.
  • At least one backup copy is offline or immutable and uses credentials separate from your domain.
  • A restore test was completed recently, with the date and result documented.
  • Critical patches are applied within a defined window, and no end-of-life systems remain (or they’re isolated and documented).
  • No remote desktop or admin interfaces are exposed directly to the internet.
  • Email filtering is in place, plus SPF, DKIM, and DMARC on your domain.
  • A written call-back procedure exists for any change to payment or banking details.
  • Staff complete security-awareness training at least annually, with phishing simulations.
  • Everyday accounts have no admin rights, and privileged accounts are separate and MFA-protected.
  • A written incident response plan includes your insurer’s claim contact and notice requirements.
  • Last year’s application has been reviewed, and every answer is re-verified before signing.
  • Evidence (screenshots, reports, policies) is saved alongside the submitted application.

How PinellasIT helps

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.

  • Free security assessment — see how your current setup lines up with typical questionnaire items before your renewal.
  • Cybersecurity — MFA and conditional access, EDR, email filtering, DMARC, and security-awareness training.
  • Backup & disaster recovery — immutable and offline backup copies, separate credentials, and documented restore tests.
  • Managed IT services — patching, admin-rights cleanup, and asset inventory with reports you can hand an underwriter.
  • Free incident response plan template — a starting point for the written plan most applications ask about, to adapt for your business.

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.

Frequently asked questions

Do we need MFA to get cyber insurance?

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.

Is regular antivirus enough, or do insurers want EDR?

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.

What counts as an immutable or offline backup?

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.

What happens if we answer an application question incorrectly?

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.

Can PinellasIT fill out our cyber insurance application?

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.

Will better security lower our premium?

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.

Want a second set of eyes on your safeguards?

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.