Cybersecurity glossary

What is a WebAuthn Authenticator?

Learn what a WebAuthn authenticator is, how platform and roaming authenticators store FIDO credentials, user verification options, and how to choose authenticators for phishing-resistant login.

Identity and accessUpdated July 23, 2026
Also known asFIDO authenticatorPlatform authenticatorRoaming authenticator

Definition

A WebAuthn authenticator is a hardware or platform component that generates and stores public-key credentials and produces signed WebAuthn assertions—such as a laptop’s secure enclave, a phone’s passkey provider, or a USB/NFC security key.

Why the authenticator is the trust root

WebAuthn ceremonies are only as strong as the component that holds the private key. A WebAuthn authenticator performs that role: create credentials, keep secrets offline from the website, and sign origin-bound challenges after user verification.

Choosing authenticators is therefore both a UX decision and a security-policy decision.

Authenticator categories

Platform authenticators

Built into phones and laptops; power most consumer passkey experiences.

Roaming authenticators

Portable security keys for shared machines and admin backups.

Synced passkey providers

Cloud-backed credential sync across a user’s devices.

Device-bound keys

Credentials that never leave a single authenticator.

Multi-protocol devices

Keys that also speak OTP or smart-card modes—prefer FIDO for phishing resistance.

Hybrid transports

Phone authenticators approving desktop logins over QR/BLE.

What the authenticator does in a ceremony

1

Receive request via client

Browser/OS delivers WebAuthn options over platform APIs or CTAP.

2

Check RP ID binding

Authenticator ensures the request matches the credential’s relying party.

3

Obtain user consent

Presence gesture and optional PIN/biometric user verification.

4

Perform private-key operation

Generate a new credential or sign the challenge.

5

Return authenticator data

Flags, counter, and signature go back to the relying party for verification.

Selection considerations

NeedPreferWhy
Consumer conveniencePlatform synced passkeysLow friction, good recovery
Shared kiosk/adminRoaming security keysPortable, controllable inventory
High assurance workforceDevice-bound + attestationPolicy on approved hardware
Backup resilienceAt least two authenticatorsAvoid single-device lockout

Operational checklist

  • Support both platform and roaming authenticators unless policy forbids one.
  • Require user verification for high-assurance accounts.
  • Enroll spare authenticators before enforcing WebAuthn-only login.
  • Monitor authenticator add/remove events as privileged changes.
  • Use attestation only when you have a clear enterprise need and privacy review.
  • Educate users not to approve unexpected authenticator prompts.
  • Revoke credentials promptly when devices are lost or employees leave.
  • Test hybrid/cross-device flows used by your real user population.

The practical takeaway

A WebAuthn authenticator is the key-holding device or platform service behind passkeys and security-key login. It provides phishing-resistant proofs without sharing biometrics with websites.

Match authenticator types to user populations, always enroll backups, and govern lifecycle events with the same rigor you apply to privileged credentials.

Related security terms

Frequently asked questions

What is a WebAuthn authenticator in simple terms?

It is the thing that holds your login key—your phone, laptop, or security key—and signs a challenge when you unlock it with biometrics, a PIN, or a touch.

What is a platform authenticator?

An authenticator built into the device OS/hardware, such as Windows Hello, Touch ID/Face ID secure enclave integrations, or Android platform authenticators.

What is a roaming authenticator?

A separate device you can move between computers—typically a FIDO2 USB/NFC/Bluetooth security key.

What is user verification (UV)?

Proof that a person unlocked the authenticator via PIN or biometrics, beyond mere presence (touch).

Can one user have multiple authenticators?

Yes, and they should—especially for backups—so losing one device does not lock them out.

Do authenticators send fingerprints to websites?

No. Biometrics stay local to the authenticator/platform; websites receive cryptographic proofs only.

How do enterprises restrict authenticator types?

Using attestation and authenticator selection criteria to allow only approved security keys or platform classes.

References

Explore authoritative guidance and frameworks related to webauthn authenticator.

Explore every security definition

Return to the glossary to search by term, alias, starting letter, or security category.

Browse glossary