Cyber insurers now ask detailed questions about specific security controls before they quote or renew a policy. The controls they most commonly ask about include MFA for email, remote access and admin accounts, EDR, offline or immutable backups, patching, privileged access, training and an incident response plan. This guide explains each one and how to answer an application accurately, since a wrong answer can put coverage at risk.
Cyber insurance requirements used to be a short questionnaire. Now most applications read like a security audit: do you enforce MFA on email and remote access, do you run EDR, are your backups offline or immutable, how fast do you patch? The answers decide whether you get a quote, what it costs, and in some cases whether a claim gets paid.
There is no universal list. Each carrier writes its own application, and requirements shift with policy size, industry and the loss trends underwriters are seeing. What follows are the controls that come up most often, why insurers care about them, and how to answer the questions without creating a problem for yourself later.
Why insurers now ask about specific controls
Insurers have years of claims data showing which weaknesses lead to losses. Marsh, one of the largest insurance brokers, put it plainly in its twelve key controls report: insurers are tightening underwriting terms, scrutinizing applications, and asking more questions than ever, and "the adoption of certain controls has now become a minimum requirement of insurers."
For a 20-person firm, that changes the purchasing conversation. A few missing controls can mean a declined application or less favorable terms, and your broker can tell you how a specific carrier treats each gap. In our experience, fixing the gaps before renewal is a better use of money than arguing about them during it.
Common cyber insurance requirements: the controls applications ask about
Marsh's list of twelve controls is a useful map, because it lines up closely with what carriers ask. We have grouped them below with the questions you are likely to see. Treat this as "commonly asked," not as any single insurer's checklist.
| Control | What applications typically ask | Evidence to have ready |
|---|---|---|
| MFA | Is MFA enforced for email, remote access (VPN, RDP), cloud apps and all admin accounts? | Conditional access or MFA policy report, list of exclusions |
| Endpoint detection and response (EDR) | Do you run EDR on all servers and workstations? Is it monitored? | Console screenshot showing device coverage |
| Backups | Are backups encrypted, offline or immutable, and tested? How often? | Backup job reports, last restore test date |
| Patch and vulnerability management | How quickly do you apply critical patches? Do you scan for vulnerabilities? | Patch compliance report |
| Privileged access management | Are admin rights restricted? Do admins use separate accounts? | List of admin accounts and who holds them |
| Email filtering and web security | Do you filter inbound email for phishing and malware? | Email security policy settings |
| Security awareness training | Do staff get training and phishing simulations? | Training completion records |
| Incident response plan | Do you have a written plan? Has it been tested? | The plan and date of last tabletop exercise |
| Remote desktop hardening | Is RDP exposed to the internet? | External scan results |
| Logging and monitoring | Are security logs collected and reviewed? | SIEM or log retention settings |
| End-of-life systems | Do you run unsupported operating systems or software? | Asset inventory with OS versions |
| Vendor and supply chain risk | How do you assess vendors with access to your systems or data? | Vendor list and contract terms |
Some applications also ask about encryption of sensitive data, network segmentation, and whether you have a managed security provider watching alerts around the clock.
MFA questions deserve the most care
MFA is the control insurers ask about most, and it is the one where honest firms most often answer wrong. The usual problem is not lying. It is assuming MFA is "on" because people get prompted when they log into Outlook, while a service account, an old admin login, or the remote desktop gateway sits outside the policy.
Marsh says MFA should be enforced, at a minimum, on critical assets, privileged accounts and remote applications. Its implementation guidance goes further: MFA for all remote logins, all administrative account access regardless of location, and access to the most sensitive data and systems.
The case that made brokers nervous is Travelers v. International Control Services. According to Insurance Journal's coverage, the company's president signed an application and MFA attestation in March 2022. After a ransomware event that May, Travelers alleged the attestation misrepresented the company's MFA use. The parties then asked the court to declare the policy null and void from its inception. A Lockton analysis describes the issue as MFA covering fewer systems than the application claimed.
That case settled by agreement, so there is no court opinion on the merits. It still shows the risk clearly. If you answer "yes" to MFA on all remote access, it needs to be true for all remote access.
A note on MFA type: CISA calls phishing-resistant MFA the gold standard and warns that SMS codes and push notifications can be defeated by phishing, push bombing and SIM swaps. An application may ask which MFA methods you use as well as whether you use MFA at all. Passkeys and hardware security keys are worth considering for admins first.
Backups: what "offline" and "immutable" mean to an underwriter
Ransomware groups go after backups on purpose. CISA's #StopRansomware Guide says many ransomware variants try to find and delete or encrypt accessible backups, and it recommends maintaining offline, encrypted backups of critical data and regularly testing their availability and integrity.
Insurers ask about this because a clean, restorable backup is the difference between a bad week and paying a ransom. Expect questions like these:
- Is at least one copy offline, air-gapped or immutable?
- Are backups encrypted?
- Are backup systems protected with separate credentials and MFA?
- When did you last test a full restore, and how long did it take?
- Do you back up cloud data such as Microsoft 365 mailboxes and SharePoint?
The last question catches a lot of firms. Microsoft runs the platform, but Microsoft's shared responsibility model leaves customer data, accounts and configuration with you. Our guide to backup vs disaster recovery explains RTO and RPO targets and the 3-2-1-1-0 approach, and our data backup and disaster recovery service covers how we set this up.
EDR is not the same as antivirus
Many applications ask specifically about endpoint detection and response (EDR), not antivirus. Traditional antivirus matches files against known malware. EDR records process, file and network activity on each device, flags suspicious behavior, and lets a responder isolate a machine remotely.
The follow-up question matters as much as the first: who watches the alerts? An EDR tool that sends warnings to an unread mailbox does little. If you rely on a managed provider, be ready to say so and to describe their hours.
Privileged access, patching and the boring stuff
Underwriters also ask about controls that are less exciting but cause plenty of claims:
- Admin rights. Staff should not use accounts with local or global admin rights for daily work. Admins should have separate, MFA-protected admin accounts.
- Patching. Expect a question about how many days it takes to apply critical patches. Have a real number, not an aspiration.
- End-of-life systems. An old Windows 10 PC running the scanner software, or a server past support, is often flagged. See our notes on Windows 10 end of support if that applies to you.
- Remote desktop. RDP open to the internet is one of the fastest ways to get declined.
Many of these live in Microsoft 365 settings. Our Microsoft 365 security checklist walks through the tenant side.
Cyber insurance requirements can change at every renewal
Do not assume this year's form matches last year's. Carriers revise their applications as claims trends shift, and a question that used to be a simple yes or no can come back split into five parts, asking separately about MFA on email, on remote access, on backups and on each kind of admin account. If you switch carriers, expect a different form entirely.
The easiest way to handle this is to keep a standing "controls file" that your IT provider updates a few times a year: current MFA coverage and exceptions, EDR device counts, backup reports and the last restore test, patch compliance, the admin account list, training records and the incident response plan. When the renewal arrives, you are answering from current evidence instead of starting from scratch. The same file is useful for client security questionnaires and for regulatory reviews, so the effort pays off more than once.
How to answer the application truthfully
The application is part of your insurance contract. Lockton's advice after the ICS case boils down to this: read each question carefully, describe your controls as they actually are, and verify the extent of a control, not just its existence. Here is the process we recommend.
- Get the actual application early. Ask your broker for the carrier's form 60 to 90 days before renewal, not the week it is due.
- Read the question literally. "MFA for all remote access" includes the VPN, remote desktop gateway, remote management tools and cloud admin portals.
- Check, do not recall. Have your IT provider pull current reports for each control instead of answering from memory.
- Write down exceptions. If a scanner, legacy app or service account cannot use MFA, document it and the compensating control. Then disclose it.
- Use the comment box. If a control is partly in place, say so, describe what remains, and give a completion date.
- Keep copies. Save the application, your supporting screenshots and the date. If you ever file a claim, you will want to show what was true when you signed.
- Tell your broker about changes. If something changes mid-term (an acquisition, a new remote access tool, a control that lapses), ask whether you need to update the insurer.
One more thing: do not let a vendor or salesperson fill out the security section for you. The person signing should understand what each answer commits the firm to.
What to do if you cannot answer yes yet
Most gaps are fixable in weeks, not months. MFA on remaining accounts, EDR deployment and an immutable backup copy can usually be done before a renewal date if you start early. A written incident response plan can be drafted in a few working sessions. Training can start this month.
If you need help getting ready, our cybersecurity services team can review the application with you, check each control against your environment, close the gaps that matter most, and give you documentation you can stand behind. For firms that want ongoing coverage, these controls are part of how we run managed IT services day to day.
Frequently asked questions
What security controls do cyber insurers require?
Requirements vary by insurer, policy size and industry, so there is no single list. The controls applications most commonly ask about are MFA for email, remote access and administrator accounts, endpoint detection and response, secured and tested backups kept offline or immutable, timely patching, restricted admin privileges, security awareness training, email filtering, and a written incident response plan. Your broker can tell you which ones a specific carrier treats as mandatory.
Can an insurer deny a claim if my application answers were wrong?
Inaccurate answers can give an insurer grounds to deny a claim or rescind a policy. In Travelers v. International Control Services (2022), the insurer alleged the company misrepresented its MFA use on the application, and the parties jointly asked the court to declare the policy void from its inception. That case settled by agreement, but it shows why you should treat the application like a legal document.
Does cyber insurance require MFA?
Most applications ask about MFA in detail, and many insurers treat it as a minimum condition. Broker Marsh lists MFA for remote access and privileged or administrator access as the first of its twelve key controls and says certain controls have become a minimum requirement of insurers. Expect questions about MFA on email, VPN and remote desktop access, cloud apps, and every administrative account.
What counts as an offline or immutable backup for insurance purposes?
An offline backup is disconnected from your network, so ransomware cannot reach it. An immutable backup cannot be changed or deleted for a set retention period, even by an administrator account. Insurers generally want at least one copy that meets one of those descriptions, plus evidence that you test restores. Ask your broker how the specific carrier defines the terms before you check the box.
How can a small business prepare for a cyber insurance renewal?
Start 60 to 90 days before renewal. Get the carrier's application early, have your IT provider document the current state of each control with screenshots or reports, and close gaps you can fix quickly, such as MFA on a forgotten admin account. Where something is not in place, say so and describe your plan and timeline rather than answering yes and hoping.
Sources and references
- Marsh: Cyber resilience, twelve key controls to strengthen your security (April 2022)
- Marsh: Cyber resilience, twelve key controls (overview page)
- CISA: #StopRansomware Guide
- CISA: Implementing Phishing-Resistant MFA (fact sheet, October 2022)
- Lockton: Travelers v. ICS and the need to respond carefully to cyber insurance application questions
- Insurance Journal: Travelers, insured agree to rescind cyber policy over MFA misrepresentation (August 30, 2022)
- Microsoft Learn: Shared responsibility in the cloud