FIDO vs FIDO2: what changed for security keys
Key takeaways
- FIDO2 lets security keys serve as passwordless authenticators, while older U2F keys mainly act as a second factor after a password.
- FIDO2 combines WebAuthn, the website-facing browser interface, with CTAP2, which adds PIN operations and discoverable credentials, while keeping the same public-key, phishing-resistant model.
- Touching a key proves user presence, a PIN or biometric adds user verification, and a FIDO2 PIN authorizes the key locally, not at the website.
- Register a spare key separately and test both, because passkeys on a hardware key are device-bound, and resetting a YubiKey FIDO2 invalidates previously created credentials.
FIDO2 expanded hardware security keys from a password-plus-key experience into tools that can also support passwordless login. The change combines standardized browser integration with richer communication between devices and authenticators, including support for local user verification. Older FIDO U2F keys can still provide second-factor authentication where supported; FIDO2 adds capabilities rather than making every earlier key obsolete. (fidoalliance.org)
What is the difference between FIDO and FIDO2?
FIDO is the broader family of authentication standards, while FIDO2 is a specific set of standards within that family. In comparisons about security keys, “FIDO” usually means the earlier Universal Second Factor standard, or U2F. That distinction matters: the earlier FIDO Universal Authentication Framework, or UAF, already supported passwordless authentication, so passwordless access did not begin with FIDO2 across the entire FIDO ecosystem. (fidoalliance.org)
For hardware-key users, the practical difference is this: U2F was designed to supplement an existing login, typically a password. FIDO2 supports that role and enables additional experiences, including signing in with a key and local verification instead of a website password. Whether you actually get that experience depends on the key, browser, operating system, and service. (fidoalliance.org)
| Capability | Earlier FIDO U2F keys | FIDO2 keys |
|---|---|---|
| Typical role | Second factor after a password | Second factor or passwordless authenticator |
| External-key protocol | U2F, also called CTAP1 | CTAP2; U2F support depends on the model |
| User interaction | Usually a touch to confirm presence | Touch, with PIN or biometric verification where supported and required |
| Discoverable credentials | Not supported | Supported by capable authenticators |
| Website integration | Can work through WebAuthn for compatible second-factor flows | WebAuthn supports richer authentication flows |
The table describes protocol capabilities, not promises about every product. A FIDO2 label does not guarantee a fingerprint reader, identical storage capacity, or acceptance by every website. (fidoalliance.org)
The security foundation stayed familiar
Both approaches use public-key cryptography rather than asking the security key to disclose a reusable login secret. During registration, the service receives a public key associated with a credential. During authentication, the authenticator signs a challenge, and the service checks that signature. (fidoalliance.org)
Credentials are scoped to the relevant service. With a correctly implemented browser and service, a lookalike phishing domain cannot simply request a valid authentication response for the legitimate site. This phishing resistance was already an important property of U2F; FIDO2 did not introduce it from scratch. (fidoalliance.org)
The meaningful upgrade is therefore not “insecure keys became secure.” It is that an existing secure authentication model gained more flexible login experiences and broader standardized integration. (fidoalliance.org)
WebAuthn and CTAP2 changed the connection
FIDO2 brings together two complementary pieces. WebAuthn defines how websites request public-key authentication through browsers and platforms. CTAP defines communication between those clients and external authenticators, such as hardware security keys. (fidoalliance.org)
WebAuthn handles the website-facing request
WebAuthn provides a standard interface for creating and using credentials. A website can express requirements such as whether user verification is necessary or whether it needs a discoverable credential. The browser coordinates that request with an available authenticator rather than the website directly controlling the hardware. (w3.org)
CTAP2 enables richer authenticator behavior
CTAP2 supports capabilities beyond the earlier U2F exchange, including PIN-related operations and discoverable credentials. These features help an external key participate in passwordless authentication. The available connection—such as USB or NFC—still depends on the particular key and client device. (fidoalliance.org)
From confirming presence to verifying the user
Touching a security key generally establishes user presence: someone is physically interacting with it. User verification goes further by checking an authorized user through a local method, such as a PIN or a supported biometric. A simple touch is not automatically a fingerprint check, even when the key has a touch-sensitive surface. (w3.org)
A FIDO2 PIN is also different from a website password. It authorizes use of the authenticator locally rather than being sent to the website for verification. Where a biometric is used, WebAuthn does not reveal the biometric data to the website. (developers.yubico.com)
This distinction explains how passwordless login can still involve multiple factors: possession of the key plus a PIN or biometric verification. However, a FIDO2 key does not necessarily request verification in every flow; requirements depend on the service and authenticator configuration. (developers.yubico.com)
Discoverable credentials connect security keys and passkeys
A discoverable credential lets the authenticator locate a credential for a service without first receiving its credential identifier from that service. This enables account-selection experiences that can avoid entering a username first. Older documentation often calls these “resident keys.” (w3.org)
Passkeys can be device-bound or synced through a passkey provider. A passkey stored on a hardware security key is device-bound: it stays with that key rather than automatically appearing on your other devices. “Passkey” describes the credential, while “security key” describes the physical authenticator holding it. (fidoalliance.org)
Discoverable credentials also introduce a practical buying consideration: storage. Hardware keys have model-specific limits for these credentials, and that capacity is distinct from their ability to handle non-discoverable credentials. Check the manufacturer's documentation instead of assuming a listed passkey limit is a limit on every account the key can protect. (developers.yubico.com)
Do you need to replace an older security key?
Not necessarily. An older U2F key can remain useful when your service accepts it as a second factor, including through compatible WebAuthn implementations. Replacement becomes relevant when you need capabilities that U2F cannot supply, such as discoverable credentials or the user verification required by a particular passwordless flow. (fidoalliance.org)
Before buying FIDO2 keys, check the complete login path rather than just the product label:
- Account support: Confirm whether the service accepts external security keys for second-factor authentication, passwordless access, or both.
- Device connection: Match USB connectors and NFC support to the computers and phones you actually use.
- Verification method: Decide whether PIN-based verification meets your needs or whether you require a biometric-capable model.
- Credential capacity: Check discoverable-credential storage if you expect to keep multiple passkeys on the key.
- Workplace restrictions: Ask whether your organization limits permitted authenticators or requires particular verification settings.
These checks address different parts of compatibility. A key can support the necessary protocol while still failing to meet a service's registration policy or your device's connection requirements. (w3.org)
Set up recovery before relying on the key
Device-bound credentials make backup planning important. Losing a hardware key does not cause its passkeys to reappear on a replacement, and registering a spare creates separate credentials rather than cloning the original key. FIDO Alliance enterprise guidance recommends providing two hardware keys so one can serve as a backup. (fidoalliance.org)
Use this setup sequence:
- Register your primary key in the account's security settings, following its security-key or passkey flow.
- Enroll a spare separately wherever the service permits additional authenticators, then store it apart from the primary key.
- Test both keys before removing an existing sign-in method.
- Review recovery options and protect any backup codes or recovery account.
- Check reset consequences before resetting a malfunctioning key. For example, a YubiKey FIDO2 reset invalidates previously created credentials.
Treat recovery as part of identity protection, not an afterthought. A weak fallback can provide an easier route into an account even when its everyday FIDO authentication is strong. Protecting the login while neglecting recovery leaves an avoidable gap. (fidoalliance.org)
The practical takeaway
FIDO2 changed what security keys can do, not the basic reason they are valuable. It retained public-key, phishing-resistant authentication while adding the capabilities needed for richer passwordless experiences. (fidoalliance.org)
Keep an older key if it still meets your account requirements. Choose a FIDO2 model when you need its additional capabilities, verify the entire login flow, and register a backup before making it essential to your access. (fidoalliance.org)
Related guides
Sources
- FIDO User Authentication Specifications | FIDO Alliance
- User Authentication Specifications | FIDO Alliance
- FIDO Security Reference
- Web Authentication: An API for accessing Public Key Credentials - Level 2
- Client to Authenticator Protocol (CTAP)
- Web Authentication: An API for accessing Public Key Credentials - Level 3
- FAQ
- Resident Keys
- FIDO Passkeys: Passwordless Authentication | FIDO Alliance
- Key generation
- White Paper: Replacing Password-Only Authentication with Passkeys in the Enterprise | FIDO Alliance
- fidoalliance.org: FIDO EDWG Spring 2023 Paper 2 Replacing Password Only Authentication FINALv3.docx