How to Answer a Cyber Insurance Questionnaire Without Weakening Your Quote
Every answer on your cyber application can be checked against your logs after a claim. Here's how to split the form among the people who run each control, keep proof for every answer and disclose half-finished controls without losing the quote.
Signed Answers Become Part of the Policy Contract
Most people filling in a cyber insurance questionnaire treat it as paperwork that stands between the company and a quote. That's a mistake. Under most cyber policies, the signed application is incorporated into the contract. Each answer is a representation the insurer relies on when it prices and accepts the risk. After a ransomware claim, the insurer's forensic firm will open your EDR console, pull your identity provider's sign-in logs and inspect your backup configuration. If what they find doesn't match what you signed, the insurer may reduce the payout, deny the claim or try to rescind the policy.
This has already happened in public. In a widely reported 2022 US case, Travelers asked a court to rescind a policy after a ransomware incident. The applicant had attested to multi-factor authentication, but MFA turned out to protect the firewall and not other access paths. The policy was rescinded by agreement.
Overstating your controls also doesn't reliably get you a better quote. Underwriters price uncertainty. A qualified answer such as "yes, on 94% of endpoints, with the rest scheduled by a named date" often prices close to a clean yes. It's also far safer than a yes that won't survive a forensic review. The sections below work through the form in order.
Assign an Owner and an Evidence File to Every Section
Before anyone types an answer, name one coordinator (usually the risk manager or whoever works with the broker) and one signer (normally the CFO, CEO or CISO, depending on what the form requires). Then give each section to the person who actually runs that control, not the person who wrote the policy document about it.
| Application section | Answer owner | Evidence to keep or attach |
|---|---|---|
| Company profile, revenue, record counts | Finance and legal/privacy | Revenue by region, data inventory with record estimates by type |
| Identity and MFA | Identity/IAM administrator | Conditional access policy export, MFA enrollment report, legacy-auth block evidence |
| Endpoint protection / EDR | Security operations lead | Console deployment report reconciled to asset inventory |
| Backups and recovery | Infrastructure/backup administrator | Immutability settings, retention, last restore test record |
| Patching and vulnerability management | IT operations | Scanner summary, patch-time metrics, end-of-life system list |
| Email security | Messaging administrator | SPF/DKIM/DMARC records, filtering configuration |
| Privileged access | IAM or security engineering | Admin account list, PAM report |
| Incident response and continuity | CISO or risk manager | IR plan version, last tabletop date, retainer details |
| Prior incidents, claims, circumstances | Risk manager with legal | Incident log for the look-back period the form specifies |
Store the evidence for each answer in a dated folder. You won't attach all of it, but you should be able to produce any piece within a day if the underwriter asks. A forensic firm certainly will.
Identity and MFA: Answer for Each Access Path Separately
Forms ask about MFA in several places: remote access, email, cloud consoles, privileged accounts, backup consoles and sometimes third-party access. The identity owner should answer each one on its own, after checking what's actually enforced rather than what the policy says.
Look for these gaps before you tick yes:
- Legacy authentication. Protocols such as IMAP, POP or basic-auth SMTP can bypass MFA on email entirely.
- Exempt accounts. Service accounts, break-glass accounts and executive exceptions are common. Disclose them and explain how they're restricted.
- Side doors. Exposed RDP, a vendor's remote-support tool or an old VPN appliance may not sit behind the identity provider at all.
- Contractors and offshore teams. They often authenticate through separate tenants or partner portals.
At many mid-size companies, the honest answer to "Is MFA enforced for all remote access?" turns out to be "yes, with two exceptions." Write exactly that. Name the exceptions and the compensating controls, such as IP restrictions or credential vaulting.
EDR Requirements: Report Coverage as a Number
EDR requirements for cyber insurance are now standard with most carriers in North America, the UK, Europe and Australia, and increasingly common in Asia and the Middle East. The questions usually ask whether EDR runs on all endpoints and servers, which product it is, and whether alerts are monitored around the clock by an internal team or a managed detection and response (MDR) provider.
The trap is the word "all." Linux servers, OT workstations, kiosks, lab machines and contractor laptops routinely go without agents. The security operations lead should compare healthy, reporting agents against the asset inventory and explain the difference. Name the product and tier precisely, for example Microsoft Defender for Endpoint Plan 2, CrowdStrike Falcon, SentinelOne or Sophos Intercept X, because some insurers treat entry-level antivirus tiers differently from full EDR. State whether agents run in prevention (block) mode or detect-only.
If closing the gap means buying licenses, typical 2026 market ranges run roughly $30 to $90 per endpoint per year for EDR alone and roughly $80 to $250 or more for MDR. Pricing varies widely by contract size and region, so confirm current quotes with vendors or local resellers.
Immutable Backup Requirements: Prove You Can Restore
Insurers care about backups because recovery capability decides whether a ransomware event costs days or months of business interruption. Immutable backup requirements typically cover four points: at least one immutable or offline copy, backup credentials separate from the main domain, MFA on the backup console, and tested restores.
The backup administrator should answer with specifics:
- Which systems are covered, including SaaS data such as Microsoft 365 or Google Workspace and cloud workloads.
- How immutability is enforced (object lock on cloud storage, a hardened repository or a vendor-managed vault) and the retention period.
- Whether a domain admin could delete or encrypt the backups. If so, the credentials aren't truly separate.
- The date of the last full restore test, what was restored and how long it took against your stated recovery time objective.
A "yes" backed by a restore test record is one of the strongest answers on the form. A "yes" based on a vendor brochure is one of the most dangerous.
Patching, Email Security and Privileged Access: Report Practice, Not Policy
These sections attract answers copied from the policy manual rather than measured from the environment.
Patching. When asked how quickly critical patches are applied, give your measured median from scanner or patch-management data, not the target in your policy. List end-of-life operating systems and applications, why they remain and how they're segmented. Underwriters can usually work with an isolated legacy system you've disclosed. An undisclosed one is a misrepresentation problem.
Email security. Report your actual DMARC policy. A record set to p=none means monitoring only, not enforcement. Name your filtering layer and say whether attachments and links are sandboxed.
Privileged access. Count your domain and global admins, confirm whether admins use separate accounts for privileged work, and say whether a PAM tool vaults credentials. Hypothetically, if a 300-person firm finds 38 domain admins, it should state the number and attach a reduction plan. That count will surface in any forensic review regardless.
How to Disclose Partly Deployed Controls
Most weak answers start here. Binary yes/no fields push people to round up. Don't. Use the same four-part disclosure wherever a control is incomplete:
- Scope: what is covered, as a number or percentage.
- Gap: what isn't covered and why.
- Compensating control: what reduces risk in the gap today.
- Dated plan: when the gap closes and who owns it.
A hypothetical example: say a 450-person manufacturer has EDR reporting on 412 of 450 endpoints. The other 38 are plant-floor workstations whose vendor won't certify the agent. A strong disclosure reads: "EDR (named product, prevention mode) deployed on 412 of 450 endpoints, including all servers and corporate laptops. 38 OT workstations excluded pending vendor certification; these sit on an isolated VLAN with no internet access and application allow-listing. Certification and rollout targeted for Q2 2027, owned by the OT engineering manager."
If the form has no comment field, put disclosures in a signed addendum or a broker cover letter, and get the broker to confirm in writing that the underwriter received it as part of the submission. Set remediation dates you can actually hit. Insurers sometimes turn your plan into a subjectivity or policy condition, and missing that date can affect cover.
Prior Incidents and Material Misrepresentation Across Jurisdictions
The incident and claims questions carry the most legal weight. They usually ask about past breaches, ransom demands, regulatory inquiries and any "facts or circumstances" that could give rise to a claim. The risk manager and legal counsel should answer them together, working from an incident log that covers the exact look-back period the form specifies. Under prior-knowledge exclusions, a known incident you didn't disclose may be excluded even if the rest of the policy stands.
What counts as a material misrepresentation, and the consequence, depends on the country. In broad terms:
- United Kingdom: The Insurance Act 2015 puts a duty of fair presentation on business insureds, with proportionate remedies. Deliberate or reckless breaches can let the insurer avoid the policy; other breaches may lead to a reduced payment or amended terms.
- Continental Europe: In Germany and several other civil-law systems, the pre-contract disclosure duty focuses mainly on what the insurer asks in writing, which makes precise answers to each question decisive.
- United States: Rules vary by state. Some require intent to deceive; others allow rescission for a material misstatement regardless of intent.
- Australia, India and many other markets apply statutory disclosure duties or the principle of utmost good faith, with differing remedies.
Forms often ask about the knowledge of senior management or named officers, so poll those people in writing before signing. Given how much the outcomes vary, have your broker and a qualified insurance lawyer in your jurisdiction review the incident answers.
Sign-Off, Evidence Retention and Mid-Term Changes
Before signing, the coordinator runs one final check. Every yes has a named owner and dated evidence. Every qualified answer has a scope, gap, compensating control and date. Every incident answer has been through legal review. The signer reads the qualified answers themselves, not a summary.
Archive the submitted application, any addendum and the evidence folder for the policy period plus your claims-reporting window. Renewal then means updating a file rather than starting over. Check the policy's change-notification duties as well: removing a control, making a major acquisition or taking on a significant new data set mid-term may need to be reported.
Apply one rule to every answer: if the owner can't produce evidence for a "yes" within 48 hours, it isn't a yes yet. Write it as a qualified answer, attach the plan and let the underwriter price it.
Quick answers
Will disclosing a gap in our controls automatically raise our premium?
Not necessarily. Underwriters price uncertainty, and a clearly scoped gap with compensating controls and a dated fix often prices close to full compliance. An unexplained "no" or a vague answer is more likely to bring a higher rate, a sublimit or a decline.
Who should sign the cyber insurance application?
Usually a senior officer such as the CFO, CEO or CISO, depending on what the form requires. The signer should get written confirmation from each section owner and read every qualified answer first. In many jurisdictions, the knowledge of the signer and senior management is attributed to the company.
What if a control was in place when we applied but lapsed during the policy term?
Check the policy for change-notification or condition-of-cover clauses, since some policies require you to report material changes. Tell your broker promptly. Fixing and documenting the lapse quickly is far better than letting a claim investigation find it.
Does basic antivirus satisfy EDR requirements for cyber insurance?
Generally no. Most carriers distinguish signature-based antivirus from EDR, which records endpoint behavior and supports investigation and response. Name the exact product and license tier on the form, and ask your broker how a specific tier is treated if you're unsure.
Can our broker answer the form for us?
A broker can structure the submission, write a cover letter and push back on unclear questions. But the answers remain your company's representations. The facts must come from the people who run each control, and the evidence stays with you.
How far back do we need to report prior incidents?
As far as the form's look-back period specifies, which is often three to five years, though forms vary. Read the definitions closely, since some count unsuccessful attacks, ransom demands or regulatory inquiries as incidents. Have legal counsel review these answers, because undisclosed known circumstances are a frequent reason claims are excluded.
Written by the Auditinsure Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.