What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Post-quantum cryptography (PQC) is cryptography designed to resist attacks from both classical and quantum computers. Its algorithms run on existing computing platforms; organizations do not need quantum computers to use them. The reason to plan a migration now is practical: updating cryptography across systems and suppliers takes time, while encrypted data collected today could be targeted for decryption in the future.

What post-quantum cryptography does

PQC uses mathematical algorithms intended to withstand attacks from powerful quantum computers as well as conventional computers. It addresses a future risk to some widely used cryptographic systems; it does not mean that all encryption is already broken or that quantum computing defeats every cryptographic method equally.

PQC is different from quantum key distribution (QKD). PQC relies on mathematical algorithms implemented in software and existing computing platforms. QKD uses quantum-mechanical systems and specialized technology to distribute keys. The terms are not interchangeable. The U.S. National Security Agency (NSA) says it does not recommend QKD or quantum cryptography for National Security Systems unless cited limitations are overcome; that position is specific to those systems, not a universal judgment about every possible use.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Why begin migrating before a quantum computer can break current encryption?

Some data may need to stay secret for years

In a “harvest now, decrypt later” attack, an adversary collects and stores encrypted information that cannot be read today, hoping to decrypt it if future quantum capabilities make that possible. This makes the issue relevant now for information whose confidentiality must last a long time. It does not establish that a particular adversary is collecting any particular organization’s data.

#1 Best Overall
Sale
Thetis Nano-A FIDO2 Security Key Hardware Passkey Device with USB Type A, TOTP/HOTP, FIDO2.0 Two Factor Authentication 2FA MFA, Works with Windows/mac/iOS/Android/Linux/Gmail/Facebook/GitHub/Coinbase
  • Ultra-Compact FIDO2 Security Key - Plug-and-stay or carry on a keychain. This USB-A hardware security key offers portable, always-on protection for desktop and mobile use. (Item Size: 0.75 X 0.74 IN x 0.25 IN)
  • USB-A Hardware Key for All Devices - Works with USB-A ports on PC, Mac, Android, and other laptop/notebook device. Enables secure, cross-platform login with FIDO2.0 passkey support.
  • FIDO Certified Security Key - Meets FIDO and FIDO2 standards. Works with Google, Microsoft, GitHub, Dropbox, and more. Please check service compatibility before purchase.
  • Passwordless Login with Passkey - Supports passkey login via WebAuthn and CTAP2. Enjoy password-free sign-ins where supported. Not all websites or services currently support passkeys.
  • Advanced Multi-Factor Authentication - Offers 200 FIDO2 passkey slots and 50 OATH-TOTP slots. Strong, flexible 2FA/MFA support across various apps and authentication platforms.

Cryptographic change takes time

NIST says it has historically taken 10 to 20 years from standardization of a new algorithm to its full integration into information systems. That is a historical estimate, not a prediction that every PQC deployment will take that long. A migration can involve applications, products, services, protocols, and supplier-controlled dependencies—not just a single setting an organization can switch.

The timing of the quantum threat is uncertain

NIST says estimates vary widely and it is not possible to predict exactly when—or even whether—quantum computers will break present-day encryption. A credible migration plan therefore does not need a speculative “Q-Day” countdown. It can be justified by the long lead time, the sensitivity and secrecy lifetime of data, and the effort required to find and update cryptographic dependencies.

Which PQC standards are ready to implement?

NIST released its first three final PQC standards in August 2024. They cover different cryptographic functions, so they are not interchangeable versions of one general-purpose encryption algorithm.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Standard Algorithm Function
FIPS 203 ML-KEM (Module-Lattice-Based Key-Encapsulation Mechanism) Key establishment
FIPS 204 ML-DSA (Module-Lattice-Based Digital Signature Algorithm) Digital signatures
FIPS 205 SLH-DSA (Stateless Hash-Based Digital Signature Algorithm) Stateless hash-based digital signatures

NIST says organizations can implement these standards now and encourages them to begin applying them. NIST is also evaluating additional algorithms that could become backup or alternative standards. Which standard is relevant depends on the cryptographic function a system needs; selecting and deploying algorithms should be part of an organization’s technical migration planning.

What migration timelines apply—and to whom?

NIST’s transition timeline, described in NIST IR 8547, calls for quantum-vulnerable algorithms to be deprecated and ultimately removed from NIST standards by 2035, with high-risk systems transitioning earlier. This is a NIST standards transition timeline, not a universal legal deadline for every organization.

