What is post-quantum cryptography (PQC) migration?

PQC migration is the process of replacing quantum-vulnerable public-key cryptography (RSA, ECC, DH) with NIST-standardized post-quantum algorithms (ML-KEM for key encapsulation, ML-DSA and SLH-DSA for digital signatures). It typically spans 3–7 years across discovery, planning, hybrid rollout, and full cutover phases.

When should we start migrating to post-quantum cryptography?

Now. CNSA 2.0 mandates US National Security Systems complete the transition by 2035, with software/firmware signing prioritized for 2025. Harvest-now-decrypt-later attacks already make any data with a confidentiality lifetime past 2030 a present-day risk, even before a cryptographically relevant quantum computer exists.

What are the NIST-standardized PQC algorithms?

NIST published three primary standards in August 2024: FIPS 203 (ML-KEM, formerly Kyber) for key encapsulation; FIPS 204 (ML-DSA, formerly Dilithium) for general-purpose digital signatures; and FIPS 205 (SLH-DSA, formerly SPHINCS+) for stateless hash-based signatures. FIPS 206 (FN-DSA, formerly Falcon) is in draft.

Why use hybrid X.509 certificates during migration?

Hybrid X.509 certificates carry both a classical (RSA or ECC) and a post-quantum (ML-DSA or SLH-DSA) key pair. This provides defense in depth during the transition: a flaw in either algorithm does not break the certificate, and clients that only support one algorithm family can still validate. Hybrid mode is the recommended migration path in IETF drafts and CNSA 2.0 guidance.

How does QuantumSecure Migration prioritize remediation?

Migration ranks each cryptographic asset by three factors: harvest-now-decrypt-later exposure (data confidentiality lifetime), regulatory deadline (CNSA, PCI, sector mandates), and operational dependency depth. The output is a phased roadmap — Quick Wins (0–3 months), Strategic (3–12 months), Transformation (12–24 months) — with effort estimates and rollback plans per item.

L3Plan — Layer 3 of the platform

Migration Roadmap & Decision Engine

Turn the inventory into a phased, auditable plan. Every action is scored on quantum risk × data sensitivity × asset type, sorted into Quick Wins, Strategic, and Transformation phases — and tagged for one-click execution by Layer 4 where applicable.

Phased planQuick winsInvestment estimateL4 CA handoffAuditable scoring model

Sample artefact

CRITICAL

HIGH

MED

Phase 1 — Quick Wins (0–3 mo)

• Rotate payments cert → hybrid X.509 (CRITICAL, M, → L4)
• Enable hybrid KEM on edge-api (HIGH, S)
• Upgrade AES-128 keys in warehouse (MED, S)

Phase 2 — Strategic (3–12 mo)

• Replace ECDSA-P256 in admin auth flow
• Roll out PQC KEM across internal mTLS
• Crypto-agility wrapper in payment SDK

Phase 3 — Transformation (12–24 mo)

• Decommission legacy IPSEC tunnels
• Replace HSMs that lack PQC firmware
• Vendor & supplier PQC compliance gates

Who it's for

CISOs who have to defend the migration plan to the board
Programme managers who need to sequence work across teams
Architects who want a no-regret path before vendor commits
Anyone whose roadmap today is a slide, not a system of record

What you get

Phased roadmap (0–3 mo / 3–12 mo / 12–24 mo)
Per-action priority (CRITICAL / HIGH / MED / LOW)
Per-action effort band (S / M / L / XL)
Per-action handoff layer (→ L4 CA where relevant)
Quick-wins shortlist for first sprint
Snapshot history — see how the plan evolves

How it works

Step 1

Pull the inventory

Run on the L2 inventory you already have. No re-import, no second source of truth.

Step 2

Score every asset

score = risk × data classification × asset type. Explicit, auditable; we publish the model.

Step 3

Bucket and dispatch

Quick Wins surface; Strategic and Transformation flow into the programme. Actions tagged → L4 can be executed straight from the CA.