Post-Quantum Crypto Headlines Miss the Migration Checklist
Archi4 min read
Contents
The Headline Gap#
Another week, another story about quantum computers breaking encryption. The pieces usually end with a warning: organizations must migrate to post-quantum cryptography. What they rarely include is the operational checklist that makes a migration possible. That gap matters because the algorithms are only one piece. The harder work is finding every place cryptography lives in your systems, deciding what to replace, and testing the replacements without breaking production.
The National Institute of Standards and Technology finalized its first three post-quantum algorithms in 2024: ML-KEM for key encapsulation, and ML-DSA and SLH-DSA for digital signatures. Vendors have started shipping support. But a headline that says "quantum-safe" often skips the inventory problem: most organizations do not have a complete list of their cryptographic assets, key lengths, or protocol versions. Without that list, a migration plan is guesswork.
This checklist is for the teams who have to do the work. It covers the steps that headlines miss, from asset inventory to crypto agility, with a focus on what you can start measuring this quarter.
1. Inventory Every Cryptographic Endpoint#
Start with a question: where does your system use cryptography? The answer is broader than most teams expect. It includes TLS certificates, SSH keys, code signing keys, database encryption, API tokens, VPNs, hardware security modules, and firmware update signatures. It also includes forgotten places: test environments with production keys, old backup tapes, and third-party libraries that bundle their own crypto.
A practical first step is to run a discovery scan across your network and cloud accounts. Tools exist for certificate discovery, but they rarely cover every protocol. You will need to combine automated scanning with manual review of architecture diagrams and vendor contracts. Record the algorithm, key size, protocol version, and owner for each endpoint. That record becomes your migration backlog.
2. Separate the Harvest Now Problem from the Rest#
Not all data needs the same urgency. The "harvest now, decrypt later" threat applies to data that must stay confidential for years: health records, financial data, intellectual property, and government secrets. If an adversary can record encrypted traffic today and decrypt it after a quantum computer arrives, then long-lived secrets are at risk now.
For each data store, ask how long the data must remain confidential. If the answer is more than five to ten years, prioritize it for post-quantum key exchange. If the data is ephemeral, like session tokens, the migration can wait for vendor support. This sorting prevents teams from trying to replace everything at once.
3. Build Crypto Agility Before You Need It#
Crypto agility means the ability to swap algorithms without rewriting applications. Most systems are not agile: a certificate hard-coded to RSA-2048, a library pinned to an old version, or a protocol that only supports one key exchange. The migration to post-quantum algorithms will not be the last one. New algorithms will appear, and some current candidates may be weakened by future research.
A practical test: can you change the algorithm used by your TLS termination point in a staging environment without a code deploy? If not, that is a gap. Start by abstracting cryptographic operations behind interfaces, and by requiring vendors to document how they support algorithm updates. The goal is to make the next migration cheaper than this one.
4. Test Hybrid Modes in Real Traffic#
Many vendors are shipping hybrid key exchange, which combines a classical algorithm with a post-quantum one. The idea is to keep security if one algorithm fails. The headlines call this "quantum-safe," but the operational detail is that hybrid modes can increase handshake size and CPU cost. A TLS handshake that grows from a few kilobytes to tens of kilobytes can cause fragmentation and timeouts on constrained networks.
Run hybrid modes in a canary environment with real traffic patterns. Measure latency, CPU, and packet loss. Check that load balancers, firewalls, and monitoring tools can parse the larger handshakes. Some older network devices may drop packets they cannot inspect. These failures rarely make headlines, but they will stall a rollout.
5. Do Not Forget Signatures#
Most coverage focuses on encryption, but signatures matter too. If a quantum computer can forge a signature, then software updates, certificate chains, and authentication tokens become attack vectors. The migration for signatures is often harder because it involves trust stores and long-lived certificates.
Start by inventorying where you verify signatures: firmware updates, package managers, code repositories, and identity providers. Ask vendors how they plan to support ML-DSA or SLH-DSA. For internal systems, test signature verification performance, since some post-quantum signature schemes produce larger keys and signatures than current ones.
6. Plan for the Long Tail of Embedded Systems#
The hardest migration targets are embedded devices with long service lives: industrial controllers, medical devices, and network hardware. These systems may not support algorithm updates, and their vendors may not exist in five years. A headline about a new standard does not help a plant manager with a 20-year-old controller.
Build a register of embedded systems and their cryptographic capabilities. For each, record the expected service life and the vendor's update path. Where updates are impossible, plan compensating controls: network segmentation, dedicated encryption gateways, or replacement budgets. This is unglamorous work, but it determines whether a migration succeeds.
7. Measure Progress with Concrete Metrics#
The final checklist item is measurement. Track the percentage of endpoints that support post-quantum algorithms, the number of certificates with key sizes below your policy, and the time to rotate a key in each system. These metrics turn a vague goal into a managed program. Review them quarterly, and adjust priorities as vendor support improves.
The headlines will keep focusing on quantum breakthroughs. The teams that manage this migration will be the ones who spent the quiet quarters building inventories, testing hybrids, and retiring hard-coded algorithms. That work does not generate press releases, but it is what makes the transition real.
More articles