Field Notes
Post-Quantum Is an Inventory Problem Before It Is a Cryptography Problem
Post-quantum planning starts with an inventory: long-lived data, dependent systems, suppliers, and the documented path to upgrade or replace them.
A post-quantum plan cannot begin with, “Which new algorithm should we buy?” It begins with a less glamorous question: where, exactly, does the organization rely on public-key cryptography, and which of those dependencies can actually be changed?
NIST’s new transition report is useful partly because it makes the answer larger than an encryption setting. The change can touch applications, cryptographic libraries, hardware, certificate infrastructure, network protocols, cloud services, and the vendors that maintain them. If those dependencies are unknown, a date on a roadmap is mostly decorative.
An inventory reveals the replacement problem
Consider a business with a customer portal, a VPN, laptops that verify software updates, a hosted line-of-business application, and a device that will remain in service for years. Each may use public-key cryptography differently. Some may be updated by a vendor. Some may need a firmware update, a new certificate process, or eventual replacement. Some may already use a service whose provider controls the underlying change.
That is why a useful first inventory is not a search for every mathematical detail. It is a record of the systems that protect important information or establish trust, what information must remain confidential for a long time, who supplies each system, and what the supplier says about its upgrade or replacement path. The record will be incomplete at first. That is still more actionable than treating the organization as one undifferentiated “encryption project.”
NIST IR 8547 describes the same practical layering: applications depend on libraries and hardware; public-key infrastructure has its own issuance, validation, and revocation work; protocols may need to accommodate different key sizes or interfaces. A change at one layer does not establish that the others are ready.
Not every item has the same clock
Post-quantum planning is often discussed as if a future quantum computer will ring a bell and every organization must migrate on the same afternoon. NIST does not describe it that way. Its federal timelines apply to particular federal systems, and the report says migration details and schedules vary by use case.
The difference matters. The “harvest now, decrypt later” risk is most relevant when someone can collect encrypted information today and that information must remain confidential far into the future. A short-lived transaction, a system that can be upgraded quickly, and a device with a long replacement cycle are not necessarily the same planning problem. Digital signatures, authentication, encrypted archives, and software-update verification also create different dependencies.
This is not an argument to wait for a prediction about when quantum computers will become capable enough to break current public-key systems. NIST says no such cryptanalytically relevant machine currently exists, while also noting that cryptographic migrations can take a long time. The sensible conclusion is narrower: identify which commitments last longest and which systems move slowest before deciding what should be first.
Ask suppliers for a path, not a promise
An inventory becomes useful when it produces specific conversations. For each consequential system, ask: What public-key functions does this product or service use? Who controls the upgrade? Is a supported post-quantum or hybrid option documented? Does a dependency such as a hardware module, certificate authority, remote peer, or older device limit the change? If the product cannot support the transition, is there a replacement or retirement path?
Those questions are not a demand for every vendor to deploy a new algorithm tomorrow. They are a way to discover where a future transition depends on contracts, refresh cycles, interoperability, or a decision someone else must make. NIST notes that systems unable to support post-quantum cryptography should be identified for replacement or decommissioning in the federal context; for other organizations, the comparable task is to know whether such a dependency exists before it becomes an urgent surprise.
Make the first deliverable small enough to use
A business does not need to turn this into a speculative technology program. Start with one bounded record: the service or system, the protected information or trust function, the owner and supplier, the expected life of the data or equipment, and the documented next step. Mark unknowns plainly. A supplier’s unsupported answer is useful evidence too.
That record will not choose an algorithm or prove that a migration is complete. It does something earlier and more valuable: it turns post-quantum cryptography from a distant noun into a list of business dependencies that can be scheduled, funded, or retired on purpose.
No name or email needed. Select a rating to add details; click it again to clear it.