Q-Cyber Magazine

Enterprise · 3 November 2026 · 3 min read

An enterprise plan for post-quantum migration

NIST's 2026 transition report asks organisations to treat post-quantum migration as a current operational priority, beginning with a cryptographic inventory and early use of FIPS 203, 204 and 205.

Abstract graphic of a lattice of connected points in Knowlcom blue

For most enterprises, the post-quantum problem is not a research brief. It is a replacement programme: find the public-key cryptography already in use, decide what must move first, and buy products that can change algorithms without a full redesign.

Begin with what you already run

NIST's October 2026 report is written for federal agencies, technology providers and standards bodies, but its first instruction is universal: identify quantum-vulnerable algorithms and plan their replacement. That inventory should cover applications, protocols, certificates, hardware security modules, devices, and the suppliers who embed cryptography that the enterprise never configured itself.

Two sequencing rules follow from the published guidance. First, because of harvest-now-decrypt-later, key establishment for long-lived or highly sensitive data should move early, which points to FIPS 203. Second, signatures and the certificate infrastructure that underwrite software and identity must follow, using FIPS 204 and FIPS 205. NIST also accommodates hybrid constructions that combine classical and post-quantum algorithms. They are more conservative and more expensive computationally. For many enterprises they will be the practical bridge, not a way to avoid choosing a standard.

Exhibit 1

Dates that should appear on an enterprise PQC plan

  1. 13 August 2024

    Principal PQC standards approved: FIPS 203, 204 and 205

  2. 27 October 2026

    NIST IR 8547 issued, with transition plans for quantum-vulnerable algorithms

  3. 31 December 2030

    Federal high-value and high-impact systems: PQC key establishment

  4. 31 December 2031

    Federal high-value and high-impact systems: PQC digital signatures

  5. 2035

    Primary federal completion target; quantum-vulnerable algorithms to leave NIST standards

Source: NIST FIPS announcement, 13 August 2024; NIST, 27 October 2026, and NIST IR 8547.

Reference

Size comparisonPublic keys: classical vs post-quantum
Public keys: classical vs post-quantum, in bytes
AlgorithmBarSize (bytes)
X25519 public key32 bytes
RSA-2048 public modulus256 bytes
ML-KEM-512 encapsulation key800 bytes
ML-KEM-768 encapsulation key1,184 bytes
ML-KEM-1024 encapsulation key1,568 bytes
ML-DSA-65 public key1,952 bytes

ML-KEM ciphertexts are 768, 1,088 and 1,568 bytes for the three parameter sets.

Sources NIST FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA), FIPS 186-5 (ECDSA); RFC 7748 (X25519); RFC 8032 (Ed25519).

Size comparisonSignatures: classical vs post-quantum
Signatures: classical vs post-quantum, in bytes
AlgorithmBarSize (bytes)
Ed2551964 bytes
ECDSA P-25664 bytes
RSA-2048256 bytes
ML-DSA-442,420 bytes
ML-DSA-653,309 bytes
ML-DSA-874,627 bytes
SLH-DSA-SHA2-128s7,856 bytes
SLH-DSA-SHA2-128f17,088 bytes

SLH-DSA keeps a 32-byte public key but carries the largest signatures.

Sources NIST FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA), FIPS 186-5 (ECDSA); RFC 7748 (X25519); RFC 8032 (Ed25519).

The supply chain is part of the plan

NIST is explicit that an organisation's cryptographic supply chain matters as much as its own systems. Enterprises should therefore put cryptographic agility and a dated PQC road map into vendor contracts, and should ask how each product will handle hybrid modes, certificate chains and performance. A supplier that can only promise a future review is a programme risk.

The work is easier if it is owned. A named officer, a backlog tied to the 2030–2035 markers, and a board-visible inventory of long-lived data are enough to start. Advisory support, including on cryptographic engineering review, is useful only after those artefacts exist.

Implications

  1. Inventory first. No road map is credible without a list of algorithms, protocols and suppliers.
  2. Prioritise confidentiality life. Move key establishment for long-lived data before cosmetic upgrades.
  3. Buy agility. Prefer products and contracts that can change algorithms.
  4. Use the federal dates as planning anchors, especially if you sell to or process data for government or regulated clients.

What this means for enterprise

The standards are no longer pending. The enterprises that will finish on time are the ones that can already point to an inventory, a first-wave list and a supplier conversation. That work can begin this quarter.

Sources

  1. NIST Report Provides Guidelines for Transition to Post-Quantum Cryptography Standards
  2. NIST IR 8547
  3. NIST FIPS 203, 204 and 205 announcement
  4. NIST Post-Quantum Cryptography project