Skip to main content
The state of ai impact assessment
Passkey Enrollment Is the New Attack SurfaceFIDO & Passkeys
5 min readFor IAM Architects

Passkey Enrollment Is the New Attack Surface

Passkeys can't be phished at sign-in. A credential bound to the real origin gives a lookalike domain nothing to replay. So attackers have shifted tactics, focusing on adding their own credentials.

Okta Threat Intelligence documented a vishing campaign (tracked by Okta as O-UNC-066 and by Palo Alto Networks Unit 42 as CL-CRI-1147) where a caller tells an employee they must register a new passkey. A live operator guides the victim through a fake Microsoft Entra sign-in page, captures the password and MFA code, replays them against the real account, and enrolls the attacker's passkey. Okta's report, published July 5, 2026, notes the pretext sounds plausible because Microsoft administrators can now run passkey registration campaigns that prompt users at sign-in, and in some circumstances, those prompts are on by default.

The FIDO Alliance Passkey Index reports 36% of successful sign-ins now use a passkey. As adoption climbs, enrollment becomes the soft spot. This guide will help you secure it.

Preparation Checklist

  • Admin access to your identity provider (Microsoft Entra ID, Okta, or equivalent) with rights to edit authentication methods and Conditional Access policies.
  • Log export to your SIEM for authentication method registration events.
  • An inventory of accounts still relying on a password plus a one-time code. These are vulnerable to attacker enrollment.
  • A help desk process document. Recovery is part of the attack surface.
  • A decision on your assurance model: which signals prove a person's identity when no registered authenticator exists yet.

Step-by-Step Implementation

1. Treat registration as a privileged action.
Adding an authenticator is a credential change, so protect it like one. Require a fresh, strong authentication event before the registration flow starts, not a session that's hours old. In Microsoft Entra, use Conditional Access with the "Register security information" user action as the target. In Okta, enforce re-authentication through authenticator enrollment policies.

2. Require phishing-resistant proof for adding a second authenticator.
If a user already has a passkey, make adding another one require an existing passkey. A password and a one-time code should not be enough to extend a phishing-resistant footprint. This rule breaks the Okta-documented chain because the captured password and MFA code no longer authorize enrollment.

3. Gate first-time enrollment with a Temporary Access Pass or verified identity.
For users with no passkey yet, the bootstrap moment is your highest risk. Issue a time-limited, single-use credential (Entra's Temporary Access Pass, or an equivalent enrollment token) delivered through a channel the user didn't initiate. Set a short lifetime and one-use only. For higher-risk roles, add identity proofing or manager approval before issuance.

4. Restrict enrollment by network and device context.
Require registration from a compliant, managed device or a trusted network location. A remote attacker working from a fake page ends up enrolling from an unmanaged device in an unexpected location, which a Conditional Access policy can block outright.

5. Control which authenticators can register.
Use AAGUID (Authenticator Attestation GUID) allow-lists where your IdP supports them, so only approved authenticator models can enroll. Decide deliberately whether to permit synced passkeys or require device-bound, hardware-backed ones for admins and other privileged accounts.

6. Lock down recovery and help desk paths.
Attackers who can't enroll directly will try recovery. Remove SMS and email as standalone recovery factors for privileged users. Require help desk staff to verify identity through a documented, out-of-band process, and never let a caller's urgency override it. No one on the help desk should be able to issue an enrollment credential on a phone call alone.

7. Notify on every enrollment.
Send an immediate message to the user's existing channels when any authenticator is added, with a one-click "this wasn't me" path that revokes the new credential and forces a session reset. Attackers lose their foothold quickly when the real user is notified within minutes.

8. Train people on the specific script.
Generic phishing awareness won't suffice. Teach one rule: your organization will never ask you to register a passkey because someone called you. Enrollment is something you start yourself, from a bookmarked portal, or something your IT team initiates through a pre-announced campaign. If your admins run registration campaigns, announce them in advance through an internal channel so a legitimate prompt is never a surprise. Tell users to hang up and call back using a number from the internal directory. Run vishing simulations that test this behavior, not just email clicks.

Validation

Don't assume the controls work; test them.

  • Attempt enrollment with password plus MFA only. On a test account that already has a passkey, try to add a second authenticator without presenting the first. The attempt should fail.
  • Attempt enrollment from an unmanaged device. Confirm the Conditional Access policy blocks it, and check that the sign-in log records the policy result.
  • Test the recovery path. Have a colleague play the caller and try to talk your help desk into issuing an enrollment credential. Treat success as a process failure, then fix the script.
  • Confirm alerting fires. Register a test authenticator and verify the user notification arrives and your SIEM ingests the event.
  • Check the Temporary Access Pass lifecycle. Verify it expires and can't be reused.

Maintenance and Ongoing Tasks

  • Monitor registration events continuously. Alert on authenticator additions followed by sign-ins from new locations, multiple registrations in a short window, and registrations outside business hours. In Entra, the audit log category for authentication method changes is your primary feed.
  • Review the password-plus-code holdouts. Every account still on that pair is exposed to attacker-driven enrollment. Track the count and drive it down.
  • Audit enrollment policy exceptions quarterly. Exceptions made for a deadline tend to become permanent. Run them through your Certification Campaign process.
  • Re-read vendor defaults after platform changes. The default-on registration prompts in Microsoft's tooling show how a vendor change can alter what users see and expect. Check release notes and adjust your user messaging and policies when behavior shifts.
  • Refresh training on a schedule, and update the scripted pretexts as attackers change them.

Passkeys closed the sign-in door. Make sure the enrollment door has a lock of equal strength.

promotional banner for evidence for every CC6 control checklist

You Might Also Like