CIOs should begin post-quantum cryptography (PQC) migration planning now—not because a quantum computer capable of breaking today’s public-key cryptography is known to be imminent, but because its arrival date is uncertain, sensitive data can remain valuable for years, and enterprise cryptography takes time to find and replace. NIST’s three finalized PQC standards are ready for implementation, making inventory, risk prioritization, supplier engagement, and controlled testing practical first steps.
What is post-quantum cryptography, and what does it protect?
Post-quantum cryptography uses cryptographic algorithms designed to resist attacks from both conventional computers and sufficiently capable quantum computers. For CIOs, the immediate concern is especially public-key cryptography: it is embedded in protocols, applications, infrastructure, certificates, and supplier products, so preparing for PQC is an enterprise migration—not simply an algorithm purchase.
As an Amazon Associate I earn from qualifying purchases.
The risk is not that every kind of encryption or every stored record becomes readable at once. The relevant concern is that quantum computing could undermine public-key mechanisms on which systems rely. The scope and timing of any impact depend on the cryptographic use and the system involved.
Why data can be at risk before a quantum computer arrives
“Harvest now, decrypt later” describes an attacker collecting encrypted information today in hopes of decrypting it in the future if a sufficiently capable quantum computer becomes available. That possibility matters most for information whose confidentiality must last a long time. It does not mean that collected records can currently be decrypted this way, or that a particular quantum computer has already demonstrated the capability.
#1 Best Overall
When will a cryptanalytically relevant quantum computer exist?
No firm arrival date is established. NIST’s FAQ, updated June 30, 2026, reports widely varying estimates: some anticipate such a computer by 2030, many place it 15–20 years away, and others believe it could take more than 30 years. These ranges illustrate uncertainty; they are not a consensus forecast or a dependable deadline for enterprise planning.
That uncertainty is not a reason to wait. The relevant planning question is whether data, systems, and dependencies will still matter if quantum capabilities arrive sooner than expected—and how long the organization would need to change them. A migration that begins with discovery and testing can be paced according to risk rather than triggered by a prediction.
Rank #2
Which post-quantum standards are ready?
NIST finalized three standards in 2024 and says they are ready to implement. They cover different cryptographic functions, so an organization should map each standard to its actual use rather than treating the names as interchangeable.
| Standard | Function | Status |
|---|---|---|
| ML-KEM (FIPS 203) | Key establishment | Finalized by NIST in 2024; ready for implementation |
| ML-DSA (FIPS 204) | Digital signatures | Finalized by NIST in 2024; ready for implementation |
| SLH-DSA (FIPS 205) | Digital signatures | Finalized by NIST in 2024; ready for implementation |
Distinguish these finalized standards from algorithms still under consideration and from vendor-specific proposals. NIST’s current program page notes that HAWK, a candidate, was withdrawn in July 2026 after a reported vulnerability; NIST says that withdrawal does not affect the three finalized standards. Candidate status can change, which is why standards tracking belongs in the program.
What should a CIO inventory first?
Begin with uses of public-key cryptography and the people, systems, data, and suppliers connected to them. NIST’s migration work emphasizes cryptographic visibility and risk management; a useful inventory records not just an algorithm name but its purpose and replacement constraints.
- Protocols, applications, infrastructure, and products that use public-key cryptography; record the algorithm and protocol where known.
- The use of each cryptographic component, such as key establishment or digital signatures, and the systems that depend on it.
- System, application, and business owners; data sensitivity and how long confidentiality must be maintained.
- External dependencies, including vendors, counterparties, certificates, and integration points that could constrain a change.
- Upgrade paths, hardware or software dependencies, operational constraints, and the effort or lead time required to replace components.
Make the inventory a governed asset rather than a one-time spreadsheet. Assign owners to unresolved entries and establish how teams will update it as systems and supplier products change.
Rank #4
How should the enterprise prioritize and migrate?
A cross-functional roadmap is more useful than a standalone security project. NIST’s migration guidance and the joint CISA, NSA, and NIST factsheet emphasize readiness planning, inventory, risk assessment, and vendor engagement. The sequence below turns those priorities into a manageable program.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Set governance and scope. Name an executive sponsor, technical owner, and decision-making group. Include security architecture, infrastructure, application teams, procurement, and relevant legal, privacy, and business owners—especially those responsible for long-lived sensitive data.
- Discover and record cryptographic dependencies. Identify public-key uses, their purpose, owners, suppliers, and replacement constraints. Track unknowns rather than treating missing inventory data as evidence that a system is out of scope.
- Rank risk and migration effort. Consider data sensitivity and confidentiality lifetime, exposure to collection, system criticality and lifespan, external dependencies, and the difficulty of upgrading. NIST’s stated transition approach has high-risk systems moving earlier than the outer 2035 horizon.
- Engage suppliers and counterparties. Ask for support plans, the standards and protocol versions they intend to support, rollout timing, upgrade mechanisms, interoperability evidence, performance results, and how they will manage future algorithm changes. Record dependencies that could delay a complete end-to-end transition.
- Test representative systems before broad deployment. Benchmark protocols, certificates, endpoints, network traffic, latency, memory, hardware, and integrations in the organization’s own environment. NIST’s migration project explicitly includes interoperability and benchmarking; there is no single performance outcome established for every deployment.
- Fund phased work and operational safeguards. Convert priorities into budgets, supplier milestones, deployment increments, monitoring, and rollback plans. Define how teams will verify successful operation and respond if an upgrade disrupts a dependent service.
What does the 2035 transition timeline mean?
NIST’s current program page identifies 2035 as the horizon for deprecating and ultimately removing quantum-vulnerable algorithms from NIST standards, with high-risk systems transitioning earlier. It is a standards-transition horizon—not a safe date to begin discovery, nor evidence that every private organization faces the same binding deadline.
NIST’s IR 8547, published November 12, 2024, is an Initial Public Draft describing NIST’s expected approach; its comment period closed January 10, 2025. It should not be presented as final guidance. For detailed algorithm-specific dates or procurement requirements, use the latest NIST publications rather than assuming the draft settles them. The historical 2035 goal also appeared in U.S. policy context following the May 2022 White House memorandum; current transition planning should be based on current NIST guidance.
How should leaders compare PQC implementations?
There is no universal winner for every enterprise use case. Evaluate the complete implementation and its operational fit, not just the algorithm label.
- Standards status and function: Confirm whether the option implements a finalized NIST standard, and whether it supports the required function—key establishment or digital signatures.
- Interoperability: Verify that protocols, certificates, endpoints, and counterparties work together in the actual deployment.
- Performance and resource demands: Measure throughput, latency, memory, network overhead, hardware support, and operational effects under relevant conditions.
- Supplier readiness: Establish supported versions, delivery dates, upgrade mechanisms, and dependencies, and request evidence rather than relying on broad readiness claims.
- Operational maturity and agility: Assess monitoring, rollback, and the ability to replace algorithms without disruptive redesign.
Why crypto agility belongs in the plan
NIST defines cryptographic agility as the capability to replace and adapt algorithms across protocols, applications, software, hardware, firmware, and infrastructure while preserving security and operations. In practice, that means designing governed configuration and upgrade paths so algorithm changes can be managed deliberately instead of requiring brittle assumptions or widespread redesign. Treat agility as an architectural and operational capability with owners and change controls, not as a promise that future upgrades will be effortless.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →What CIOs should do next
Authorize a cross-functional readiness roadmap, start a public-key cryptography inventory, and rank systems by data lifetime, risk, and migration difficulty. In parallel, ask key suppliers for standards support and upgrade plans, then test interoperability and performance on representative systems. Use the findings to fund phased migration and build changeable cryptographic architecture; revisit priorities as official standards and transition guidance evolve.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
