03: Post-Quantum Cryptography: The Security Upgrade Happening Behind the Scenes

Post-Quantum Cryptography: The Security Upgrade Happening Behind the Scenes

Post-quantum cryptography, or PQC, is not a replacement for all encryption. It is an upgrade to the public-key systems that help digital services establish secrets and prove identity. Much of the transition will occur quietly through browsers, operating systems, cloud services, networks, and institutional software.

The question readers are really asking

What is post-quantum cryptography, and will I need to replace the encryption I already use?

For most people, the answer is no. PQC is not a new kind of “quantum encryption,” and it does not mean that every encrypted file, password manager, or encrypted disk must be replaced.

The central issue is more specific. Many digital systems rely on public-key cryptography—especially RSA and elliptic-curve cryptography—to do two jobs:

1. establish a shared secret between parties who have not met before; and
2. prove that a message, website, software update, or account credential is authentic.

Large-scale quantum computers could eventually undermine those classical public-key systems. PQC provides new public-key algorithms intended to resist both conventional and quantum attacks.

The transition is therefore best understood as a security upgrade happening beneath the surface of everyday technology.

The short answer

PQC replaces or supplements vulnerable public-key components. It does not replace the symmetric encryption that usually protects the actual contents of data.

A secure web connection commonly works in two stages:

• public-key cryptography helps the browser and website establish a temporary shared secret; then
• symmetric encryption, such as AES or ChaCha20, protects the actual web traffic.

PQC mainly changes the first stage. It gives the parties a new way to establish that shared secret and a new way to create digital signatures that remain credible in a post-quantum future.

Why NIST standards matter

Cryptographic research produces many possible algorithms. A workable transition requires a smaller set that has been publicly evaluated, specified, tested, and adopted across products and protocols.

In the United States, the National Institute of Standards and Technology, or NIST, has led an international process to evaluate and standardize post-quantum algorithms. In 2024, it issued its first three post-quantum Federal Information Processing Standards, commonly called FIPS:

• FIPS 203: ML-KEM, for establishing shared secrets;
• FIPS 204: ML-DSA, for digital signatures; and
• FIPS 205: SLH-DSA, a second, hash-based digital-signature option.

NIST is also developing FN-DSA, based on FALCON, as an additional post-quantum digital-signature standard. Its smaller signatures and fast verification can be useful where bandwidth or signature size matters, although its implementation is more complex. Unlike the three FIPS listed above, FN-DSA is still under development.

These names matter because they give software makers, cloud providers, government agencies, hardware vendors, and standards bodies common technical building blocks. End users need not memorize them; they need products and services that adopt them responsibly.

A bridge under repair

A useful analogy is a bridge that cannot simply close for reconstruction. Traffic must continue crossing while engineers strengthen the structure.

Digital systems face the same constraint. No organization can replace every key, certificate, device, application, and network protocol on a single day. Existing services must continue to work while new cryptography is introduced and tested.

The goal is to strengthen the bridge before a future quantum computer makes the older supports unsafe.

The two public-key jobs that PQC must upgrade

1. Establishing a shared secret

When two parties communicate securely, they need a secret key that outsiders do not know. Public-key cryptography makes it possible to establish that secret over an open network.

The NIST standard ML-KEM—short for Module-Lattice-Based Key-Encapsulation Mechanism—is designed for this purpose. Its role matters more than its name: it helps two systems create or protect a shared secret that can then be used with ordinary fast symmetric encryption.

In a web connection, ML-KEM may help a browser and website agree on the temporary key that protects the session. The actual traffic can still use AES or ChaCha20.

2. Creating digital signatures

Digital signatures answer a different question: How do I know this really came from the claimed sender and has not been altered?

Signatures are used for software updates, websites and certificates, signed documents, code repositories, firmware, and identity credentials.

The NIST standard ML-DSA—short for Module-Lattice-Based Digital Signature Algorithm—is designed for this role. It lets a sender create a signature that others can verify, using a method intended to resist a powerful quantum computer.

NIST has also standardized SLH-DSA, a hash-based signature scheme that provides a second design option. Most readers need only remember the underlying point: PQC protects trust in identities, updates, and documents as well as secrecy.

Why systems may use both old and new methods

During the transition, many systems will use hybrid cryptography: a conventional public-key method and a post-quantum method together.

For key establishment, a hybrid system may combine a classical elliptic-curve exchange with ML-KEM. The final session key is derived from both contributions. The practical aim is simple: the connection should remain protected if at least one of the components remains secure.

This is a conservative engineering choice. It reduces quantum risk while allowing new algorithms to be tested and deployed without requiring every device and service to change at once.

Why the transition will take years

Standardization is essential, but it is only the beginning. Real-world cryptography is embedded in software, hardware, standards, vendor products, and institutional procedures.

First, systems must identify where public-key cryptography is used. It appears in websites, email, networks, cloud services, software updates, certificates, devices, and old archives.

Second, the new algorithms must be tested in real environments. PQC keys, signatures, certificates, and protocol messages can be larger than their classical counterparts. That can affect storage, bandwidth, memory, performance, and compatibility.

Third, old and new systems must coexist. Not every browser, router, phone, server, or embedded device can upgrade at the same time.

Finally, organizations need crypto agility. They need to rotate keys, replace algorithms, update certificates, and re-encrypt valuable long-lived data without rebuilding everything.

What readers should do now

1. Keep devices and applications updated. Most PQC improvements will arrive through supported software and services.

2. Continue using strong symmetric encryption. Full-disk encryption, password managers, and encrypted backups remain important.

3. Protect accounts and recovery information. Strong passwords, passkeys, multi-factor authentication, recovery keys, and secure backups address more immediate risks.

4. Pay attention to long-lived sensitive data. Health, legal, financial, research, and institutional records may need a longer-term migration plan.

5. Ask vendors clear questions. Do they support hybrid cryptography? Can they update keys, certificates, and algorithms without replacing everything? Do they have a documented PQC roadmap?

What readers do not need to do

Most people do not need to select ML-KEM settings, manually configure browser cipher suites, replace modern devices, or buy products merely because their marketing mentions quantum computing.

PQC is largely an upgrade for the organizations that operate the digital infrastructure beneath everyday services. The best individual preparation remains basic: use supported software, keep it current, protect passwords and recovery information, and distinguish long-lived sensitive records from routine short-lived activity.

Takeaway: NIST standards give the post-quantum transition common building blocks, but adoption will be gradual. PQC is a practical upgrade to the public-key foundations that establish secrets and verify trust across modern digital systems.

Key terms

Post-quantum cryptography (PQC)
Public-key cryptography designed to resist attacks by both conventional and quantum computers.

NIST
The U.S. National Institute of Standards and Technology, which has led a major international process to evaluate and standardize post-quantum algorithms.

Key establishment
The process by which two parties create or agree on a shared secret key for secure communication.

Digital signature
A cryptographic proof that helps verify who signed information and whether it has been changed.

ML-KEM
A NIST post-quantum standard for establishing or protecting a shared secret.

ML-DSA
A NIST post-quantum standard for digital signatures.

FN-DSA (FALCON)
A NIST post-quantum digital-signature standard under development. It is based on FALCON and may be useful where smaller signatures are especially valuable.

Hybrid cryptography
A transition approach that combines conventional and post-quantum cryptographic methods.

Crypto agility
The ability to update cryptographic algorithms, keys, certificates, and protocols without rebuilding an entire system.

Watch Video Summary