Tutorials · Security Operations

How to Roll Out Phishing-Resistant MFA With Passkeys and FIDO2 Security Keys

SMS codes and push approvals can be phished or spammed. Passkeys and FIDO2 security keys cannot. A rollout plan for admins first, then all staff.

Intermediate15 min6 steps

Before you start

  • An identity provider that supports FIDO2/passkeys (Microsoft Entra ID, Google Workspace, Okta and others)
  • Two FIDO2 security keys per admin (one primary, one backup)

Step by step

  1. Start with admins

    Admins, finance and executives are targeted most. Enrol them first, with two keys each, kept in different places.

  2. Enable the method in your identity provider

    Turn on passkeys/FIDO2 as an authentication method and allow registration for a pilot group.

  3. Register keys in person

    Hand out keys at a short session: users register both keys and set a PIN. Record the key serials in your asset list.

  4. Require it for admin portals

    Use conditional access or sign-on policies so admin roles can only sign in with phishing-resistant methods.

  5. Extend to all staff

    Allow platform passkeys (Windows Hello, Touch ID, Android, iOS) for everyone, and phase out SMS and voice codes.

  6. Plan for lost keys

    Define a recovery process with identity checks by the helpdesk and a temporary access pass. Never fall back to SMS for admins.

Pro tips

  • Network devices and NavCloud admin accounts also deserve MFA: enable it wherever available.
  • Keep a few spare keys at the IT desk for fast replacement.