NIST published the final version of Internal Report 8547 on October 27, turning the federal transition to post-quantum cryptography into a dated migration program. The roadmap identifies vulnerable standards, points to their replacements, and gives agencies and technology providers a timetable for changing the cryptography already embedded in working systems.
What changed
The broad federal target remains 2035, the completion year set by National Security Memorandum 10. Executive Order 14412 adds earlier milestones for federal high-value assets and high-impact systems: key establishment must move by 2030, followed by digital signatures in 2031.
Those dates do not automatically become legal deadlines for every private organization. They still matter beyond government because agencies depend on commercial products, cloud services, contractors, open-source components, and standards bodies. A federal system cannot complete its migration if a necessary product or protocol has no supported replacement path.
Why it matters
The first practical task is finding where vulnerable cryptography lives. An organization may know which algorithms appear in a current application while missing certificates, libraries, hardware modules, archived signatures, vendor-managed services, and older systems that rarely enter the normal upgrade cycle. NIST explicitly includes the cryptographic supply chain in the transition problem.
That changes the meaning of quantum readiness. Choosing a replacement standard is one decision. Building a usable inventory reveals the sequence of products, vendors, contracts, tests, and data protections that must change around it. The inventory also exposes dependencies whose timing belongs to someone else.
Long-lived sensitive data belongs near the front of the queue. NIST cites the harvest-now-decrypt-later threat, in which encrypted material collected today could be held for later decryption if capable quantum hardware emerges. For data that must remain confidential for years, the relevant deadline is shaped by its required secrecy period as well as the date when a vulnerable system is finally replaced. NIST points to FIPS 203 key establishment as a priority for this risk.
Verification bottleneck
An inventory is useful only if it can answer operational questions. Which systems use a vulnerable algorithm? Who owns each replacement? Does a vendor support the new standard? Can the change be tested without breaking interoperability? What long-lived data crosses the affected channel?
Hybrid deployments that combine conventional and post-quantum cryptography can reduce dependence on a single approach during transition. NIST also notes that hybrids require additional computational resources. That trade-off needs evidence from the actual system rather than a blanket policy.
Watch next
Watch for federal procurement language, vendor roadmaps, and application-specific NIST guidance that convert the high-level timetable into product requirements. The strongest readiness signal will be a maintained inventory tied to owners, replacement paths, and test results. A policy that says “post-quantum ready” without those links leaves the migration dependent on unseen infrastructure.
Sources
- NIST IR 8547, final, October 27, 2026
- NIST release
- DOI: 10.6028/NIST.IR.8547
