A FIDO2 security key is a physical authenticator that stores credentials on the device and requires possession to sign in. A passkey is a FIDO2 credential that lives on a phone, computer, or password manager and can sync across devices. Both support phishing resistant authentication, but they serve different operational and usability needs.
Why a FIDO2 security key and a passkey are not the same thing
A FIDO2 security key is a physical authenticator you carry and present at sign-in. A passkey is a FIDO2 credential that usually lives on a phone, laptop, or password manager and can sync across devices. The distinction matters because one is device-bound hardware, while the other is a more portable credential model designed for easier recovery and everyday use.
The practical difference is not whether both are phishing resistant, because they are. It is how the credential is stored, how it is recovered, and how much user friction it introduces. A security key usually means explicit possession of the device. A passkey usually means the authenticator is embedded in a broader platform or sync ecosystem, so the operational trade-off is convenience versus a more tightly controlled physical factor.
How the sign-in experience differs in practice
With a security key, the user signs in by touching or inserting the key, often after entering a username or starting a login flow. That makes the factor easy to explain, audit, and segment by use case. It is especially useful when you want a separate, visible authenticator for high-trust access or a backup method that is not tied to a single consumer device.
With a passkey, the user may unlock it with biometrics, a device PIN, or a local device gesture, and then complete sign-in without typing a password. Because the credential can be synced, users can move between devices with less ceremony. That is the main usability gain, but it also means the account recovery and device trust model become more important than they are with a standalone hardware key. For a deeper breakdown of the underlying authentication model, see the NIST SP 800-63 Digital Identity Guidelines.
Security keys and passkeys also differ in where they fit best. A hardware key is often the cleaner choice for shared workstations, controlled admin access, or users who need a clearly separable authenticator. A passkey is usually the better default for consumer and employee populations that need fewer login prompts and simpler recovery without giving up phishing resistance.
Choosing between portability, recovery, and control
The choice is usually about operational fit, not cryptographic strength. If your main goal is maximum portability and lower help desk load, passkeys are attractive because they can be restored and used across devices. If your main goal is a physically distinct authenticator with a simpler possession story, a security key is easier to reason about and may be easier to standardise in tightly managed environments. The Passwordless and Passkeys Guide covers how those choices affect rollout and recovery.
From a control standpoint, the biggest difference is what happens when the user loses a device or changes hardware. A passkey program needs a recovery path that is secure enough not to undo the phishing resistance it was meant to create. A security-key program needs backup keys, enrollment discipline, and a lost-key process. If you are designing the broader sign-in stack, the Hardware Security Keys Guide is the most relevant internal reference for the physical authenticator side, while the Authentication Guide helps place both options in the wider assurance model.
In other words, the decision is less about “which is stronger” and more about which trust boundary you want to operate. A security key keeps the factor in a dedicated object. A passkey moves that factor into the user’s device ecosystem and may spread it across multiple endpoints. That can improve adoption, but it also changes who and what you trust for recovery, sync, and endpoint security.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, NIST SP 800-53 Rev 5, CIS Controls v8 and OWASP ASVS set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | Covers authenticator assurance and phishing-resistant sign-in for FIDO2 and passkeys. |
| Recommendation — Use phishing-resistant authenticator guidance to choose the right assurance level for the login experience. | ||
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | Applies because the question compares authenticators for workforce and user sign-in. |
| IA-5 — Authenticator Management | Applies because the difference includes credential storage, recovery, and lifecycle handling. | |
| Recommendation — Require strong user authentication and align authenticator choice to access sensitivity. Manage authenticator enrollment, backup, replacement, and revocation as a lifecycle control. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Applies because selecting between passkeys and keys changes how access is granted and recovered. |
| Recommendation — Standardise approved authenticators and remove unnecessary fallback access paths. | ||
| OWASP ASVS | V6 — Authentication | Applies because both mechanisms are authentication methods and need verification requirements. |
| Recommendation — Verify that authentication controls support phishing-resistant sign-in and secure recovery. | ||
Practitioner Guidance
What to prioritise: Decide whether your programme optimises for hardware separation or for user convenience and recoverability. If the account set includes admins, sensitive internal systems, or shared-device scenarios, a hardware key remains the clearer operational control. If the user population is broad and support burden is the constraint, passkeys usually deliver better adoption.
What to verify: Confirm how recovery works before you roll out synced passkeys. The critical question is whether losing a device creates a safe re-enrollment path or a weaker fallback that reintroduces phishing risk. Also verify whether your backup-key process is realistic enough that users will actually follow it.
Common mistake: Treating passkeys and security keys as interchangeable. They both use FIDO2-style authentication, but they produce different lifecycle, recovery, and user-experience outcomes. A programme that ignores those differences often ends up with either avoidable help desk friction or an overly permissive recovery flow.
Practitioner takeaway: Use security keys when you need a distinct physical factor with tight control, and use passkeys when the main objective is phishing-resistant sign-in with lower friction, but never design recovery as an afterthought.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org