- Insurers frequently assess MFA, EDR, backups, privileged access and patching, but requirements vary by insurer, organisation size, sector, geography and limit
- Answer proposal questions accurately, disclose material qualifications and keep the evidence behind each answer
- Under the Insurance Act 2015, the consequence of an unfair presentation depends on whether it was deliberate or reckless and on what the insurer would otherwise have done
- Lloyd's Market Bulletin Y5381 set minimum standards for state-backed cyber attack exclusions; it did not require every state-linked loss to be excluded
- Insurer notification periods come from your policy, not a universal 72-hour rule, and are separate from reporting to the ICO
Why cyber underwriting changed
Ransomware losses in 2020 and 2021 were higher than many insurers had priced for. Incidents such as Colonial Pipeline and JBS Foods showed how quickly a single attack could produce business interruption, recovery and liability costs. Insurers responded by raising rates, reducing capacity for some risks and asking far more detailed questions about security controls.
The rate increases were steep. In its Global Insurance Market Index for the fourth quarter of 2021, Marsh reported that cyber insurance pricing rose by 130% year on year in the US and by 92% in the UK. Those are averages for two markets, not a global figure, and individual renewals varied. Some insurers also introduced separate sublimits, coinsurance or higher deductibles for ransomware losses.
The ransom and recovery figures come from Sophos State of Ransomware 2026, a survey of 2,158 IT and security leaders in 17 countries whose organisations were hit by ransomware in the previous year. Pricing has moderated since the 2021 peak and conditions differ by market and quarter, so ask your broker for current figures. The underwriting discipline that emerged from that period has largely stayed: insurers still expect evidence that key controls are in place, and renewal questions remain detailed.
Five controls frequently assessed in underwriting
Proposal forms can run to dozens of questions. The five controls below are among those insurers most often ask about in detail, particularly in relation to ransomware. They are not universal prerequisites: what an insurer asks for, and how much weight it gives each answer, varies by insurer, organisation size, sector, geography and the limit requested. Depending on the insurer, a gap may lead to a declined quote, different terms, a higher premium or specific exclusions.
Beyond these five, insurers increasingly ask about email authentication (SPF, DKIM and DMARC), network segmentation, security awareness training, and whether you have an incident response plan that has been tested recently.
Answering the proposal form accurately
Accuracy matters as much as the controls themselves. If an incident later reveals a gap between what was in place and what the proposal stated, the insurer may raise it when assessing the claim. Whether that affects cover depends on what was represented, how material it was, the policy conditions and exclusions, what you knew, any connection between the gap and the loss, and the applicable law.
Typical application questions cover:
- Whether MFA is deployed on email, VPN, remote access, cloud services and privileged accounts, asked separately rather than as a single yes or no
- The percentage of endpoints covered by EDR
- Your patching timeframes for critical vulnerabilities
- Whether you have a documented incident response plan and when it was last tested
- How backups are protected, and whether and how often restores are tested
- Whether you have PAM controls, and whether privileged credentials are vaulted
- Annual revenue, number of employees, data types processed (personal data, payment card, health) and sector
Three habits reduce the risk of a dispute later:
- Answer accurately. Do not round up. If MFA covers most but not all remote access, say so and explain the exception.
- Disclose material qualifications. Exceptions, legacy systems, pending projects and compensating controls belong in the answer or in a covering note to the insurer.
- Ask about ambiguous questions. If a question could be read more than one way, ask your broker or the insurer how it should be interpreted and keep a record of the reply.
Do not complete the questionnaire from memory. Build an evidence register before you start: for each question, record the exact wording, your answer, its scope or qualifications, the supporting evidence, who reviewed it and the date it was approved.
Illustrative example. The register below shows the format only. The entries are fictional and do not reproduce any particular insurer's questions.
| Question | Answer | Scope or qualification | Evidence |
|---|---|---|---|
| Is MFA enforced for all remote access? | Yes, with one exception | Enforced on VPN and remote desktop gateway; one legacy supplier connection is restricted by IP allow-list until its planned migration | Conditional access policy export, VPN configuration, migration plan |
| Is EDR deployed on all endpoints? | 98% of in-scope devices | Laptops and servers covered; a small set of lab devices without EDR are on an isolated network | EDR console coverage report, asset inventory |
| Are backups protected against deletion or encryption? | Yes | Daily backups to immutable storage with fixed retention, plus a monthly offline copy | Storage configuration, latest restore test report |
| Within how many days are critical patches applied? | 14 days internet-facing, 30 days internal | Exceptions approved through change management | Patch compliance report, exception register |
Request a copy of last year's proposal from your broker. Comparing year-on-year answers against your current posture is one of the fastest ways to identify where your documentation does not match your controls.
The duty of fair presentation under the Insurance Act 2015
For business insurance in the UK, the main disclosure rules come from the Insurance Act 2015. The Consumer Insurance (Disclosure and Representations) Act 2012 applies to consumers, not to businesses buying cyber cover.
Before the contract is entered into, the insured must make a fair presentation of the risk (section 3). In broad terms, that means disclosing every material circumstance it knows or ought to know, or at least giving the insurer enough information to prompt further enquiries, in a reasonably clear and accessible way. Material representations of fact must be substantially correct, and representations of expectation or belief must be made in good faith.
A breach does not automatically cancel cover. Under Schedule 1, the insurer has a remedy only if it shows that, with a fair presentation, it would not have entered into the contract or would have done so on different terms. The remedy then depends on the type of breach:
- Deliberate or reckless. The insurer may avoid the contract, refuse all claims and keep the premium.
- Neither deliberate nor reckless. The remedy reflects what the insurer would have done: if it would not have written the policy, it may avoid it but must return the premium; if it would have imposed different terms, the contract is treated as including them; if it would have charged a higher premium, the claim may be reduced proportionately.
Section 11 also limits reliance on certain terms intended to reduce the risk of a particular kind of loss, where the insured shows that the non-compliance could not have increased the risk of the loss that actually occurred. Business policies can vary some of these default rules if the Act's transparency requirements are met, so read the wording and take legal advice on any specific dispute.
How insurers assess claims
When you notify a claim, the insurer needs to establish what happened and whether it is covered. That can involve document review, technical investigation, loss adjusting and checking the policy conditions. Many policies give access to a panel of approved incident response, forensic and legal specialists, and some require or encourage you to use them.
Forensic investigators establish the cause, scope and impact of the incident: how the attacker got in, which systems and data were affected, and what recovery will take. Their findings may also inform the coverage assessment, for example where the route in relates to a control described in the proposal. That is one reason accurate answers and good records matter.
Notification is the second issue. There is no universal deadline: each policy sets its own triggers and periods, such as notice as soon as practicable after you become aware of an incident or circumstance, sometimes with a stated number of days. Some notification clauses are conditions of cover. Record the insurer's contacts, triggers and periods in your incident response plan so the team can follow them under pressure.
Notifying your insurer is separate from regulatory reporting. Under UK GDPR, a personal data breach that is likely to pose a risk to individuals must be reported to the ICO without undue delay and, where feasible, within 72 hours of becoming aware of it. Sector regulators and contracts may impose their own deadlines. One notification does not cover the others.
Where feasible, check your policy and contact the insurer or its breach response line before appointing PR, legal or forensic providers, because some policies only reimburse approved providers or require prior consent for costs. Those requirements must not delay mandatory legal notifications, urgent steps to protect people and systems, or containment. Record what you did and why.
Exclusions and cover limits to understand
Read the full policy wording and schedule, not just the summary. The terms that matter most in a claim often sit in the definitions, exclusions and conditions.
Cyber insurance readiness checklist
Use this checklist to keep the evidence behind your proposal answers in one place, and update it whenever controls change rather than only at renewal.
| Area | What to document |
|---|---|
| Policy | Current wording and schedule, limits, sublimits, deductibles, exclusions, endorsements and panel providers |
| MFA | Systems and user groups covered, enforcement method, exceptions and compensating controls |
| Endpoint security | EDR deployment by device type, coverage percentage, excluded devices and why |
| Backups | Design (immutable, offline, isolated or a combination), retention, latest restore test, protection of backup admin credentials |
| Privileged access | Inventory of admin accounts, vaulting, time-limited access, review dates |
| Vulnerability management | Patching timeframes by severity, latest scan results, exception register |
| Incident response | Current plan, insurer contacts and notification triggers, regulatory deadlines, latest exercise and findings |
| Underwriting representations | Exact question, answer given, evidence, reviewer and approval date |
| Claims procedure | How to notify, information the insurer needs, approved providers, consent requirements for costs |
| Renewal | Planning timeline, broker contact, changes since the last proposal, open remediation items |
Preparing for renewal
Starting around six months before renewal is a sensible planning window, not a fixed rule; organisations with complex estates or open remediation work may need longer. Brokers often send pre-renewal questionnaires a few months out. The bigger point is to keep security evidence current all year, so renewal becomes a review rather than a scramble.
An organisation that arrives at renewal with a current evidence register, a tested backup report and a documented tabletop exercise is in a stronger position than one relying on memory. The same records provide consistent documentation that can be checked if questions arise after an incident.
ENISA's guidance on minimum security baseline measures is available at enisa.europa.eu. The NCSC publishes practical implementation guidance on the technical controls that underwriters and regulators most commonly ask about.
If you are building a controls inventory for the first time and need a programme structure to sequence the work, a cybersecurity roadmap maps each control to a business priority and assigns ownership before the insurer questionnaire arrives.