Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A passkey is a FIDO credential that replaces a password entirely: a private key held by your device or password manager, unlocked by a fingerprint, face, or PIN.

What Is a Passkey?
A passkey is what a password would be if it had been designed after phishing existed. Instead of a secret you know and can be persuaded to type somewhere, it is a private key your device holds, which signs a challenge only for the website it was created for. You prove you are present with a fingerprint, a face scan, or a device PIN, and nothing reusable ever crosses the network.
Underneath, a passkey is a FIDO2 and WebAuthn credential. The word “passkey” was adopted in 2022 by Apple, Google, and Microsoft to describe the user-facing experience, chiefly because “discoverable WebAuthn credential” was never going to reach the public.
At registration the authenticator creates a key pair scoped to the site’s origin. The public key goes to the server; the private key never leaves the authenticator. At sign-in the server sends a random challenge, the browser supplies the origin, the authenticator checks it holds a key for that exact origin, asks you to confirm, and returns a signature.
Two consequences matter more than any other. The server stores only a public key, so a breach of its database yields nothing an attacker can use—there is no hash to crack and no credential to stuff elsewhere. And because the origin check happens inside the authenticator using a value the page cannot forge, a convincing replica at a lookalike domain receives nothing at all, including from a proxy phishing kit that defeats one-time codes.
This is the distinction that matters for an enterprise decision, and the two are often discussed as if they were the same thing.
| Synced passkey | Device-bound passkey | |
|---|---|---|
| Where the key lives | Platform account or password manager, encrypted | One device or security key only |
| If the device is lost | Restore on a new device | Credential is gone |
| Attestation of hardware | Usually unavailable | Available |
| Suits | Consumers and general staff | Administrators, regulated environments |
Synced passkeys solve the recovery problem that stops most passwordless projects, and they bring a new consideration: the security of the credential now depends on the platform account or password manager holding it. If someone’s iCloud or Google account is compromised, so are the passkeys synced to it. That is an argument for protecting those accounts well, not against synced passkeys—but it is a real change in the trust model, and regulated environments often require device-bound credentials with attestation for exactly that reason.
Signing in on a computer using a passkey held on a phone works through a QR code and a Bluetooth proximity check. The Bluetooth element is not decoration: it proves the two devices are physically near each other, which prevents an attacker displaying a QR code on a phishing page and persuading a remote victim to scan it. This is why cross-device authentication resists relay in a way that scanning a code in other contexts does not.
Adoption passed the point of novelty some time ago: major UK banks, government services, and the large consumer platforms all support passkeys, and the NCSC lists phishing-resistant authentication as its strongest recommendation for protecting accounts. For organisations still planning, the realistic sequence is passkeys for staff sign-in, hardware keys for privileged roles, and one-time passwords retained only where nothing better is supported.
At Privia Security, we assess passwordless deployments and their recovery paths through our cyber risk analysis services.
With a synced passkey, you sign in to your platform account or password manager on a replacement device and the passkeys are restored, which is the main practical advantage of syncing. With a device-bound passkey the credential is gone and you must use another registered authenticator or go through account recovery, which is why registering two authenticators is advised.
Synced passkeys are protected by the platform account that stores them, so that account becomes critical. Protect it with its own strong authentication and recovery controls. Organisations that cannot accept this dependency should require device-bound passkeys or hardware security keys with attestation, particularly for administrative and regulated access.
The authentication itself cannot, because the authenticator only signs for the exact origin the credential was registered to and the origin comes from the browser rather than the page. What remains attackable is everything around it: account recovery processes, weaker fallback methods left enabled, and session tokens stolen after a successful sign-in.
Not naturally, since a passkey is tied to a personal authenticator rather than a workstation. The usual pattern is cross-device sign-in, where the user authenticates on the shared machine using a passkey held on their own phone via a QR code and Bluetooth proximity check. Hardware security keys are the other option where phones are not permitted.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.