Yes, nearly every application now carries a cyber insurance MFA requirement. Carriers expect multi-factor authentication on email, on all remote access into your network, on administrator accounts, and increasingly on backups and cloud consoles, and many will decline to quote or will exclude ransomware coverage without it. Answering yes when MFA is only partly deployed is the single most common way we see Treasure Coast businesses put a future claim at risk.

Why did cyber insurance start requiring MFA?

Insurers pay claims, and they learned the hard way that most of the ransomware and email-fraud losses they paid between 2019 and 2022 started with a stolen password and no second factor. Once carriers priced that in, the application changed from a two-page questionnaire to a detailed security attestation. MFA moved from a nice-to-have to a condition of coverage because it is inexpensive and it stops the majority of credential-based attacks.

The questions are also getting more specific each renewal cycle. A form that asked whether you use MFA three years ago now asks where, for whom, and with what method.

Where does a cyber insurance application require MFA?

Wording differs by carrier, but the same five areas appear on almost every form.

1. Email

MFA for all users on Microsoft 365, Google Workspace, or any hosted email. Not just the owner, not just the office manager: every mailbox, including shared and service accounts. Carriers ask this first because business email compromise is their most frequent claim.

2. Remote network access

Any way into your network from outside must require a second factor: VPN, remote desktop gateways, remote-control tools used by staff or vendors, and cloud-hosted desktops. This is the question that catches construction, marine, and property-management firms whose field staff or bookkeeper connect remotely through a tool set up years ago.

3. Privileged and administrative accounts

Domain administrators, Microsoft 365 global admins, firewall and switch logins, and any account your IT provider uses. Some forms ask specifically whether admins use separate accounts for daily work and administration.

4. Backups and cloud consoles

Newer applications ask whether backup consoles and cloud management portals (Azure, AWS, your backup vendor) are protected by MFA, and whether backups are immutable or offline. Attackers delete backups before deploying ransomware, and carriers know it.

5. Critical business applications

Accounting, banking portals, payroll, practice-management, and CRM systems. Not every carrier asks, but the ones that do also want to know about payment-verification procedures for wire and ACH changes.

Can a wrong MFA answer void a cyber insurance claim?

It can, and it has. When a claim is filed, the carrier investigates how the incident happened. If the attacker walked in through an account without MFA and the application said MFA was in place everywhere, the insurer may argue the policy was issued based on a misrepresentation and deny the claim or rescind coverage. Widely reported litigation has involved exactly this pattern, and the details of whether the attestation was knowingly false or simply mistaken matter far less to a business that suddenly has no coverage after a six-figure loss.

We are not attorneys and cannot tell you how a specific policy would be interpreted. What we can say from experience is that the person filling out the form is usually an owner or office manager answering in good faith, based on what they believe IT set up, and the gap between belief and reality is where claims go wrong. Never sign an attestation without someone verifying each item technically.

What counts as MFA to an insurer?

  • Accepted: authenticator apps (Microsoft Authenticator, Google Authenticator, Duo), hardware keys, and push notifications with number matching.
  • Often accepted but weaker: SMS text codes. Some carriers still allow them; others exclude them for administrator accounts. Phone numbers can be hijacked, so plan to move away from SMS.
  • Not MFA: a security question, a second password, or a PIN on the same device. Some applications explicitly warn about this.
  • Watch for exceptions: if MFA is enabled but a conditional-access rule exempts the office IP address, or a few legacy accounts are excluded because an old scanner or app could not handle it, you may not be able to answer yes honestly. Legacy authentication protocols in Microsoft 365 are a classic hole.

How do you get MFA fully in place before a renewal deadline?

Renewal notices tend to arrive with a few weeks to respond. This is the order we recommend when a deadline is close.

  1. Inventory every way in. Email tenant, VPN, remote desktop, remote-support tools, cloud portals, backup console, firewall admin, and line-of-business applications. Vendors with remote access count.
  2. Turn on MFA for email and admins first. In Microsoft 365 this means security defaults or, on Business Premium, conditional access policies that require MFA everywhere with no location exceptions and legacy authentication blocked.
  3. Close remote access holes. Put MFA on the VPN or replace it. Remove exposed remote desktop entirely and use a gateway or cloud desktop with MFA instead.
  4. Protect backups. MFA on the backup console, a separate credential for the backup system, and immutable or offline copies.
  5. Deal with exceptions honestly. If an old application cannot support MFA, isolate it, document the compensating control, and disclose it on the application. Carriers respond far better to a documented exception than to a discovered one.
  6. Verify and document. Screenshots of the policies, a list of accounts with MFA status exported from the tenant, and a dated summary you can attach to the application and keep for the claim file.

For a 20 to 50 person office with Microsoft 365 the technical work usually fits inside one to two weeks, most of it spent enrolling staff and handling the few who resist. The change management is the hard part: a five-minute all-hands explanation of why the insurer requires it goes a long way.

Beyond MFA: what else is on the application?

MFA is the headline, but the same forms ask about endpoint detection and response, email filtering, patching cadence, security awareness training, tested backups, an incident response plan, and whether end-of-life systems are still in use. Our compliance services cover the technical side: walking the application line by line and fixing the gaps. When a claim does happen, having incident response already arranged is another item carriers reward.

If a renewal or a new application is sitting on your desk and you are not sure every MFA answer is true, call MainSail Data at (772) 794-1194 or request a free security assessment. We will verify each item technically so you can sign with confidence.