.png){kind=small}
The Quantum Deadline Is Coming: Are Other Countries Moving Faster Than the United States?
Oct 13, 2026
The United States wrote the world's post-quantum algorithms. For most of the past two years, other governments were quicker to attach dates to them: Canada bound its departments and contracts, Australia set 2030, and Singapore and India aimed critical infrastructure at 2031 and 2029. In June 2026, Washington answered with the hardest federal deadline of any large economy.
The result is not a simple "others are ahead" story. It is a split. Governments everywhere now have dates for themselves; almost none have imposed enforceable dates on their private sectors. That leaves U.S. companies outside federal supply chains with standards but no schedule, and makes it likely that their first binding post-quantum requirement arrives from a foreign regulator, a foreign government buyer, a global bank or a federal prime contractor rather than from a U.S. sector regulator.
This article tests that thesis against primary sources, labels each requirement as mandatory, announced, proposed, recommended or anticipated, and sets out what leaders should do in the next 12 months.
Why a 2030 deadline is really a 2026 deadline
"Harvest now, decrypt later" turns every PQC date into a date that has already partly passed. Data encrypted today with RSA or elliptic-curve key exchange can be captured and stored, then decrypted once a cryptographically relevant quantum computer exists. The U.S. government now says this plainly: Executive Order 14412 opens by warning that adversaries may be collecting U.S. information now to decrypt it later.
The practical consequence is captured by Mosca's inequality. If the years your data must stay confidential, plus the years your migration will take, exceed the years until a capable quantum computer arrives, you are already exposed.
{shelf life} + {migration time} > (time to a relevant quantum computer} = {exposure today}
Two things follow for executives. First, a regulator's "complete by 2030" date protects new traffic only from 2030 onward; records with a 10 or 20-year confidentiality horizon, health data, account histories, identity records, trade secrets, diplomatic and defense material, need their key exchange moved much earlier. Second, signatures behave differently. Forged signatures are a future-only risk, which is why most roadmaps, including the U.S. order, give authentication a later date than key establishment. The meaningful deadline for confidentiality is therefore the earliest date your most long-lived data starts flowing over quantum-safe channels, not the date on a regulator's slide.
United States: from standards-setter to deadline-setter — for the government
Until June 2026, the fairest description of the U.S. was "world-class standards, federal-only obligations, long horizons." That changed on June 22, 2026, but only for part of the economy.
The standards layer (voluntary for the private sector). NIST published FIPS 203 (ML-KEM), FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) in August 2024, and its draft NIST IR 8547 proposes deprecating 112-bit RSA and elliptic-curve algorithms after 2030 and disallowing them after 2035. IR 8547 is still a draft, and FIPS bind federal systems, not private companies. Status: published standards; transition dates proposed.
The national-security layer (mandatory, NSS only). NSA's CNSA 2.0 requires national security systems to prefer quantum-resistant algorithms in most categories from 2025, use them exclusively in software signing and networking equipment by 2030 and in browsers, cloud services and operating systems by 2033, with full NSS transition by 2035. These requirements reach private firms only as vendors to NSS. Status: mandatory for NSS.
The federal civilian layer (now mandatory, with dates). The 2022 Quantum Computing Cybersecurity Preparedness Act and OMB M-23-02 required inventories and planning but set no completion date. Executive Order 14412 (June 22, 2026) changed that. It directs agencies to move all high value assets and high-impact systems to PQC for key establishment by December 31, 2030, and for digital signatures by December 31, 2031. OMB M-26-15, issued two days later, requires each civilian agency to submit a migration plan within 120 days - that is, this month - and lays out a phased schedule ending in full migration by 2035. Status: mandatory for federal civilian agencies.
The bridge to the private sector (proposed). Section 6(c) of the order directs the FAR Council to publish, within 180 days, a proposed rule requiring covered federal contractors to comply with NIST FIPS, including the PQC standards, by December 31, 2030. The order also directs CISA and NIST to publish minimum elements for a cryptographic bill of materials within 270 days, and tells Sector Risk Management Agencies to help critical-infrastructure operators develop migration plans. Help is not a mandate. Status: contractor rule announced, not yet proposed as of this writing; critical-infrastructure support is voluntary.
Sector regulators (general, not PQC-specific). No U.S. banking, securities, health or telecom regulator has published a PQC migration deadline. Obligations arrive indirectly, through general requirements to maintain current encryption and manage technology risk, such as the NYDFS cybersecurity regulation, the FFIEC handbooks and the HIPAA Security Rule.
The bottom line: a U.S. company that does not sell to the federal government still has no PQC deadline. A U.S. company that does will likely face one dated 2030.
Europe, the UK, Canada and Australia: dates first, mandates second
Outside the U.S., the common pattern is clear dates aimed at government and critical infrastructure, carried to the private sector by existing risk-management law rather than by a PQC statute.
European Union — directed, moving toward law. The Coordinated Implementation Roadmap published by the NIS Cooperation Group in June 2025 asks Member States to start transitioning and have national plans by the end of 2026, complete high-risk use cases — including critical infrastructure — by the end of 2030, and finish as much as feasible by 2035. It is a Member State commitment, not directly binding on companies. Two legal hooks give it reach. NIS2 Article 21 already requires essential and important entities to maintain cryptography policies, and the Commission's January 2026 proposal to amend NIS2 (COM(2026) 13) would add an explicit requirement for national PQC transition policies. For banks and insurers, the DORA technical standards on ICT risk management (Delegated Regulation 2024/1774) already require firms to update cryptographic technology in light of cryptanalytic developments, including quantum advances. Status: roadmap dates recommended; NIS2 amendment proposed; DORA obligation in force but without a PQC date.
United Kingdom — guided, with the clearest national timetable. The NCSC's migration timelines (March 2025) ask organisations to complete discovery and an initial plan by 2028, finish highest-priority migrations by 2031, and complete migration by 2035. They are aimed at large organisations, critical national infrastructure operators and regulators, and expect finance and telecoms to move earlier. No UK statute or regulator makes them binding. Status: recommended.
Canada — directed, and the most procedurally concrete. The Cyber Centre's roadmap (ITSM.40.001) was turned into policy by a Treasury Board Security Policy Implementation Notice, effective October 9, 2025. Departments had to file migration plans by April 1, 2026, and every federal contract with a digital component signed after that date must include PQC, validated-module and crypto-agility clauses. Inventories are due by April 2028, high-priority systems migrate by the end of 2031 and the rest by 2035, with Treasury Board compliance monitoring. Status: mandatory for federal institutions; reaches vendors through procurement now.
Australia — directed, and the most aggressive date. ASD's Information Security Manual guidance calls for ceasing traditional asymmetric cryptography — RSA, Diffie-Hellman, ECDH, ECDSA — by the end of 2030, five years ahead of most peers, with a refined plan by the end of 2026 and transition under way by 2028. For Commonwealth entities the ISM is the expected control baseline; for everyone else it is advice. Status: recommended, with government expected to comply.
Financial regulators in all four jurisdictions are converging on the G7 Cyber Expert Group roadmap of January 2026, which the U.S. Treasury co-chaired. It is explicitly non-binding, and it points to 2030–2032 for critical financial systems and 2035 for the sector as a whole.
Asia-Pacific: the earliest dates for critical infrastructure and finance
The most compressed timelines anywhere now sit in Asia, and they target the private operators of critical infrastructure and financial institutions directly.
Singapore — directed, the most aggressive critical-infrastructure dates. The Cyber Security Agency's Quantum-Safe Migration Handbook (July 16, 2026, with GovTech and IMDA) sets out what CSA calls requirements for Critical Information Infrastructure owners. CII owners are to submit migration plans by March 31, 2027. From January 1, 2028, newly procured CII systems should support quantum-safe algorithms or be quantum-safe ready, and migration should be complete by the end of 2031. The Handbook itself says it is not mandatory, and binding force under the Cybersecurity Act would need a code of practice or a Commissioner's direction; CII owners should nonetheless treat the dates as supervisory expectations. Separately, the Monetary Authority of Singapore said in its 2025/26 Annual Report that it will issue supervisory expectations guiding financial institutions' phased migration toward quantum resilience, with the aim of reaching it before the end of this decade. Those expectations had not been published as of this writing. Status: CII dates announced; MAS expectations anticipated.
South Korea — directed, on a 2035 horizon. Korea's 2023 national PQC Master Plan targets transition of the national cryptographic system by 2035, and the KpqC competition selected four domestic algorithms in January 2025, running alongside NIST's. The Ministry of Science and ICT expanded its pilot conversions in May 2026 to telecoms, finance, transport, defense and space. These are government programs and pilots, not obligations on operators. Multinationals should watch for a dual-algorithm requirement in Korean public procurement. Status: government target; no private-sector mandate.
Japan — directed for government, guided for industry. The National Cyber Command Office's November 2025 interim report set 2035 as the target for government agencies to migrate, with a detailed roadmap due during fiscal 2026 (report coverage). The Financial Services Agency's 2024 study group asked deposit-taking institutions to begin preparing, but set no deadline. Status: government target announced; finance guided.
The pattern in the region is telling. Where governments set dates for private operators, Singapore's CII owners, India's CII sectors, MAS-supervised banks, the dates cluster in 2029–2031, earlier than the 2035 endpoint common in the West.
India: the most ambitious dates, not yet the strongest mandates
India has published the earliest national PQC dates of any major economy, but as of October 2026 they are recommendations awaiting sector regulators to make them binding.
Why the stakes are unusually high. Few countries run so much of daily life on a small number of national cryptographic trust anchors. UPI processed 24.07 billion transactions in September 2026 alone (NPCI data), across more than 700 banks. Aadhaar authentication, the DigiLocker and eSign stack, bank and card networks, and telecom subscriber systems all depend on public-key cryptography concentrated in a few PKI hierarchies, HSM estates and switching platforms. A compromised root or signing key in that architecture is a national-scale event, and identity and financial records carry decades-long confidentiality horizons — exactly the profile harvest-now-decrypt-later targets.
Research funding is not a mandate. The National Quantum Mission, approved in 2023 with an outlay of about ₹6,000 crore through 2030–31, funds quantum computing, communication, sensing and materials. It creates no obligation on any bank, telecom operator or ministry to change its cryptography.
The national roadmap (recommended). Under the NQM's governance, a DST Task Force , with sub-groups led by DoT's Telecommunication Engineering Centre and the Data Security Council of India, published Quantum-Safe Ecosystem in India: Roadmap to Quantum Resiliency in May 2026, after a February draft. For CII sectors including defense, power, telecom, transport and banking and finance, it proposes foundations by December 2027, high-priority migration by December 2028 and full PQC adoption by December 2029, with enterprises following by 2033. It also proposes national testing labs under TEC, STQC and BIS, crypto-agile PKI, and cryptographic bills of materials in procurement from FY 2027–28. These are Task Force recommendations to government, not regulations. Status: recommended timelines.
CERT-In and MeitY (guidance). CERT-In's Technical Guidelines on SBOM, QBOM & CBOM, AIBOM and HBOM (version 2.0, July 2025) define minimum elements for a cryptographic bill of materials and a quantum-readiness strategy. They are best-practice guidance, not binding directions. Status: recommended.
RBI and financial services (anticipated). On May 25, 2026, the Reserve Bank of India constituted the Q-SAFE expert committee, including NPCI, SBI, MeitY, DST and DSCI, to assess the sector's cryptographic inventory through a CBOM, evaluate crypto-agility and vendor readiness, and recommend a roadmap to quantum-secure the financial system. Its report is due six months after its first meeting, so late 2026 or early 2027. The earlier Reserve Bank Innovation Hub white paper (December 2024) urged banks to begin transitioning but states that it does not represent RBI's views. No RBI, SEBI, IRDAI or PFRDA instrument yet sets a PQC deadline; SEBI's 2024 Cybersecurity and Cyber Resilience Framework requires software bills of materials but not PQC migration. Status: RBI roadmap anticipated.
Telecom and critical infrastructure (no published directive). TEC co-led the Task Force and is slated to host testing labs, but neither DoT, TRAI nor NCIIPC has published a binding PQC migration requirement for operators or protected systems that we could find.
Pressure from several directions. An Indian bank, IT-services firm or payments processor serving global clients may face PQC expectations from the EU through DORA and NIS2 supply-chain clauses, from U.S. federal flow-down once the FAR rule lands, from MAS if it operates in Singapore, and from global banking partners following the G7 roadmap, possibly before RBI acts. For India's IT-services exporters, that external pull is likely to arrive first.
Could India's regulators ultimately move faster than U.S. ones? The structural case is strong: a central bank that also oversees the national payments utility, a 2029 national target already on paper, and an RBI committee explicitly tasked with writing a roadmap. The U.S. has no single financial regulator able to set a sector-wide PQC date. But until RBI or CERT-In converts the Task Force dates into directions, India is best classified as directed on paper and guided in force.
The global PQC timeline
No jurisdiction has yet imposed a broad, enforceable PQC deadline on its private sector; the firm mandates bind governments and reach companies through procurement.
Country/Region | Requirement or guidance | Who it applies to | Key PQC dates | Mandatory? | Body |
United States | Federal civilian HVAs and high-impact systems | Plans Oct 2026; key establishment 2030; signatures 2031; full 2035 | Mandatory (federal) | White House, OMB, ONCD | |
United States | EO 14412 §6(c) FAR rule | Covered federal contractors | Comply with PQC FIPS by Dec 31, 2030 | Announced; rule not yet proposed | FAR Council |
United States | National security systems and vendors | Exclusive use 2030–2033 by category; all NSS 2035 | Mandatory (NSS) | NSA | |
United States | Federal systems; de facto industry baseline | RSA/ECC deprecated after 2030, disallowed after 2035 | Proposed | NIST | |
Canada | Federal departments; vendors via contract clauses | Plans and PQC contract clauses Apr 2026; inventory 2028; high-priority 2031; all 2035 | Mandatory (federal) | Treasury Board, Cyber Centre | |
Australia | Government entities; recommended for all | Plan 2026; transition from 2028; cease traditional asymmetric crypto end-2030 | Recommended; expected of government | ASD/ACSC | |
Singapore | CII owners | Plans Mar 31, 2027; new systems quantum-safe from Jan 2028; complete end-2031 | Announced as requirements; Handbook non-binding | CSA | |
Singapore | Financial institutions | Quantum resilience before 2030 | Anticipated | MAS | |
India | CII incl. BFSI and telecom; enterprises | CII foundations 2027, priority 2028, full 2029; enterprise 2033 | Recommended | DST / NQM Task Force | |
India | Financial system | Roadmap due ~6 months after first meeting | Anticipated | RBI | |
European Union | Member States; critical infrastructure | Start by end-2026; high-risk by end-2030; feasible by 2035 | Recommended; NIS2 amendment proposed | Commission, NIS Cooperation Group | |
EU (finance) | Financial entities | No PQC date; must track quantum threats to cryptography | Mandatory (general obligation) | ESAs, national supervisors | |
United Kingdom | Large organisations, CNI, regulators | Discovery 2028; priority 2031; complete 2035 | Recommended | NCSC | |
Japan | NCO interim report | Government agencies | Full migration 2035; roadmap FY2026 | Government target | National Cyber Command Office |
South Korea | PQC Master Plan | National cryptographic system | Full transition 2035 | Government target | MSIT, NIS |
G7 finance | Financial sector | Critical systems 2030–2032; sector 2035 | Non-binding | G7 Cyber Expert Group |
Mandated, Directed or Guided
Mandated — United States (federal) and Canada (federal). Both governments have bound their own agencies to dated migrations with compliance oversight. Canada has gone a step further in practice: since April 1, 2026, its new digital contracts must carry PQC clauses. The U.S. ties federal contractors to a 2030 date, but only once the FAR rule is proposed and finalized. Neither binds the private sector at large.
Directed — European Union, Australia, Singapore, India, Japan, South Korea. Each has explicit dates set by a government or regulator, but they apply mainly to government or critical infrastructure, or have not yet been made enforceable. Singapore and Australia have the earliest dates (2031 for CII, 2030); the EU has the strongest legal hooks through NIS2 and DORA; India's 2029 CII target is the most ambitious but the least enforced.
Guided — United Kingdom, and the U.S. private sector. The UK's dates are clear but voluntary, with sector regulators expected to carry them. U.S. companies outside federal supply chains face standards, not schedules.
The U.S. mandate gap — and where the first deadline will come from
The U.S. private sector does face a mandate gap: the standards are final, the federal dates are firm, but a bank, hospital or manufacturer with no federal contract has no date it must meet. Sector regulators have not filled it, and Executive Order 14412 offers critical infrastructure assistance rather than obligations.
The first enforceable PQC date most U.S. companies meet is therefore likely to come from somewhere else:
A federal contract. The FAR rule would turn December 31, 2030 into a contract condition, and primes will push it to subcontractors.
A foreign regulator. A U.S. bank's EU subsidiary under DORA, a Singapore branch under forthcoming MAS expectations, or a U.S. vendor to Singapore CII procuring "quantum-safe ready" systems from January 2028.
A foreign government customer. Since April 2026, Canadian federal contracts with a digital component carry PQC clauses.
A large customer or counterparty. Global banks following the G7 roadmap are already adding PQC questions to vendor risk assessments.
This is where the thesis needs refining. The evidence supports the first half: the U.S. defined the algorithms, and Canada, Australia, Singapore and India set operational dates before Washington did. But since June 2026, the U.S. has the hardest dated federal mandate of any large economy, and its 2030 contractor clause, once finalized, will reach more companies worldwide than any foreign rule. The more accurate statement is that other governments moved first on critical infrastructure and finance, while the U.S. moved hardest on its own systems and supply chain. For U.S. multinationals, the second implication holds: their first binding PQC obligation may well arrive through a foreign regulator, a foreign government contract or a global bank's vendor questionnaire.
Why this is not an algorithm swap
Every roadmap above, from OMB to Singapore's Handbook to India's Task Force, starts with the same work: knowing where your cryptography is. Replacing RSA with ML-KEM is the easy part. Finding every place RSA lives, in libraries, HSMs, certificates, VPN concentrators, payment terminals, firmware signing, partner APIs and SaaS platforms you do not control, is the hard part.
Discover — scan code, binaries, network traffic and configurations for cryptographic use, including in third-party and cloud services.
Inventory — record it in a cryptographic bill of materials (CBOM): algorithm, key length, protocol, owner, data protected, vendor. CISA's forthcoming minimum CBOM elements, CERT-In's CBOM fields and Canada's 2028 inventory fields are converging on what regulators will ask to see.
Assess — rate each asset for harvest-now-decrypt-later exposure by data shelf life and network exposure.
Prioritize — key exchange on long-lived, internet-facing data first; then PKI and code signing; then long-lived hardware and OT.
Migrate — prefer hybrid classical-plus-PQC modes during transition, and build PQC requirements into every refresh and new contract.
Maintain — treat cryptographic posture as a continuously monitored control, not a project with an end date.
Three disciplines decide whether that sequence works. Crypto-agility, the ability to change algorithms by configuration rather than re-engineering, is the real objective, because PQC standards will keep evolving. PKI modernization is the long pole: new roots of trust, larger certificates and shorter lifetimes touch every system that authenticates. Supply-chain dependency is the largest unknown: most enterprises will migrate on their vendors' schedules, so vendor PQC roadmaps belong in contracts now.
Could you show a plan tomorrow?
The global picture is less a race than a convergence. Almost every government points to 2035 for completion, and the earlier dates, 2029 for India's critical infrastructure, 2030 for Australia and U.S. federal key exchange, 2031 for Singapore's CII, are aimed at the systems that matter most. The question for executives is not which country is fastest. It is this: if a regulator, a major customer or a government contract required your organization to demonstrate a credible post-quantum migration plan tomorrow, could you?
What leaders should do now
Name an owner and a budget. Appoint an accountable PQC migration lead reporting to the CIO or CISO, as the U.S. order requires of agencies, and fund discovery in the next budget cycle.
Build a first CBOM for your crown jewels within 12 months. Cover systems holding data that must stay confidential past 2035, plus your PKI, HSMs and code-signing.
Map your regulatory exposure by jurisdiction. List every regulator, government customer and critical-infrastructure designation you fall under, and the earliest PQC date among them — it may be Singapore, Canada or a federal contract, not your home regulator.
Write PQC into procurement now. Require vendor PQC roadmaps, crypto-agility and validated modules in new contracts and renewals, following the Canadian clause model.
Protect long-lived data first. Enable hybrid post-quantum key exchange on internet-facing and partner channels where vendors already support it, and report progress to the board as a standing resilience metric.
The deadline that matters is not the one on any government's roadmap. It is the date your most sensitive data started being harvested, which, for data with a long shelf life, may already be behind you.
Research current to October 13, 2026. Pending items to watch: the FAR proposed rule (due December 2026), CISA's CBOM guidance (due March 2027), MAS supervisory expectations and RBI's Q-SAFE report.
Comments