Passkeys and FIDO2 security keys are not automatically quantum-safe. Phishing resistance and resistance to a future cryptographically relevant quantum computer address different threats. An authenticator’s algorithms and the wider sign-in system determine its post-quantum properties; the FIDO2 label alone is not sufficient evidence. The FIDO Alliance’s quantum white paper identifies the need to migrate affected public-key algorithms. FIDO Alliance white paper
For users and IT teams, this creates two parallel priorities: improve authentication against current attacks, and prepare systems to adopt new cryptography as supported implementations become available.
Phishing resistance solves a different problem
A passkey is a public-key credential used for authentication. A FIDO2 security key is a physical authenticator that can hold and use such a credential. In WebAuthn, authentication is bound to the service’s verified name, helping prevent a lookalike site from obtaining an authentication response usable as though it came from the legitimate service.
NIST recognizes this verifier-name binding as a method of phishing resistance. That property concerns authenticating to the right service. It does not establish that the signature algorithm will withstand every future form of computation. NIST authentication guidance
Our recommendation is to keep those claims separate in procurement documents. Ask whether a product supports the intended phishing-resistant workflow, then ask independently what evidence supports any post-quantum claim.
What would quantum computing change?
A sufficiently capable quantum computer could threaten widely used public-key mathematics. The FIDO Alliance identifies asymmetric algorithms such as RSA and ECDSA as requiring algorithm changes, and describes coordination with other standards bodies as part of migration. Its 2024 paper is useful background, not proof that a particular product has since completed that transition. FIDO’s migration discussion
NIST says the arrival date of a cryptographically relevant quantum computer is uncertain. It nevertheless recommends preparation because changing cryptographic systems takes time. This is a planning problem with uncertain timing, rather than a sound basis for declaring all existing authentication broken today. NIST’s post-quantum explainer
That distinction should shape the tone of security communications. A useful roadmap explains what can be tested and replaced. A countdown without evidence does not help a reader make a better decision.
Digital signatures matter for authentication
Post-quantum cryptography includes different tools for different jobs. For authentication, digital-signature standards are particularly relevant. NIST’s FIPS 204 specifies ML-DSA, a module-lattice-based signature algorithm. FIPS 205 specifies SLH-DSA, a stateless hash-based signature algorithm. Both were finalized in August 2024. FIPS 204, FIPS 205
A published standard is not the same thing as an available end-to-end passkey implementation. A deployment also needs compatible software, authenticators, and services, plus a way to enroll and manage the new credentials. This is our practical deployment inference: verify the working combination instead of treating an algorithm name on a roadmap as completed interoperability.
The same reasoning applies to a device’s enclosure or secure hardware. Physical protection and algorithm selection answer different questions. A durable or tamper-resistant product should not be described as post-quantum merely because it protects a private key well against other attacks.
Build a migration plan that can be executed
Our recommended first step is a compact authentication inventory. Record the services that matter most, who owns them, which authenticators are approved, and where documented algorithm information can be found. Mark unknowns explicitly so they become follow-up questions rather than hidden assumptions.
Then ask suppliers and identity-platform teams:
- Which algorithms does the current implementation use for authentication and attestation?
- Is post-quantum support shipping, experimental, or only planned?
- What independent documentation supports the claim?
- Would migration require replacement hardware, software changes, or new credential registration?
- How would old credentials be retired without locking users out?
These are editorial procurement questions, not a certification checklist. Their purpose is to turn a broad promise into a sequence of observable steps.
For example, a business buying authenticators for several years of use could document a replacement budget and an enrollment process alongside its initial rollout. That approach does not predict an exact quantum deadline. It makes future change more manageable.
Should you wait before adopting security keys?
Our recommendation is to address a demonstrated authentication weakness now while maintaining a migration plan. An organization still relying on phishable sign-in methods has a current problem to solve. Future algorithm changes do not make that problem disappear.
For teams considering hardware authenticators, Thetis’s FIDO2 security key collection provides options to evaluate against current requirements. This article makes no claim that any Thetis model implements post-quantum signatures. Product-specific capabilities should be confirmed through current documentation.
The useful long-term goal is authentication that can evolve: clear ownership, documented dependencies, tested recovery, and a credible route to change credentials or devices. Passkeys can improve how users sign in today; quantum readiness requires additional evidence and planning for tomorrow.
Sources checked September 30, 2026. This is a research-based explainer with editorial recommendations, not a product certification or a forecast of quantum-computer availability.