A June 2026 U.S. executive order sets directions for federal high-value assets and high-impact systems, excluding National Security Systems: transition to PQC for key establishment by December 31, 2030, and for digital signatures by December 31, 2031. Those dates have a defined federal scope. They should not be treated as deadlines for every company, country, or National Security System.

Rank #4
Thetis Nano-C FIDO2 Security Key Hardware Passkey Device with USB Type C, TOTP/HOTP, FIDO2.0 Two Factor Authentication 2FA MFA, Works with Windows/mac/iOS/Android/Linux/Gmail/Facebook/GitHub/Coinbase
  • Ultra-Compact FIDO2 Security Key – Plug-and-stay or carry on a keychain. This USB-C hardware security key offers portable, always-on protection for desktop and mobile use.(Item Size: 0.73 X 0.60 X 0.30 inches)
  • USB-C Hardware Key for All Devices – Works with USB-C ports on PC, Mac, Android, and USB-C iPhones. Enables secure, cross-platform login with FIDO2.0 passkey support.
  • FIDO Certified Security Key – Meets FIDO and FIDO2 standards. Works with Google, Microsoft, GitHub, Dropbox, and more. Please check service compatibility before purchase.
  • Passwordless Login with Passkey – Supports passkey login via WebAuthn and CTAP2. Enjoy password-free sign-ins where supported. Not all websites or services currently support passkeys.
  • Advanced Multi-Factor Authentication – Offers 200 FIDO2 passkey slots and 50 OATH-TOTP slots. Strong, flexible 2FA/MFA support across various apps and authentication platforms.

Separately, a joint CISA, NIST, and NSA release dated August 21, 2023 recommended that organizations prepare by building roadmaps, engaging technology vendors, taking inventory, and prioritizing sensitive and critical assets. The recommendation predates the August 2024 final standards; it is preparation guidance, not a substitute for the standards themselves.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How an organization can start

Start with discovery and risk prioritization rather than assuming every system should change at once or in the same way. The joint CISA, NIST, and NSA guidance supports establishing a roadmap, engaging vendors, inventorying cryptographic systems and assets, and planning prioritized migrations.

Best Value
Yubico - Security Key C NFC - Basic Compatibility - Multi-Factor authentication (MFA) Security Key and passkey, Connect via USB-C or NFC, FIDO Certified
  • POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
  • WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
  • FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
  • TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
  • BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
  1. Inventory cryptographic use. Identify applications, systems, protocols, and assets that rely on cryptography, including where public-key cryptography is used. NIST advises technology managers to inventory applications that use encryption and alert technology teams and vendors.
  2. Prioritize by exposure and impact. Determine which data must remain confidential for the longest period, which systems are most critical, and which assets are sensitive. The joint guidance specifically recommends prioritizing sensitive and critical assets.
  3. Ask suppliers about their plans. Find out which products, services, and protocols contain cryptographic dependencies, how vendors plan to update them, and what the organization must do to adopt those updates. Some dependencies may be controlled outside the organization.
  4. Build a migration roadmap. Use the inventory and priorities to plan replacements or updates, coordinate affected teams and suppliers, and sequence work. NIST notes that cybersecurity products, services, and protocols will need updates as organizations move to PQC.

This is a starting framework, not a complete technical implementation guide. The right migration sequence depends on an organization’s systems, data, and supplier dependencies.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What PQC migration does not mean

  • It does not require quantum hardware. PQC algorithms are designed to run on existing computing platforms.
  • It does not mean all current encryption has failed. The concern is that future quantum capability could threaten some widely used cryptographic systems, which is why organizations need to identify vulnerable uses and plan updates.
  • It does not make QKD another name for PQC. PQC is based on mathematical algorithms; QKD relies on quantum-mechanical systems and specialized technology.
  • It does not establish one universal deadline. NIST’s standards timeline and the federal executive order have specific scopes; neither should be generalized into a global requirement for every organization.

The practical takeaway

Organizations do not need to predict when a cryptographically relevant quantum computer will arrive to justify preparation. They can begin by discovering where cryptography is used, identifying data and systems that deserve priority, and coordinating with suppliers on a standards-based migration roadmap. The goal is an orderly transition before vulnerable dependencies become an urgent operational problem.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.