Touching a FIDO2 security key and verifying its user are different operations. A simple touch can demonstrate user presence; a PIN or biometric check can provide user verification. The distinction matters when deciding whether a sign-in demonstrates only possession or also requires another authentication factor. W3C explicitly distinguishes a presence test from verification of the user. WebAuthn terminology
For someone choosing a security key, the practical question is therefore more specific than “Does it have a button?” Ask what the authenticator can verify and what the service requires for the particular sign-in. This standards-informed guide was checked on October 2, 2026.
Presence and verification answer different questions
User presence, abbreviated UP, records an interaction with the authenticator. User verification, or UV, can involve a PIN or biometric. WebAuthn represents them with distinct flags. A service that requires verification must check the UV result; requesting “preferred” verification does not impose the same requirement as “required.” The flags also do not establish a person's legal identity. W3C WebAuthn specification
Our editorial advice is to use those distinctions in employee instructions. “Touch your key to continue” and “Verify yourself using your key's PIN” describe different actions. Combining both into “approve the login” makes troubleshooting harder because users cannot explain which step failed. Precise instructions are especially helpful when a team supports several key models and operating systems.
A PIN can unlock a credential without becoming a website password
FIDO Alliance's Passkey Central describes passkey authentication as a public-key process. The service receives a public key during enrollment and checks a signed challenge during authentication. The private key remains with the credential provider or security key. Local PIN or biometric verification is not sent to the website as a reusable account password. How passkeys work
That difference suggests a useful training exercise: ask users to identify whether they are seeing an account-password prompt or the expected local verification prompt. Our recommendation is to teach the normal flow on a trusted device before a deadline or travel day. Do not train people to enter their key PIN into an arbitrary web form that claims it is necessary for support.
A short PIN should not be evaluated as if it were a standalone internet password. NIST treats a locally used activation secret separately and specifies retry limiting and other requirements. Its multi-factor cryptographic model combines control of a key with a second factor that activates it. NIST also requires the verifier to establish that the activation factor was used before treating that output as multi-factor authentication. NIST SP 800-63B-4, Authenticators
This does not make every PIN-protected product automatically compliant with a particular assurance level. Procurement decisions need evidence about the full implementation and the applicable requirements. A label on a shopping page cannot settle that assessment.
A fingerprint prompt is local verification, not biometric upload
In the FIDO passkey model, biometric measurements stay local rather than being provided to each website. The service checks cryptographic evidence. Passkeys may live in a credential manager or on an external security key; a fingerprint experience does not by itself tell the user which of those holds the credential. FIDO Alliance's technical overview
Our practical recommendation is to evaluate accessibility and everyday working conditions alongside convenience. A team should consider whether its chosen verification method is workable with its equipment, environment, and users. Record the supported alternative for people who cannot reliably use the preferred interaction. That is a deployment design decision, not evidence that one biometric method is universally superior.
Is touching a security key multi-factor authentication?
Count the factors in the complete authentication flow. NIST describes a cryptographic authenticator without a second activation factor as a possession factor. Adding a required activation factor changes that model. A password followed by a touch-only key can also combine knowledge and possession across the flow; touching the key alone does not supply a knowledge or biometric factor. NIST authenticator definitions
For administrators, our recommendation is to document the intended assurance outcome before choosing a prompt. A useful acceptance statement would specify the required factors, the credential types allowed, and what evidence the service must verify. Avoid counting screens or clicks as factors. Two prompts can still represent one factor, while one coordinated experience can involve two.
Choose and test the experience your service supports
For a purchasing or rollout decision, use a small acceptance checklist:
- Confirm that the service explicitly supports external FIDO2 security keys in the intended workflow.
- Check the selected model's verification capabilities and supported connections.
- Record the expected presence and verification prompts on the actual operating system and browser.
- Have the service owner confirm the enforced authentication policy, rather than inferring it from the interface alone.
These are editorial recommendations for evaluation, not results of hands-on product testing. A general passkey-support statement is not enough to guarantee external-key compatibility. Teams can review Thetis's FIDO2 security key collection while comparing those requirements.
The most useful purchasing question is the one a service owner can answer with evidence: what does this exact sign-in require, and how is that requirement enforced? Clear answers make both everyday use and deployment decisions easier.
