Commercial Insurance & Risk ManagementChecklist3 min readUpdated September 2026

Cyber Insurance Applications: The Questions Underwriters Ask

A cyber insurance application asks whether you have specific security controls in place: multi-factor authentication, tested backups, endpoint protection, patching, payment verification and an incident response plan. Underwriters use your answers to decide whether to offer coverage and at what price.

Answer every question accurately and get evidence for each one. A confident "yes" that turns out to be untrue can create a serious problem when you file a claim. Here are the questions in plain English and how to prepare.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

What will the application ask about identity and access?

Expect the sharpest questions here, because stolen credentials are behind many incidents. Typical questions:

  • Is multi-factor authentication required for email, remote access and administrator accounts?
  • Is it required for cloud consoles and for anyone with privileged access to production systems?
  • Do you use single sign-on, and how do you remove access when someone leaves?
  • Who has administrator rights, and are those accounts separate from daily-use accounts?

Before you answer "yes" to anything, check the actual settings. "MFA is enabled" and "MFA is enforced for everyone with no exceptions" are different statements. Export a report from your identity provider that shows enforcement, and note any service accounts or legacy protocols that bypass it. If there's an exception, fix it or state it honestly.

What do underwriters ask about backups and recovery?

Ransomware is the loss scenario insurers worry about, so backups get detailed attention. You may be asked:

  • How often are backups taken, and what data do they cover?
  • Are backups stored separately from your production environment, and can an attacker with your admin credentials delete them?
  • Are backups encrypted, and do they have a retention lock that prevents changes?
  • When did you last test a restore, and how long did it take?

The word to focus on is tested. An untested backup is a hope, not a control. Run a restore of a real system, time it, write down the result and keep the record. A documented recovery time gives you a factual answer when the form asks how long restoration takes.

What about endpoints, patching and monitoring?

Insurers want to know how quickly you notice and fix problems:

  • Is endpoint detection and response software installed on all laptops and servers, and who watches its alerts?
  • How do you track software and operating system updates, and what's your target time for critical fixes?
  • Do you log security events centrally, and for how long do you keep logs?
  • Do you scan for vulnerabilities, and how do you prioritize what you find?

Answer with the process you follow, and be careful with words like "all" and "always." If your target is to patch critical issues within a set number of days but you sometimes miss it, describe the target and how you handle exceptions. Coverage gaps such as unmanaged personal devices should be listed and closed.

Which payment fraud and governance questions matter?

Business email compromise and wire fraud are common claims, and many applications include specific questions:

  • Do you verify payment instruction changes by a second channel, such as a call to a known number?
  • Is there dual approval for wire transfers and changes to vendor bank details?
  • Do employees receive security awareness training, and do you run phishing simulations?
  • Do you have a written incident response plan, and when did you last rehearse it?
  • Do you vet vendors that hold your data, and require them to carry security controls?

These are process controls that cost little. Write them down, train the finance team and put the incident response plan somewhere you can reach it when systems are down.

How do you complete the application without risking your coverage?

Treat the application as a formal representation, because insurers can rely on it. A repeatable process helps:

  1. Have the person who actually runs IT or security answer the technical questions, not the person who signs the form.
  2. Attach or keep evidence for each answer: screenshots, policy documents and the restore test record.
  3. Where a control is partial, describe it accurately. Ask the broker how to present it, and whether a future date for a fix can be noted.
  4. Have an officer review and sign, and keep a copy of what you submitted.
  5. Re-check at renewal, since your environment changes and last year's answers may no longer be true.

Compare quotes from more than one source, and read exclusions and sublimits with your broker. The comparison of Embroker, Vouch and Hiscox shows how providers differ, and the guide on tech E&O versus cyber insurance explains which policy covers what. If a customer asks for proof, see the certificate of insurance guide.

Executive Capability Standard

What Good Looks Like

Every answer on a cyber insurance application is true, current and backed by evidence, with the key controls in place before you apply.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Read a sample application and learn what each question about MFA, backups, endpoint protection and payment verification is testing.
2. Do Manually:Run a restore test, export your MFA enforcement report and list every exception before you answer a single question.
3. Delegate:Have your IT lead or security provider answer the technical questions, and an officer review and sign the final form.
4. Automate:Automate MFA enforcement, patching reports and endpoint alerts so your answers stay true year-round.
5. Buy:Work with a specialist insurance broker or provider to place cover and compare terms, and keep your evidence file ready.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Embroker

Fits a tech company that wants a digital process for comparing and buying cyber and related business insurance.

Visit Embroker→
Vouch

Fits a venture-backed startup that wants cyber cover placed together with other startup policies.

Visit Vouch→

Frequently Asked Questions

What is the most common reason for a cyber insurance application to be declined?

Missing or unenforced multi-factor authentication is a frequent cause of declined applications or restrictive terms, especially for email and remote access. Fixing that gap first usually improves your options more than any other single change.

What does cyber insurance typically cover?

Policies commonly include first-party costs such as incident response, forensics, business interruption and notification, plus third-party liability for claims arising from a breach. Coverage, limits and exclusions vary by policy, so read the terms with your broker.

What happens if I answer an application question incorrectly?

An inaccurate answer can give the insurer grounds to dispute or deny a claim, depending on the policy and the facts. Answer accurately, keep evidence, and ask your broker how to disclose partial controls.

How much does cyber insurance cost for a startup?

Price depends on your industry, revenue, data, controls and the limits you choose, so quotes vary. Get several, compare limits and retentions along with the premium, and ask how improving specific controls would change the price.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides