Complete Guide

Post-Quantum Cryptography Guide: NIST Standards and Migration

A comprehensive guide to understanding and implementing quantum-resistant cryptography in your organisation. Updated for 2026.

Last updated: August 2026|25 min read

Post-Quantum Cryptography at a Glance

Post-quantum cryptography protects digital systems against attacks from future quantum computers while continuing to run on conventional hardware. It is needed because a sufficiently capable quantum computer could break the public-key algorithms used today for key exchange, identity and digital signatures.

QuestionPractical answer
What needs to change?Vulnerable public-key cryptography, including RSA and elliptic-curve key exchange and signatures.
What are the main standards?NIST FIPS 203 for ML-KEM, FIPS 204 for ML-DSA and FIPS 205 for SLH-DSA.
What is the first action?Build a cryptographic inventory and prioritise systems by exposure, data lifetime and migration difficulty.
Should teams replace everything now?No. Test supported hybrid deployments first, with compatibility checks and a documented rollback path.

Post-Quantum Cryptography Step 2: Turn Awareness Into Evidence

Many teams search for a second post-quantum cryptography guide after they understand the basic threat. The useful next step is not to pick an algorithm in isolation. It is to create evidence that shows where RSA, ECDH, ECDSA and other vulnerable public-key dependencies still exist.

Treat step 2 as a short evidence sprint: check the public attack surface, build a cryptographic inventory, then select one low-risk pilot where hybrid post-quantum protection can be tested without breaking users.

Check exposed services

Scan public websites, APIs, VPN portals and customer-facing hosts for TLS posture, downgrade risk and visible PQC support.

Run the free quantum security scanner

Build the inventory

List certificates, key exchange, signing keys, libraries, hardware, suppliers, owners and data-lifetime requirements.

Use the cryptographic inventory guide

Choose the first pilot

Prioritise reversible hybrid ML-KEM tests for TLS, APIs or VPNs before moving to signing and long-term verification.

Read the implementation guide

1. What is Post-Quantum Cryptography?

Post-quantum cryptography (PQC), also known as quantum-resistant or quantum-safe cryptography, refers to cryptographic algorithms that are designed to be secure against attacks from both classical computers and quantum computers.

Unlike current encryption standards like RSA and ECC (Elliptic Curve Cryptography), which rely on mathematical problems that quantum computers can solve efficiently, PQC algorithms are based on problems that remain computationally hard even for quantum computers.

Key Takeaway

PQC is not about quantum computers doing encryption. It's about classical cryptography that quantum computers cannot break.

2. Why It Matters Now

You might think that if quantum computers capable of breaking encryption are still years away, there's no urgency. This assumption is dangerously wrong for three critical reasons:

  • 1.
    Data has a shelf life.

    Medical records, financial data, government secrets, and trade secrets often need to remain confidential for 10, 20, or 30+ years. Data encrypted today must withstand threats that will exist throughout its entire lifetime.

  • 2.
    Migration takes time.

    Transitioning enterprise cryptographic infrastructure is not a quick process. Large organisations typically need 5-10 years to fully migrate their systems. Starting now means being ready when quantum computers arrive.

  • 3.
    Attackers are already collecting.

    Nation-states and sophisticated adversaries are already harvesting encrypted data, storing it until quantum computers can decrypt it. This is happening now.

3. The Quantum Computing Threat

In 1994, mathematician Peter Shor developed an algorithm that demonstrated quantum computers could efficiently solve the mathematical problems underlying RSA and ECC encryption. This theoretical breakthrough has driven decades of quantum computing research.

What Quantum Computers Will Break

AlgorithmTypeQuantum Impact
RSA-2048Public KeyBroken
ECDSA / ECDHPublic KeyBroken
DSASignaturesBroken
AES-256SymmetricWeakened (128-bit effective)
SHA-256HashStill secure

Timeline Estimates

Experts estimate that cryptographically relevant quantum computers (CRQCs) capable of breaking RSA-2048 could emerge between 2030 and 2040. However, these timelines are uncertain, and breakthroughs could accelerate progress significantly.

4. Harvest Now, Decrypt Later

"Harvest now, decrypt later" (HNDL) is a threat model where adversaries intercept and store encrypted data today, with the intention of decrypting it once quantum computers become available.

This Is Happening Now

Intelligence agencies and sophisticated threat actors are believed to be actively collecting encrypted communications and stored data. Any sensitive data transmitted or stored with classical encryption is potentially at risk.

High-Risk Data Categories

  • Government and military communications
  • Healthcare records and genetic data
  • Financial transactions and records
  • Intellectual property and trade secrets
  • Legal documents and contracts
  • Infrastructure control systems

5. NIST PQC Standards

In August 2024, the National Institute of Standards and Technology (NIST) published the first three post-quantum cryptography standards, marking a historic milestone in cryptographic security.

FIPS 203

ML-KEM

Module-Lattice Key Encapsulation Mechanism. For secure key exchange in TLS, VPNs, and encrypted communications.

FIPS 204

ML-DSA

Module-Lattice Digital Signature Algorithm. For code signing, document signing, and authentication.

FIPS 205

SLH-DSA

Stateless Hash-Based Digital Signature Algorithm. A conservative alternative based on well-understood hash functions.

6. The Algorithms Explained

ML-KEM (Kyber)

ML-KEM is based on the Module Learning With Errors (MLWE) problem. It provides a way to securely establish shared secret keys between parties. In practice, it replaces ECDH key exchange in TLS and similar protocols.

  • Key sizes: 800 - 1568 bytes (depending on security level)
  • Ciphertext: 768 - 1568 bytes
  • Very fast: Comparable to classical algorithms

ML-DSA (Dilithium)

ML-DSA is also lattice-based, providing digital signatures that can replace RSA and ECDSA signatures. It's suitable for most signature use cases including TLS authentication, document signing, and code signing.

  • Public key: 1312 - 2592 bytes
  • Signature: 2420 - 4627 bytes
  • Fast signing and verification

SLH-DSA (SPHINCS+)

SLH-DSA is based entirely on hash functions, making it the most conservative choice. While signatures are larger and slower, the security assumptions are minimal and well-understood.

  • Public key: 32 - 64 bytes
  • Signature: 7856 - 49856 bytes (much larger)
  • Best for high-security, low-frequency signing

7. Implementation Strategy

Migrating to post-quantum cryptography requires a systematic approach. Here's a proven framework for enterprise PQC adoption:

Phase 1: Cryptographic Inventory

Identify all cryptographic assets in your organisation:

  • TLS/SSL certificates and configurations
  • VPN and encrypted tunnel technologies
  • Digital signature systems
  • Key management systems
  • Encrypted data stores
  • Third-party integrations using cryptography

Phase 2: Risk Assessment

Prioritise systems based on:

  • Data sensitivity and longevity requirements
  • Exposure to network interception
  • Regulatory requirements (NIS2, GDPR, etc.)
  • Business criticality

Phase 3: Hybrid Implementation

Deploy hybrid cryptography that combines classical and post-quantum algorithms. This approach ensures:

  • Backward compatibility with existing systems
  • Defence in depth (if one fails, the other protects)
  • Compliance with current and future requirements

Phase 4: Full Migration

Once hybrid systems are proven and classical cryptography is deprecated, transition to pure PQC implementations.

8. Planning Roadmap

Now
Assessment & Data Lifetime

Identify externally visible cryptographic posture and assess data-lifetime exposure

By 2028
Discovery & Initial Plan

Complete discovery and initial migration planning aligned with NCSC guidance

By 2031
Priority Migration

Undertake highest-priority migration activities

By 2035
Target Completion

Target completion of PQC migration for applicable systems, services and products

9. Getting Started

The transition to post-quantum cryptography is a significant undertaking, but it doesn't have to be overwhelming. Here are your next steps:

Free Quantum Readiness Check

Start by understanding where you stand. Our free scanner analyses your website's TLS configuration and quantum readiness in seconds.

Enterprise Assessment

For a comprehensive assessment of your organisation's cryptographic infrastructure and a tailored migration roadmap, contact our team for a consultation.

Post-Quantum Cryptography FAQs

What is post-quantum cryptography?

Post-quantum cryptography uses algorithms designed to resist attacks from both classical and quantum computers. It runs on conventional hardware and protects key exchange, digital signatures and other cryptographic functions.

Which post-quantum cryptography standards should organisations know?

The first NIST standards are FIPS 203 for ML-KEM key establishment, FIPS 204 for ML-DSA signatures and FIPS 205 for SLH-DSA signatures. The appropriate choice depends on the system and use case.

Does post-quantum cryptography replace all current encryption?

No. Migration mainly changes vulnerable public-key cryptography such as RSA and elliptic-curve systems. Organisations should inventory each use of cryptography before deciding what to replace, retain or test in a hybrid design.

How should an organisation start a post-quantum migration?

Start with a cryptographic inventory, rank systems by data lifetime and exposure, ask suppliers for migration evidence, then test a reversible pilot before wider deployment.

What is the second step after learning about post-quantum cryptography?

The second step is to turn awareness into evidence: scan external endpoints, build a cryptographic inventory, identify RSA and elliptic-curve dependencies, then prioritise systems with long-lived sensitive data.

Related Resources

Our Services

Explore our post-quantum cryptography implementation services.

Compliance

How PQC relates to NIS2, GDPR, and other regulations.

NIST FIPS 203/204/205

A practical guide to ML-KEM, ML-DSA and SLH-DSA.

PQC Implementation Guide

How to move from inventory to pilots across TLS, APIs, VPNs and signatures.

Post-Quantum Digital Signatures

How to compare ML-DSA and SLH-DSA for code, identity, document and device trust.

Post-Quantum Code Signing

How software teams should inventory signers, verifiers, release artefacts and suppliers.

Cloudflare, AWS and Fastly PQC Readiness

How to verify CDN and cloud PQC support at the hostname, API and client level.

TLS 1.2 Downgrade Risk and PQC

How to reduce TLS downgrade risk while moving toward TLS 1.3 and hybrid ML-KEM.

Quantum-Safe Certificate Badge

What T1, T2 and T3 verification badges prove, what they do not prove, and when to rescan.

Free Scanner Limitations

What external scans can find, what they cannot see, and when deeper testing is required.

Quantum-Safe TLS

How TLS 1.3 and hybrid ML-KEM affect public endpoints.

Website Quantum-Safe Checklist

How to check a public website before a full PQC audit.

X25519MLKEM768 Explained

What hybrid post-quantum TLS key exchange means in practice.

ML-KEM vs Kyber

What changed when Kyber became the NIST FIPS 203 standard.

PQC for APIs

How API owners should plan migration across TLS, mTLS and signatures.

Cyber Essentials and PQC

How UK Cyber Essentials evidence connects to TLS readiness and PQC migration planning.

NIS2 and PQC

How NIS2 cryptography, supplier risk and resilience work connect to post-quantum migration.

DORA and PQC

How financial entities can connect DORA ICT risk, supplier evidence and PQC migration.

Cryptographic Inventory Guide

How to map algorithms, systems, suppliers, owners and data lifetime before PQC migration.

PQC Checklist for CTOs

A board-ready checklist for scans, inventory, supplier evidence, pilots and governance.

PQC for Financial Services

How financial services teams should plan PQC migration across DORA, APIs, suppliers and signing.

PQC for Healthcare Data

How healthcare organisations should prioritise patient data, suppliers, portals and records.

Post-Quantum Cryptography UK

UK implementation planning for NCSC timelines, NIST standards and regulated data.

Free readiness account

Keep This Guide Connected to a Real Website Scan

A PQC guide is more useful when it is attached to current evidence. Create a free account, add a public domain now or later, and keep a repeatable baseline for TLS, security headers and visible post-quantum readiness.

No cardStart the free evidence path without a paid plan.
Saved scanKeep the public endpoint result after the browser session.
Rescan laterRerun after TLS, header or provider changes.

Prefer to scan first? Open the free quantum security scanner.

Create Your Free Account

Start with Google, Microsoft or a one-time email code. You can add a domain now if you want the scanner to run after signup, but it is not required.

No cardNo passwordFree saved scan
Add a domain to scan after signup (optional)

Leave this blank to create the account first and scan later.

or use email code

No card or password is needed. The free account can keep scan evidence for rescans and badge qualification when you add a public domain.