Blog

The Three MFA Questions That Decide Your Renewal

Multi-factor authentication, usually shortened to MFA, sounds like a buzzword until you sit down with a cyber-insurance renewal form. Then it turns into the question that decides whether you get a quote at all.

Here is the plain definition. MFA means a password alone is not enough to get in. You also need a second thing: a code or a prompt on your phone, a small hardware key, or a fingerprint. Travelers prints a tidy version of this on its MFA supplement: a password is something you know, a phone is something you have, a fingerprint is something you are, and the carrier wants two of them.

In our review of 13 public carrier applications (November 2026), 12 asked about MFA in some form. But they rarely ask "do you have MFA?" as one question. They split it into three, and each one is a separate place where a stolen password can hurt you.

Question one: can a stolen password open your email?

Ten of the 13 applications we read ask about MFA on email by name. That makes sense. Email is where password resets land, where invoices get approved, and where a criminal can quietly watch a conversation before stepping into it.

When I ran IT at a company of about 200 people, email was always the place where the exceptions hid. The finance team had MFA turned on. Most of the office did too. Then there was a shared mailbox nobody owned, an older phone mail app that never asked for a second factor, and a couple of people who had been "temporarily" excused two years earlier.

The carrier is not asking whether most people have it. It is asking whether anyone can read company email with just a password. If the honest answer is "mostly not," the answer on the form is no until you close the gaps.

Question two: can a stolen password open the door into your network?

Eleven of the 13 applications ask about MFA for remote access. Remote access is any way to reach the office systems from outside: a VPN (a private, encrypted connection into the office network), remote desktop, or a remote-support tool your IT provider uses.

This is the question owners most often get wrong, and it's rarely through carelessness. Remote access tends to collect side doors over the years. There is the VPN everyone knows about. Then there is the remote-support tool the outside IT company installed, the vendor who maintains one piece of equipment and has their own way in, and the old remote desktop connection somebody set up during a busy season and never shut off.

Travelers' MFA supplement makes the point directly: MFA has to cover contractors and vendors who can reach your systems, not just employees. If your IT provider has a standing exception "for after-hours support," that is a remote door without MFA, and the form wants to know about it.

Question three: can a stolen password open an administrator account?

Six of the 13 applications ask by name whether administrator accounts are protected by MFA. Several more ask related questions about how those accounts are handled.

An administrator account is one that can change settings for everyone: create users, turn off security tools, delete backups. If a criminal gets one of these, they don't have to break in anywhere else. They already hold the keys.

At a company our size, admin rights spread quietly. The IT provider has them, which is expected. So does the person who set up the phone system, the former office manager whose account was never fully cut back, and maybe the owner, "just in case." Each of those accounts needs MFA, and frankly, most of them shouldn't be admin accounts at all.

Why carriers care this much

Carriers are not being fussy. MFA is one of the few controls that blocks a whole category of attack outright. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) calls MFA one of the most effective steps an organization can take and publishes plain guidance on it at cisa.gov/MFA.

The underwriter's logic is simple. Passwords get phished, reused and guessed. If a stolen password alone can open email, remote access or an admin account, the carrier is insuring a company whose front door is one phishing email away from open.

What "yes" really means on the form

Some forms make the stakes explicit. Tokio Marine HCC's NetGuard Plus application states that a "yes" on MFA is a representation that MFA is in force and will stay in force for the policy period. That isn't a promise to work on it. It's a statement of fact that the carrier will rely on.

So read each box as a strict test:

  • Required, not optional. MFA you can skip is not MFA.
  • For everyone. That includes vendors, the IT provider, and the CEO.
  • Every door. That covers webmail, phone mail apps, the VPN, the remote-support tool and every admin console.

If any of those fail, write down the exception, fix it, and only then answer yes.

The common snags, and how they get solved

"Our older system doesn't support MFA." This is usually a remote door that should sit behind something that does, such as a VPN that requires MFA, so the old system is no longer reachable directly from the internet.

"Our IT provider needs to get in quickly." They can, with MFA. A reputable provider already uses it for its own staff. If yours pushes back, that tells you something.

"Staff will hate it." They usually grumble for about a week. Modern phone prompts take a couple of seconds, and most systems can remember a trusted device so people aren't prompted all day.

"We use Microsoft 365, so we're covered." Not automatically. Microsoft offers a free baseline called security defaults that turns on MFA for everyone, described in Microsoft's documentation, but someone has to turn it on or replace it with stricter settings. Google Workspace has a similar setting. Neither one covers your VPN or your remote-support tool.

What to do Monday morning

  1. Book an hour with whoever runs your Microsoft 365 or Google Workspace account and your remote-access tools, whether that's your own IT person or your outside provider.
  2. Walk the three boxes one at a time: email, remote access, administrator accounts. For each one, ask, "Is MFA required for every single person who can get in this way, including vendors?"
  3. List every exception by name: the shared mailbox, the vendor login, the old remote desktop. An exception you can name is one you can fix.
  4. Put a date on each fix, and don't answer yes on the application until the fix is done and someone has checked it.
  5. Save the evidence: a screenshot of the setting and the date you checked. You will want it at renewal, and you'll be glad to have it if there's ever a claim.

All essays