How to Secure Passkey Enrollment, Recovery, Endpoints, and Sessions

· Original article ↗

Summary

Passkeys strengthen authentication, but attackers can exploit enrollment, recovery, endpoints, or alternative sign-in flows. The article outlines controls for protecting the full account lifecycle and detecting suspicious activity after login.

Key points

  • Huntress researchers tracked the EvilTokens device-code phishing campaign across 344 organizations in five countries over about 16 days; victims could authorize an attacker-controlled client and give attackers a valid session without losing a password.
  • Passkey-themed phishing can use enrollment as bait to steer employees toward weaker authentication flows; this does not mean passkey cryptography was defeated.
  • Require strong verification and monitoring when users enroll or replace authenticators, recover accounts, or reset MFA.
  • Protect endpoints that handle authentication; the article says attacks manipulating Windows WebAuthn interactions have specific prerequisites, including local execution or access to the authentication process.
  • Choose synced or device-bound passkeys with their different dependencies in mind, and secure the associated accounts, spare keys, enrollment, and recovery processes.
  • Train employees to use trusted enrollment routes, verify unexpected support requests, recognize suspicious authorization prompts, and report mistakes or lost keys promptly.
  • Monitor activity after sign-in and, when compromise is confirmed, revoke sessions, remove unauthorized authenticators, and investigate persistence such as inbox rules, OAuth app grants, and forwarding addresses.

Article Details

Defense Focus
Protect the full account lifecycle around passkeys, including enrollment, recovery, authentication endpoints, and post-sign-in activity.
Detection Methods
  • Correlate unusual access with the user’s normal device, role, and authentication workflow.
  • Monitor for newly registered authentication methods and suspicious cloud activity.
  • Look for abnormal mailbox and file activity after sign-in.
  • Investigate persistence indicators such as inbox rules, OAuth app grants, and forwarding addresses.
  • Review authentication method and policy when investigating suspicious successful sign-ins.
Data Sources
  • Identity sign-in and authentication-method registration events
  • Endpoint security telemetry from managed devices
  • Cloud activity
  • Mailbox and file activity
  • Inbox rules, OAuth app grants, and forwarding addresses
Platforms
  • Endpoint detection and response (EDR)
Defensive Actions
  • Require strong verification before adding or replacing authenticators or resetting MFA.
  • Use phishing-resistant authentication, and distinguish FIDO2/WebAuthn hardware-key use from hardware tokens generating one-time codes.
  • Manage and monitor every endpoint used to access company resources; install updates promptly and restrict extensions and software to approved lists.
  • Use trusted enrollment routes and established channels to verify unexpected support requests.
  • Train users to question unexpected device-code, biometric, or security-key prompts and report suspicious requests or mistaken approvals promptly.
  • For confirmed compromise, revoke sessions, remove unauthorized authentication methods, investigate persistence, and review account activity.

MITRE ATT&CK

Vendors

Products

Related Articles