Pavan Rangani

Home › Blog › Post-Quantum Cryptography Migration: Enterprise Implementation Guide

Post-Quantum Cryptography Migration: Enterprise Implementation Guide

By Pavan Rangani · May 8, 2026 · Security

Post-Quantum Cryptography Migration: Enterprise Implementation Guide

Why Post-Quantum Cryptography Migration Cannot Wait

The threat model for post-quantum cryptography migration is not “quantum computers will break TLS tomorrow.” Instead, it is “adversaries are recording encrypted traffic today and will decrypt it whenever cryptographically relevant quantum computers arrive.” This “harvest now, decrypt later” model means data with multi-decade confidentiality requirements (medical records, intellectual property, classified information) is already at risk regardless of when CRQCs actually emerge.

Furthermore, NIST finalized the first three post-quantum standards in 2024, and major TLS implementations now support hybrid key exchange in production. Consequently, enterprises have no remaining excuse to defer planning. This guide walks through the algorithm choices, deployment patterns, and inventory strategies a large migration needs.

The NIST PQC Standards You Need to Know

Three FIPS standards anchor the migration. FIPS 203 specifies ML-KEM (formerly Kyber), a lattice-based key encapsulation mechanism that replaces RSA and ECDH for key establishment. FIPS 204 specifies ML-DSA (formerly Dilithium), a lattice-based digital signature algorithm. Additionally, FIPS 205 specifies SLH-DSA (formerly SPHINCS+), a hash-based signature scheme used as a hedge against unknown lattice attacks.

For most enterprises, ML-KEM-768 and ML-DSA-65 hit the sweet spot of NIST Level 3 security with manageable key and signature sizes. SLH-DSA produces much larger signatures (from 7,856 bytes for the 128s parameter sets to 49,856 bytes for the 256f sets, per FIPS 205) and is reserved for root-of-trust scenarios like firmware signing where signature bandwidth is acceptable. Refer to the NIST Post-Quantum Cryptography project for canonical specifications.

NIST post-quantum cryptography standards
NIST finalized ML-KEM, ML-DSA, and SLH-DSA as the first PQC standards.

TLS 1.3 Hybrid Key Exchange Today

Hybrid key exchange combines a classical algorithm (X25519) with a post-quantum KEM (ML-KEM-768) so the resulting session key is secure as long as either component is unbroken. The IANA-registered codepoint X25519MLKEM768 is now supported by Chrome, Firefox, BoringSSL, OpenSSL 3.5, and major load balancers. This is the recommended deployment posture for the next 3–5 years.

However, hybrid handshakes increase the ClientHello size enough to trigger TCP segmentation, which exposed bugs in some middleboxes during early rollouts. When Cloudflare tested sending the post-quantum key share in the first ClientHello to its customers’ origin servers, about 0.34% of connections broke, a higher rate than browsers saw; it attributed many failures to the larger ClientHello and most to servers that did not implement HelloRetryRequest correctly. Consequently, you must monitor TLS handshake error rates carefully during initial deployment.

// JDK 27+ TLS configuration with hybrid PQC key exchange (JEP 527)
import javax.net.ssl.*;
import java.security.*;
import java.security.spec.*;

public class HybridTLSServer {
    public static SSLContext createHybridContext(KeyStore ks, char[] pwd) throws Exception {
        // JDK 24 added ML-KEM and ML-DSA as standalone APIs (JEPs 496, 497); JDK 27
        // (JEP 527) adds X25519MLKEM768 to TLS 1.3 and enables it first by default
        System.setProperty("jdk.tls.namedGroups",
            "x25519mlkem768,x25519,secp256r1,secp384r1");
        // No released JDK negotiates ML-DSA in TLS yet (it is slated for JDK 28)
        System.setProperty("jdk.tls.server.SignatureSchemes",
            "ecdsa_secp256r1_sha256,rsa_pss_rsae_sha256");

        KeyManagerFactory kmf = KeyManagerFactory.getInstance("PKIX");
        kmf.init(ks, pwd);

        TrustManagerFactory tmf = TrustManagerFactory.getInstance("PKIX");
        tmf.init(ks);

        SSLContext ctx = SSLContext.getInstance("TLSv1.3");
        ctx.init(kmf.getKeyManagers(), tmf.getTrustManagers(), SecureRandom.getInstanceStrong());

        SSLParameters params = ctx.getDefaultSSLParameters();
        params.setProtocols(new String[] { "TLSv1.3" });
        params.setNamedGroups(new String[] { "x25519mlkem768", "x25519" });
        return ctx;
    }
}

Building a Cryptographic Bill of Materials

You cannot migrate what you cannot find. The Cryptography Bill of Materials (CBOM) extension to CycloneDX gives you a structured inventory of every algorithm, key length, certificate, and protocol in your software supply chain. A practical way to build one combines static analysis (for example, IBM’s CBOMkit) with runtime tracing of TLS connections.

