From Guidance to Law: PQC Deadlines Are Hardening
What the latest regulatory and standards developments mean for your migration timeline
PQC migration deadlines are hardening. Not everywhere at once, and not always in the ways that make headlines, but the pattern is unmistakable: what were suggestions are becoming requirements, what were draft timelines are being finalized, and what were voluntary frameworks are acquiring enforcement teeth.
India finalized a national roadmap with binding timelines for critical infrastructure. Canada passed enabling legislation that gives regulators the power to mandate quantum-safe cybersecurity. A reported draft U.S. executive order would set hard dates for federal agencies and their contractors. CNSA 2.0’s procurement gate for national security systems is now eight months away. NIST advanced nine additional signature candidates, reinforcing that the algorithm landscape will keep evolving. The G7 central banks published their first collective acknowledgment of the quantum threat to finance. And Google’s ECC-breaking quantum circuits were independently reproduced, removing the last uncertainty margin around the cryptanalytic resource estimates.
None of these alone rewrites a migration plan. Together, they confirm that organizations still planning to a 2035 horizon are planning to a deadline the rest of the world is abandoning. For the full picture of PQC regulatory and industry deadlines across jurisdictions, I maintain a comprehensive global PQC deadlines tracker on PostQuantum.com. What follows is my analysis of the developments that matter most for practitioners right now.
CNSA 2.0: Eight Months to the Procurement Gate
The nearest hard deadline is also the least discussed. On January 1, 2027, every new acquisition for a U.S. National Security System must support CNSA 2.0 algorithms. A system delivered the day after without ML-KEM-1024 key establishment and ML-DSA-87 digital signatures is non-compliant on arrival. No waiver queue. No grandfather clause. No transition period.
That gate does not arrive alone. On September 21, 2026, NIST moves all remaining FIPS 140-2 certificates to Historical status. On November 10, 2026, CMMC 2.0 Phase 2 begins mandatory third-party assessments for most Level 2 defense contractors. Three cryptographic compliance deadlines in five months, each assuming the previous one has been addressed.
The binding constraint is CMVP validation. Post-quantum algorithm implementations need FIPS 140-3 validation to be acceptable for federal use. The current CMVP process averages over 500 days from submission to active certificate. Organizations that entered the pipeline by late 2024 or early 2025 will have validated modules. Those that did not face a gap that no amount of urgency can compress. As I covered in The 2027 Procurement Gate, the defense industrial base is about to discover which vendors were paying attention and which were not.
India Finalizes Its Roadmap
India’s Department of Science and Technology published the final version of its national quantum-safe migration report under the National Quantum Mission. The core timelines from the draft are unchanged: Critical Information Infrastructure (defense, power, telecom, transport, BFSI) follows a 2027/2028/2029 accelerated track. Regular enterprises follow a 2028/2030/2033 schedule.
What changed in the final version is significant in three areas. First, Preferential Market Access provisions now direct both public and private organizations to prefer indigenously developed quantum-safe products. Second, the testing and certification framework specifies four assurance levels with granular test cases, including side-channel resistance with specific TVLA pass criteria. Third, CBOM submissions become mandatory starting FY 2027-28.
For multinationals operating in India, the Preferential Market Access provisions add a new variable to vendor strategy. For everyone, the mandatory CBOM requirement validates the Minimum Viable CBOM approach I have advocated: regulators are moving from “you should know your cryptography” to “prove that you do.”
U.S. Signals Hard Dates — but Hasn’t Set Them Yet
Nextgov/FCW reported on May 20 that the White House is circulating a draft executive order requiring federal agencies to migrate key establishment to PQC by December 31, 2030 and digital signatures by December 31, 2031. Covered contractors would face a 2030 deadline.
This has not been signed. It is a draft sourced to a single report, and the specific dates could shift or disappear entirely. But the signal matters because previous executive actions had been pulling in different directions. EO 14306 stripped some of the harder provisions from Biden-era guidance. Trump’s March 2026 cyber strategy named PQC as a modernization pillar but set no dates. If signed, the draft EO would fill that gap and extend hard deadlines to the federal contracting base, which is the single largest lever the U.S. government has over private-sector technology adoption.
I include it here not as a done deal but as a leading indicator of where U.S. federal policy is heading. Organizations that depend on federal contracts should be planning to the rumored 2030 timeline regardless, because by the time a signed order makes it official, the implementation window will already be too short for programs that haven’t started.
Canada Passes Enabling Legislation — Without Mentioning Quantum
Canada’s Bill C-8 passed the Senate on June 4, nearly identical to the Bill C-26 introduced in June 2022. Senator Mohamed-Iqbal Ravalia asked the only quantum-related question in the entire Senate debate. Senator McNair’s response: “There was no direct discussion at the committee level, but the bill is robust enough that the regulatory process can deal with issues around quantum computing.”
Bill C-8 does not set a PQC deadline. What it does is hand regulators the tools to set one later: mandatory cybersecurity programs, incident reporting, ministerial power to compel operators to harden systems, and penalties of up to $15 million per day. Enforceable PQC-specific regulations are 12 to 24 months away from Royal Assent, putting them at late 2027 to mid-2028 at the earliest. Canada’s Treasury Board SPIN procurement guidance, which went live April 1, 2026, is currently the sharpest PQC-adjacent lever in Canadian federal policy.
The gap between the legislative framework’s potential and its quantum-specific execution is striking. The full analysis is on PostQuantum.com.
Google’s ECC Circuits: Reproduced in Two Months
In March, Google Quantum AI published resource estimates showing ECC-256 could be broken with roughly 1,175 logical qubits and about 2.6 million Toffoli gates. The team hid the circuit designs behind zero-knowledge proofs, citing responsible disclosure.
In June, André Schrottenloher at Inria published independently constructed circuits that match Google’s results on qubits and beat them on gate count. Craig Gidney, the Google researcher who designed the original circuits, confirmed the match and conceded the ZKP approach failed.
The CRQC timeline is unchanged — breaking ECC with 1,175 logical qubits still requires hardware nobody has built. But the uncertainty margin around the resource estimates is gone. The circuits are now published and independently verified. Any future quantum hardware advance can be immediately assessed against a known, concrete cryptanalytic target. For migration programs, this tightens the connection between quantum hardware announcements and actual cryptanalytic risk: the goalposts are now fixed and visible.
NIST Advances Nine Additional Signature Candidates
NIST released NIST IR 8610, announcing that nine candidate algorithms advanced to the third round of its Additional Digital Signatures process. Five were eliminated. The survivors span four mathematical families, with only one (HAWK) lattice-based, and even HAWK rests on different assumptions than ML-DSA and FN-DSA.
NIST is building cryptographic insurance. If a breakthrough compromises the standard lattice problems underlying its primary signature standards, most of these candidates provide alternatives on entirely different foundations. For migration programs, the practical implication is that crypto-agility is not optional. Your architecture needs to accommodate algorithm changes that could come from either a lattice cryptanalysis surprise or a standards-body decision to deprecate or modify an existing standard.
The nine survivors include SQIsign (148-byte signatures, the most compact PQC scheme), UOV, MAYO, FAEST, and HAWK. Several of these produce signatures smaller than ML-DSA, which matters for constrained environments (IoT, DNSSEC, embedded OT systems) where ML-DSA’s 2,420-byte signatures are prohibitive. Organizations with significant OT/CNI deployments should track the compact signature candidates closely.
G7 Central Banks Acknowledge the Quantum Threat
The G7 central banks’ Quantum Technologies Working Group published its first report in May, with all eight G7 central banks collectively acknowledging the quantum threat to the financial system. The report follows the G7 Cyber Expert Group’s PQC migration roadmap (January 2026, targeting 2030 to 2035) but takes a wider lens, covering quantum computing applications and quantum sensing alongside cryptographic security.
For financial services CISOs, the G7 CEG roadmap’s 2030-2032 migration window for high-priority systems is the current benchmark. Combined with CNSA 2.0 (for firms with NSS-adjacent contracts), the EU’s NIS2/DORA timeline, and MAS/HKMA guidance in Asia-Pacific, financial institutions operating across jurisdictions face converging compliance expectations from multiple regulators simultaneously.
Migration Impact
If you are planning to a 2035 completion horizon, revisit that assumption. NIST’s draft guidance deprecates classical algorithms after 2030. Australia’s ASD recommends ceasing all traditional asymmetric cryptography by end of 2030. India targets CII migration by 2029. The rumored U.S. EO would set 2030/2031 for agencies. Even where hard deadlines have not yet been enacted, the direction and clustering of dates around 2028 to 2030 tells you where the finish line is moving. For the full current picture, see the global PQC deadlines tracker.
For defense contractors and NSS vendors, the January 2027 procurement gate is the immediate action item. Verify that your products support ML-KEM-1024 and ML-DSA-87. Confirm your CMVP validation status. If your cryptographic modules are not in the FIPS 140-3 validation pipeline, the January gate will close before your certificates arrive.
For multinationals, PQC standards fragmentation is now an operational planning variable. NIST selections dominate the Western world, but China’s ICCS process is actively evaluating submissions, South Korea’s KpqC winners are announced, and India’s Preferential Market Access provisions may shape vendor selection in the subcontinent. A migration plan that assumes a single global algorithm family is planning for a world that will not exist.
Bottom line: I have been arguing for years that debating Q-Day arrival dates is beside the point because regulators, vendors, and counterparties set their own deadlines. What I am seeing now is the next phase: guidance is becoming law, voluntary is becoming mandatory, and the dates are converging on 2028 to 2030. If your program timeline does not survive contact with that calendar, escalate now.
For the full and continuously updated landscape of PQC regulatory and industry deadlines, see the Global PQC Deadlines Tracker on PostQuantum.com.
The Applied Quantum PQC Migration Framework provides structured guidance for program planning, governance, and regulatory alignment across jurisdictions in Phase 0 (Executive Mandate) and Phase 4 (Roadmap & Governance).