Post-Quantum Cryptography and Quantum Readiness

NIST finalised its first post-quantum cryptography standards in August 2024: ML-KEM (CRYSTALS-Kyber) for key encapsulation and ML-DSA (CRYSTALS-Dilithium) for digital signatures. The standards exist. The migration work does not, for the vast majority of organisations. The threat driving urgency is harvest-now-decrypt-later — adversaries collecting encrypted traffic today to decrypt once quantum hardware matures.

Why this is an immediate — not future — threat

Data with a long sensitivity lifetime is already at risk. If a cryptographically relevant quantum computer emerges in the next 10–15 years, harvested data becomes readable. Organisations protecting data that must remain confidential for a decade or more need to act now, not when quantum hardware appears.

A practical quantum-readiness roadmap

Step one: cryptographic inventory — map every algorithm in use across TLS configurations, VPN endpoints, code-signing certificates, SSH keys, and application-layer crypto. Step two: prioritise systems protecting long-lived sensitive data. Step three: test NIST-standard algorithms in non-production environments, noting that performance differs significantly from RSA/ECC, especially on embedded systems.

• Conduct a full cryptographic inventory. Prioritise systems protecting data with 10+ year sensitivity requirements.
• Assess vendor and library support for ML-KEM and ML-DSA — major TLS libraries now include support.
• Pilot hybrid TLS configurations (classical + post-quantum) in your most sensitive data flows.
• Review certificate lifetimes and PKI architecture — post-quantum certificates are significantly larger.
• Include quantum readiness requirements in vendor security assessments.