An inventory like this usually surfaces older weaknesses first, such as 1024-bit RSA keys in legacy systems or outdated ciphers kept for compatibility with a vendor library. Fix those before starting the PQC migration itself. This kind of inventory work pairs well with our secret scanning guide for full supply chain visibility.

Certificate Lifecycle and Bigger Keys

ML-DSA-65 public keys are roughly 1,952 bytes and signatures are roughly 3,309 bytes, compared to 32 bytes and 64 bytes for Ed25519. Consequently, certificates roughly triple in size, which has cascading effects on TLS handshake bandwidth, OCSP responses, and certificate transparency logs. For high-volume CDN edges, this is meaningful.

Additionally, the certificate authority ecosystem is still rolling out PQC issuance, and the CA/Browser Forum Baseline Requirements do not yet permit post-quantum keys in publicly trusted TLS certificates. Let’s Encrypt published a plan in June 2026 that targets 2027 for production post-quantum certificates based on Merkle Tree Certificates. For internal PKI, you can move faster: AWS Private CA (since November 2025), DigiCert Private CA, and HashiCorp Vault’s PKI secrets engine (since Vault 2.2.0) support ML-DSA certificate issuance, and GMO GlobalSign has offered test certificates from an ML-DSA or SLH-DSA private CA since May 2025.

post-quantum cryptography migration certificate lifecycle
PQC certificates triple in size, with downstream effects on bandwidth and storage.

Migration Phases That Actually Work

A workable rollout has five phases, usually spread over more than a year. Phase 1 is inventory and CBOM generation. Phase 2 is hybrid TLS deployment for external-facing services behind feature flags. Phase 3 covers internal mTLS migration. Phase 4 addresses signing operations (JWT, code signing, document signing). Finally, Phase 5 deprecates classical-only paths once telemetry shows sufficient hybrid adoption.

Critically, do not disable classical algorithms during the rollout. Hybrid mode keeps classical algorithms as a fallback, and removing them prematurely creates outages when intermediaries do not support PQC. The defensive posture is “add PQC, keep classical, monitor, then deprecate” over a multi-year horizon similar to patterns in our mTLS and certificate pinning guide.

# nginx 1.27+ with OpenSSL 3.5 hybrid PQC configuration (inside the http block)
# Telemetry for handshake monitoring; log_format is only allowed at http level
log_format pqc_handshake '$remote_addr $ssl_protocol $ssl_cipher $ssl_curve $request_time';

server {
    listen 443 ssl;
    listen 443 quic reuseport;
    http2 on;
    server_name api.example.com;

    ssl_protocols TLSv1.3;
    # ssl_ciphers only covers TLS 1.2 and below; TLS 1.3 suites go through ssl_conf_command
    ssl_conf_command Ciphersuites TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256;

    # Hybrid PQC key exchange - X25519+ML-KEM-768
    ssl_ecdh_curve X25519MLKEM768:X25519:secp384r1;

    # Dual-stack certificates: classical + PQC
    ssl_certificate         /etc/nginx/certs/api-ecdsa.crt;
    ssl_certificate_key     /etc/nginx/certs/api-ecdsa.key;
    ssl_certificate         /etc/nginx/certs/api-mldsa65.crt;
    ssl_certificate_key     /etc/nginx/certs/api-mldsa65.key;

    ssl_session_cache shared:SSL:50m;
    ssl_session_timeout 1d;
    ssl_session_tickets off;

    access_log /var/log/nginx/pqc.log pqc_handshake;
}

Cloud Provider Rollout Timelines

AWS enabled ML-KEM hybrid key agreement on the non-FIPS endpoints of AWS KMS, ACM, and Secrets Manager in all commercial Regions in April 2025, and CloudFront added hybrid post-quantum key exchange to all of its TLS security policies for viewer connections in September 2025. Google Cloud Load Balancing added X25519MLKEM768 for Application Load Balancers and external proxy Network Load Balancers in June 2026, opt-in at first and enabled by default from October 2026. Cloudflare led the field, enabling the draft X25519Kyber768Draft00 hybrid for all websites and APIs in October 2022 and later adding the standardized X25519MLKEM768 codepoint, which its documentation now recommends over the obsolete draft.

For HSM-backed signing operations, support lags. AWS CloudHSM added ML-DSA key generation and signing in Client SDK 5.18.0 in August 2026, while Thales Luna HSM firmware 7.9 and Entrust nShield firmware 13.8, both released in 2025, already include ML-KEM and ML-DSA. Plan accordingly: HSM-bound keys cannot be migrated by software changes alone.

cloud post-quantum cryptography migration timeline
Major cloud providers now offer hybrid PQC TLS, with HSM signing support catching up.

In conclusion, post-quantum cryptography migration is a multi-year program, not a sprint. Start with cryptographic inventory, deploy hybrid TLS to externally-facing services first, plan for tripled certificate sizes, and never remove classical algorithms until telemetry proves it safe. The data you protect today must remain confidential for decades, and adversaries are already harvesting.

Related articles

← Back to all articles