Breach Risk Direct.
Security Controls

Rolling Out Phishing-Resistant MFA: A 9-Step Plan Underwriters Will Actually Credit

Underwriters now ask which MFA you use, not just whether you have it. Here's the order to roll out FIDO2 and passkeys, how to handle legacy protocols and break-glass accounts, and how to prove it.

Breach Risk Direct editorial team · November 2026 · 7 min read

Why "MFA Everywhere" No Longer Clears the Questionnaire

The simple yes/no MFA question is fading from cyber applications. Many carriers and wholesale brokers, in London, North America, Europe and Asia-Pacific alike, now ask what kind of MFA protects email, remote access and privileged accounts, and whether anyone can get around it. SMS codes, one-time codes and plain push approvals can all be phished through adversary-in-the-middle proxies, or worn down by push bombing. Underwriters treat them as weaker controls, even when the box says "MFA enabled."

That makes phishing-resistant MFA for cyber insurance a budgeting question as well as a security one. You probably can't move every account to FIDO2 by renewal, and you don't need to. You need a defensible order of work, documented well enough that an underwriter can see the riskiest identities are protected and the remaining gaps are known and scheduled. Regulators are leaning the same way. The EU's NIS2 and DORA regimes, Australia's Essential Eight and the Monetary Authority of Singapore's technology risk guidance all push toward stronger authentication for privileged access, though the exact wording differs, so check what applies to you. The steps below are in the order you should do them.

Advertisement

Inventory Identities and Rank Them by Blast Radius

Start with a list of every identity that can authenticate, not a list of employees. That means human accounts, admin accounts, service accounts, shared mailboxes and any third-party or outsourced IT accounts. Pull it from your identity provider, your cloud consoles and your remote-access tools.

Then sort it into four tiers:

  1. Tier 0: global and domain admins, identity provider admins, backup console admins, and MSP accounts with tenant-wide rights.
  2. Tier 1: anyone who can move money or change payment details, such as finance, treasury and accounts payable.
  3. Tier 2: executives, HR and anyone with bulk access to personal or regulated data.
  4. Tier 3: everyone else.

A ransomware crew wants Tier 0. A business email compromise crew wants Tier 1. Fund the rollout in that order.

Match the Authenticator to the Tier

Different tiers need different factors. FIDO2 hardware security keys are the strongest choice for admins because the credential sits on a physical device and can't be copied or synced. Device-bound passkeys in Windows Hello for Business, macOS or a managed phone authenticator are a sensible default for most staff. Synced passkeys are convenient, but the credential lives in a consumer cloud account, so some underwriters and auditors rate them lower for privileged use.

MethodPhishing-resistant?Best fitTypical 2026 cost
FIDO2 hardware key (YubiKey, Google Titan, Feitian, Token2)YesTier 0, Tier 1Roughly $25–$90 per key; budget two per user
Device-bound passkey / Windows Hello for BusinessYesTiers 1–3 on managed devicesOften included in existing OS and identity licensing
Synced passkeyYes, but recovery depends on the cloud accountTier 3, contractorsOften included
Push with number matchingNo (fatigue-resistant only)Interim for Tier 3Often included
SMS / voice codesNoRecovery fallback only, then retireTelecom fees vary by country

These are indicative ranges for typical 2026 pricing. Local prices, import duties and reseller margins vary, so confirm with vendors.

Move Privileged and Payment Accounts First

Here's a hypothetical. Say a 120-person company has 10 Tier 0 admins and 14 finance users. Two keys each for those 24 people is 48 keys. At around $55 a key, the hardware comes to roughly $2,600. Add perhaps a week of internal admin time, and the two tiers underwriters probe hardest are covered. For most mid-size teams, buying keys for Tiers 0 and 1 and using platform passkeys for everyone else is the better split: you get the strongest protection where losses concentrate without buying hardware for 120 people.

Give every admin a separate, cloud-only admin account with no mailbox, used only from a managed device. Enroll the backup key the same day and store it apart from the primary. If you use an MSP, make FIDO2 on their delegated access to your tenant a contract condition.

Shut Down Legacy Protocols and Other Bypass Routes

Phishing-resistant MFA does nothing if an attacker can log in another way. Underwriters, and the external scanning tools some carriers run against applicants, look for these:

  • IMAP, POP and SMTP AUTH still enabled for mailboxes
  • Legacy or basic authentication on VPNs, older on-premises Exchange or ERP portals
  • Exposed RDP and VPN gateways that only ask for a password
  • Service accounts with interactive sign-in rights and passwords that never expire
  • App passwords issued years ago and forgotten

