The Post-Quantum Migration: What the Headlines Missed About Cryptographic Inventory
Archi4 min read
Contents
- The Quantum Deadline Nobody Can See
- What the Headlines Missed
- The Inventory Problem in Practice
- What Happens Next: Three Forecasts
- 1. Regulatory Pressure Will Shift from Algorithms to Evidence
- 2. The Biggest Breaks Will Come from Forgotten Systems
- 3. Hybrid Deployments Will Become the Default Transition
- The Quiet Work Ahead
The Quantum Deadline Nobody Can See#
The headlines about quantum computing and cryptography tend to focus on the finish line: a machine that can break RSA or elliptic-curve keys. That moment is still years away, if it arrives at all. The more immediate problem is the starting line. Most organizations do not know where their cryptography is.
Cryptographic inventory is the unglamorous first step of any post-quantum migration. It means finding every key, certificate, protocol, library, and hard-coded secret across servers, endpoints, network gear, and cloud services. It sounds like a spreadsheet exercise. It is closer to an archaeology project.
A 2023 survey by the Ponemon Institute found that the average organization has more than 50 cryptographic libraries in use, many of them undocumented. That number is a symptom. The real issue is that cryptography is embedded in places nobody thinks to look: firmware, build scripts, backup tapes, and the Java keystore on a server that has not been rebooted since 2019.
What the Headlines Missed#
Recent coverage of NIST's post-quantum standards focused on the algorithms: CRYSTALS-Kyber for key exchange, CRYSTALS-Dilithium for signatures, and their siblings. That is the easy part. The algorithms are published, the reference implementations are open source, and the performance is reasonable.
The hard part is the long tail. A typical enterprise runs hundreds of applications, many of them built by teams that no longer exist. Each one may use cryptography in ways that are not visible from the outside. A payment gateway might call OpenSSL for TLS, but it might also use a homegrown token format with a hard-coded AES key. A mobile app might pin certificates in a way that breaks when the backend rotates to a new algorithm.
Security teams call this the "crypto debt" problem. It is similar to technical debt, but with a deadline attached. The deadline is not the day quantum computers arrive. It is the day an adversary starts harvesting encrypted traffic now with the intention of decrypting it later. That practice, known as harvest-now-decrypt-later, is already happening, according to several government advisories.
The Inventory Problem in Practice#
What does a cryptographic inventory actually look like? In the early stages, it is messy. Teams use a mix of network scanning, code analysis, and manual interviews. Commercial tools from vendors like IBM and SandboxAQ promise to automate the process, but none of them can see everything. The gaps are usually in custom code and operational technology.
A more realistic approach is to start with the highest-value data flows. Where does sensitive data travel? What protects it in transit and at rest? Which systems would be catastrophic to lose? That prioritization exercise is more useful than a complete inventory, because it directs resources to the places that matter.
The next step is to establish a cryptographic bill of materials, or CBOM. The idea borrows from software bills of materials (SBOMs), which list the components in a piece of software. A CBOM lists the cryptographic assets and their dependencies. The format is still evolving, but the concept is sound: you cannot migrate what you cannot see.
What Happens Next: Three Forecasts#
1. Regulatory Pressure Will Shift from Algorithms to Evidence#
Governments are already publishing post-quantum migration guidance. The US National Security Agency has a deadline of 2030 for national security systems. The UK's NCSC recommends starting now. But the next wave of regulation will not just ask whether you have a plan. It will ask for evidence that the plan is working.
Expect audit frameworks to require cryptographic inventories as part of compliance. That will create a market for tools that can produce verifiable reports. It will also expose organizations that have been marking time.
2. The Biggest Breaks Will Come from Forgotten Systems#
The first major post-quantum migration failure will not be in a flagship product. It will be in a legacy system that nobody remembered was still running. A certificate authority that issues internal certificates. A VPN concentrator with a fixed firmware image. A code-signing pipeline that uses an old library.
The lesson will be expensive. Organizations that start inventory work now will have a map when the failure happens. Those that do not will be guessing.
3. Hybrid Deployments Will Become the Default Transition#
Most organizations will not switch to post-quantum algorithms in one step. They will run hybrid modes, combining classical and post-quantum algorithms, so that a break in one does not compromise the whole. Chrome and Cloudflare have already tested hybrid key exchange. The approach adds complexity, but it buys time.
The forecast here is not that hybrid is perfect. It is that hybrid is inevitable. The transition will be messy, with performance trade-offs and interoperability glitches. The organizations that plan for that mess will come out ahead.
The Quiet Work Ahead#
The post-quantum migration will not be won by the organization that adopts the newest algorithm first. It will be won by the one that knows where its cryptography lives. That work is slow, unglamorous, and easy to postpone. It is also the only way to avoid a deadline that nobody can see coming.
More articles