Why Post-Quantum Cryptography?

This page provides a deeper look at the urgency of migrating to post-quantum cryptography, the strategies for doing so, and the global standards landscape. For a broader introduction to PQC concepts, see What is Post-Quantum Cryptography?.

The “Harvest Now, Decrypt Later” Threat

The most immediate quantum threat does not require a quantum computer to exist today. Adversaries – including state-level actors – can record encrypted network traffic now and store it indefinitely. Once a cryptographically relevant quantum computer (CRQC) becomes available, they can decrypt everything they collected.

This means that data encrypted today with RSA or ECDH is only as safe as the time it takes for a CRQC to be built. For data that must remain confidential for 10, 20, or 50 years – classified government communications, medical records, trade secrets, financial data – the threat is already real.

The timeline for action is not “when quantum computers arrive” but rather “now, minus the confidentiality lifetime of your data.”

Timeline Considerations

There is no consensus on exactly when a CRQC will exist. Estimates from researchers and government agencies range broadly:

Regardless of the exact date, cryptographic migrations are historically slow processes. The transition from SHA-1 to SHA-2 took over a decade. Moving from RSA to elliptic curve cryptography took even longer. Starting the PQC migration early is a risk management decision, not a prediction about quantum computing timelines.

Hybrid Approaches

During the transition period, many organizations are adopting hybrid schemes that combine a classical algorithm with a post-quantum algorithm. The security guarantee is that the system remains secure as long as at least one of the two algorithms is unbroken.

Common hybrid configurations include:

Hybrid approaches are recommended by NIST, ETSI, and the BSI (German Federal Office for Information Security) as a transition strategy. They protect against the possibility that a newly standardized PQC algorithm has an unforeseen weakness, while also protecting against quantum threats to the classical algorithm.

MetaMUI’s Approach

MetaMUI Crypto Primitives supports both classical and post-quantum algorithms to enable hybrid deployments:

Applications can use MetaMUI to deploy hybrid schemes where a post-quantum signature or key exchange is paired with a classical one, ensuring security regardless of which threat model proves correct.

Global Standards Landscape

Post-quantum standardization is not a single effort but a parallel set of processes across multiple jurisdictions:

NIST (United States)

NIST’s Post-Quantum Cryptography Standardization is the most widely referenced process globally. Published standards:

Additional algorithms (HQC, BIKE, Classic McEliece) are under evaluation for future standardization.

KPQC (South Korea)

The Korean Post-Quantum Cryptography competition has selected algorithms tailored to Korean government and industry requirements:

Korean organizations subject to domestic regulations may need to implement KPQC algorithms alongside or instead of NIST algorithms.

ETSI (Europe)

The European Telecommunications Standards Institute (ETSI) Quantum-Safe Cryptography working group publishes guidance on quantum-safe migration. ETSI recommends hybrid approaches during the transition period and has published technical reports on integration with existing protocols (TLS, IKEv2, S/MIME).

Other Efforts

How to Start Migrating

  1. Inventory your cryptographic dependencies. Identify where RSA, ECDSA, ECDH, and other quantum-vulnerable algorithms are used in your systems.
  2. Assess data sensitivity and lifetime. Data that must remain confidential for 10+ years is the highest priority for migration.
  3. Choose algorithms. Use the Algorithm Selector to pick the right algorithms for your use cases.
  4. Deploy hybrid schemes first. Combine classical and PQC algorithms during the transition to manage risk.
  5. Integrate MetaMUI Crypto Primitives. See the Getting Started guide for platform-specific installation and usage instructions.
  6. Test interoperability. If your system spans multiple platforms, verify cross-language compatibility using MetaMUI’s shared test vectors.