Block legacy authentication at the identity provider, then review sign-in logs for about 30 days to catch whatever breaks. Where an old system can't support modern authentication, put it behind an identity-aware proxy or ZTNA gateway that enforces FIDO2 in front of it. Record those systems as named, dated exceptions instead of hiding them.

Design Break-Glass Accounts That Don't Become the Hole

Every tenant needs emergency access accounts for when the identity provider, the MFA service or federation fails. The usual mistake is leaving them with a long password and no MFA, which makes them the most attractive accounts in the company.

Do this instead. Create two cloud-only break-glass accounts. Protect each with its own FIDO2 key, kept in separate physical locations such as two safes or two offices. Exclude them only from the conditional access policies that could lock them out, and alert on every sign-in. Test them quarterly and log each test. When an underwriter asks "what's excluded from MFA?", the answer should be exactly two accounts, monitored and protected by hardware keys.

Enforce Through Conditional Access in Waves

Enrolling people isn't the same as enforcing the policy. Use conditional access, such as Microsoft Entra authentication strengths, Okta authentication policies or Google Workspace security key enforcement, to require a phishing-resistant method by tier. Licensing tiers that include conditional access often run somewhere around $6–$12 per user per month at typical 2026 list prices, but bundles and contracts vary widely.

A realistic sequence:

  1. Weeks 1–2: enforce on Tier 0 and the admin portals.
  2. Weeks 3–6: enforce on Tiers 1 and 2, and require a managed or compliant device.
  3. Weeks 7–12: run the policy in report-only mode for Tier 3, fix what fails, then enforce.

Report-only mode is your safety net. It shows who would be blocked before anyone actually is.

Close the Help Desk and Recovery Gap

Attackers who can't phish a key will try the help desk, impersonating an employee to get a reset or a new device enrolled. MFA fatigue attack prevention isn't finished when push approvals go away. Recovery needs the same strength as sign-in.

  • Require identity verification by video call against a photo ID, or approval from the person's manager, before any reset for Tiers 0–2.
  • Issue temporary access passes that expire within hours, not new permanent passwords.
  • Alert the user and the security team whenever a new authenticator is registered.
  • For Tier 3 users still on push during the transition, turn on number matching and sign-in location context.

Write the procedure down. Underwriters increasingly ask about help-desk verification, so expect the question.

Build an Evidence Pack That Survives Underwriting Review

Underwriters credit what you can show, not what you describe. Assemble a short pack before the broker submission:

  • Coverage figures by tier: the percentage of accounts on a phishing-resistant method, exported from the identity provider
  • Screenshots or exports of the enforcing conditional access policies, with dates
  • Confirmation that legacy authentication is blocked, plus a dated exceptions register for each remaining system
  • The break-glass design, the alerting rule and the latest quarterly test log
  • The help-desk recovery procedure and the Tier 3 completion date

Answer the questionnaire exactly as the pack supports. Overstating MFA coverage on an application can give a carrier grounds to dispute a claim, so ask your broker or a licensed coverage adviser to review any answer that needs caveats. Your decision rule for this week: if Tier 0 isn't on FIDO2 keys under enforced conditional access yet, order the keys before anything else on this list.

Frequently asked questions

Do underwriters require FIDO2 keys for every employee?

Generally, no. Most carriers concentrate on privileged access, email and remote access, and on whether anyone can bypass MFA. Hardware keys for admins and finance, platform passkeys for everyone else, and a documented completion date for any remaining push users is usually a credible position. Requirements vary by carrier and region, so check the specific questionnaire with your broker.

Are synced passkeys good enough for cyber insurance purposes?

Synced passkeys resist phishing and are a big improvement on SMS or push for general staff. The concern is that the credential and its recovery depend on a consumer cloud account. That's why many security teams and some underwriters prefer device-bound passkeys or hardware keys for privileged and payment accounts. Use synced passkeys for Tier 3 and keep them away from admin roles.

What if a critical legacy system can't support modern authentication?

Put it behind an identity-aware proxy, ZTNA gateway or privileged access tool that enforces phishing-resistant MFA before anyone reaches the system. Restrict network access to it, and record it in an exceptions register with an owner and a replacement date. Underwriters tend to accept a known, controlled and dated exception much more readily than one they find on their own.

Written by the Breach Risk Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.