Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
FIDO2 is the standard behind security keys and passkeys. WebAuthn is the browser API that lets a website ask an authenticator to sign a challenge instead of accepting a password.

What Are FIDO2 and WebAuthn?
FIDO2 is two specifications working together. WebAuthn, a W3C recommendation since March 2019, is the browser API through which a website asks for a cryptographic assertion. CTAP2, from the FIDO Alliance, is the protocol between the browser and the authenticator—a USB security key, a phone over Bluetooth, or a secure element built into the laptop. Together they let a site authenticate a user without ever receiving a shared secret.
At registration the authenticator generates a key pair specific to that website. The private key stays in the authenticator, protected by a PIN or biometric. The public key goes to the server along with a credential identifier. The server stores the public key, which is not a secret and is worthless to anyone who steals the database.
At sign-in the server sends a random challenge. The browser passes it to the authenticator together with the origin of the page making the request. The authenticator checks whether it holds a key for that exact origin, asks the user to confirm presence—a touch, a PIN, a fingerprint—and returns a signature over the challenge and the origin. The server verifies it with the stored public key.
The origin check is the whole trick, and it is worth stating precisely. A key registered for bank.example.co.uk will not produce a signature for bank-example-login.com, however convincing the page looks. The authenticator makes that decision in hardware, using a value supplied by the browser rather than by the page, so no amount of user error reaches it.
That defeats not just lookalike domains but adversary-in-the-middle proxies such as Evilginx, which otherwise relay a genuine login and capture the resulting session. The proxy’s origin is its own, so the signature never matches. This is the structural difference between phishing-resistant authentication and the merely additional factors covered in one-time passwords and push approvals, both of which a relay can forward.
Google published the clearest evidence of this: after requiring security keys for more than 85,000 employees from early 2017, it reported no successful phishing of a work account. The NCSC’s guidance on multi-factor authentication for online services names FIDO2 as its strongest recommended option.
The hardest problem is not authentication, it is recovery. If a key is the only credential and the user drops it in the Thames, what happens? The answer must be designed before rollout, because the default answer is a help desk call, and a help desk that can reset authentication on the basis of a phone conversation has reintroduced the weakness you just removed. Register at least two authenticators per user, require an in-person or video-verified process for recovery, and never fall back to SMS.
Other practical points. Not every application supports WebAuthn—legacy and on-premises systems often cannot, so plan a mixed estate rather than a flag day. Shared workstations in clinical, retail, and manufacturing settings need a model where the authenticator belongs to the person rather than the desk. Browser and platform support is now broadly complete, but device repair and replacement flows need a documented re-enrolment path. And in Microsoft estates, Windows Hello for Business gives you a FIDO2 authenticator already built into every compliant laptop, which is usually cheaper than buying keys for everyone.
Finally, remember what remains. FIDO2 protects authentication. It does nothing about a session token stolen after sign-in, which is why it belongs alongside conditional access, short token lifetimes, and token binding rather than instead of them.
At Privia Security, we assess passwordless rollouts and their recovery paths in our cyber risk analysis services.
WebAuthn is the web API that a website and browser use to request and verify a cryptographic assertion. CTAP2 is the protocol between the browser and the authenticator device. FIDO2 is the umbrella name for both together. In everyday use people say WebAuthn when they mean the browser side and FIDO2 when they mean the whole scheme.
Whatever you designed in advance, which is why the recovery path matters more than the rollout. Best practice is registering at least two authenticators per user so the second covers loss of the first, combined with a verified recovery process involving in-person or video identity checks. Falling back to SMS or a help desk phone call undoes the phishing resistance you deployed.
The authentication itself cannot, because the authenticator will only sign for the exact origin the credential was registered to, and that origin comes from the browser rather than the page. What can still be attacked is everything around it: the account recovery process, a weaker fallback factor left enabled, and session tokens stolen after a successful sign-in.
Platform authenticators built into laptops and phones, such as Windows Hello for Business or a phone’s secure element, are genuine FIDO2 authenticators and suit most staff. External keys are worth the cost for administrators, for shared or unmanaged devices, and as the second registered authenticator so that losing a laptop does not lock someone out.
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.