Research briefs · Cybersecurity · Updated 2026-11-08

Why start post-quantum migration with inventory?

New standards are usable, but migration depends on finding cryptography embedded across systems and suppliers.

Thesis

The first practical post-quantum investment is a cryptographic inventory tied to data lifetime, system criticality, supplier plans, and upgrade paths.

Market context

Editorial analysis: New standards are usable, but migration depends on finding cryptography embedded across systems and suppliers. A useful decision framework considers ownership, exceptions, evidence, and change control alongside the technology itself.

Editorial analysis: standards and frameworks can provide shared terminology, but a citation to a standard does not establish how a particular product or organization implements it.

NIST's October 2026 transition report sets post-quantum migration milestones for 2030, 2031, and 2035; organizations should prioritize cryptographic inventory and transition planning.

Evidence

  • NIST finalized FIPS 203 for ML-KEM, FIPS 204 for ML-DSA, and FIPS 205 for SLH-DSA in 2024. These standards provide algorithms for key establishment and digital signatures, but publication does not automatically update deployed protocols, hardware, certificates, or vendor products.
  • CISA, NSA, and NIST have urged organizations to create quantum-readiness roadmaps, inventories, supply-chain assessments, and vendor engagement. Inventory matters because cryptography is often hidden in libraries, appliances, firmware, identity systems, backups, and long-lived data exchanges.
  • Editorial analysis: implementation controls should be mapped to the system, users, data, and consequences in scope; the cited sources do not establish that any particular deployment has passed those controls.
  • Editorial analysis: reviewers may find it useful to preserve dated implementation evidence and distinguish policy, configuration, and exception records.

Competing viewpoints

Editorial analysis: a standardization-first approach may improve consistency and supplier comparability, but should not be treated as proof that an implementation is effective.

Editorial analysis: a context-first approach can better reflect local risk, but may reduce consistency and require more governance. Neither position is established by the cited sources as universally preferable.

Implications

  • Record algorithm, key use, protocol, owner, supplier, and replacement constraints.
  • Prioritize systems protecting data that must remain confidential for years.
  • Ask suppliers for standards-based migration timelines and interoperability evidence.
  • Budget for evidence collection, exception handling, and periodic retesting; these are continuing operating costs, not one-time implementation tasks.
  • Use procurement and architecture review to expose dependencies early, because a technically valid control can still fail when ownership or supplier obligations are ambiguous.

Actionable takeaways

  • Write a one-page scope statement naming the covered systems, data, users, environments, and explicit exclusions. Give the scope an owner and review date.
  • Convert each cited principle into a testable requirement with an evidence source, pass condition, collection cadence, and escalation route.
  • Run one representative end-to-end test, including an adverse or exception case, and retain the configuration, inputs, outputs, and decision record.
  • Add relevant requirements to supplier evaluation and contracts. Ask for product-specific evidence and change notification rather than provider-wide assurances.
  • Review the control after material releases, architecture changes, incidents, and supplier changes; close expired exceptions or renew them with fresh evidence.

Limitations and risks

Cryptographic standards and product support continue to evolve. Migration priority depends on threat model, information lifetime, performance, protocol dependencies, and regulatory requirements. The primary sources define mechanisms, practices, or reference models; they do not measure this organization's implementation or guarantee an outcome. This is not a product comparison, legal opinion, penetration test, or audit conclusion. Applicability changes with architecture, versions, contracts, jurisdiction, threats, and data sensitivity. Validate assumptions against current source editions and product documentation, test representative failures, and obtain specialist advice for regulated or high-consequence decisions.

Sources and citations

  1. Transition to Post-Quantum Cryptography Standards — NIST, accessed 2026-11-08
  2. Quantum-Readiness: Migration to Post-Quantum Cryptography — CISA, accessed 2026-09-06