The 2026–2030 Squeeze: 14 Deadlines in 48 Months

The enterprise PQC migration study estimates that large organizations need 12 to 15+ years to complete a full PQC migration. That number accounts for cryptographic inventory, vendor assessment, procurement cycles, testing, deployment, validation, and the organizational friction that slows any infrastructure-wide change.

Hold that estimate in one hand. In the other, hold this: between January 2026 and December 2030, I count at least 14 distinct PQC milestones set by 10 different jurisdictions and organizations. Most are planning or migration deadlines. Several are binding. A few carry market-access consequences for non-compliance.

The gap between “you need 12 years” and “your first deadline is in months” is the defining tension of PQC migration in 2026. And unlike the outer 2035 boundary where most jurisdictions converge, these intermediate milestones are staggered, overlapping, and aimed at different scopes. You can’t satisfy them by picking one date and working backward from it. You have to track them all.

Here’s every one of them, in chronological order, with what each requires and who it affects.

2026: The Planning Year

January 2026 — Bank of Israel Directive 202501

Who it affects: Every banking corporation and licensed financial service provider in Israel.

What it requires: A board-approved quantum preparedness plan submitted to the Banking Supervision Department’s Head of Technology, Innovation, and Cyber Division. The plan must include a mapping of computing and communications infrastructure, identification of systems vulnerable to quantum cryptanalysis, damage assessment, and a response plan. The board must discuss and approve the plan before submission.

Enforcement: Supervisory directive under Directive 364 (IT risk management). Non-submission is a supervisory compliance failure, not an abstract risk.

Why it matters beyond Israel: This is one of the first binding financial-sector PQC directives globally. If you’re a multinational bank with Israeli operations, the one-year clock already ran out.

April 2026 — Canada CCCS ITSM.40.001

Who it affects: Government of Canada departments and agencies (non-classified systems).

What it requires: An initial departmental PQC migration plan, with annual reporting on progress starting from this date. The CCCS roadmap sets this as the first of three milestones (planning by April 2026, high-priority migration by end of 2031, full migration by end of 2035).

Enforcement: Binding for federal departments. The Treasury Board SPIN and ITSM.00.501 procurement playbook add procurement teeth: dated, auditable PQC requirements are entering government contract language.

September 21, 2026 — FIPS 140-2 Sunset

Who it affects: Every organization that sells cryptographic products to the US federal government or uses FIPS-validated modules in regulated environments.

What it requires: All FIPS 140-2 certificates move to Historical status. New FIPS 140-3 validated modules are required for federal procurement. Organizations that need to renew or obtain validation after this date must submit FIPS 140-3 capable modules.

Enforcement: Binding for federal procurement. No FIPS 140-2 validation means no sale to the US government.

Why it matters for PQC: The FIPS 140-2 sunset is not a PQC deadline per se, but it forces a cryptographic module refresh cycle at the exact moment organizations should be planning their PQC migration. The smart play is to combine the two: if you’re upgrading your cryptographic module for FIPS 140-3 validation anyway, build PQC algorithm support into the same upgrade cycle rather than touching the module twice.

~2026 — UAE National Encryption Policy

Who it affects: UAE government entities (scope may extend to critical infrastructure operators).

What it requires: Officially approved transition plans from classical encryption to PQC. Automated cryptographic inventory. Crypto-agility by design for new systems. Prioritization based on HNDL exposure for data with 10–20 year confidentiality lifetimes.

Enforcement: Binding executive regulation, not advisory guidance. Among the first countries to cross the line from recommendation to requirement.

End of 2026 — EU NIS Cooperation Group Phase 1

Who it affects: EU Member States and, through them, operators of essential services and critical infrastructure across the EU.

What it requires: National PQC strategies published, cryptographic inventories begun, pilot projects launched for high and medium-risk use cases. The coordinated roadmap expects Member States to have institutional structures and initial plans in place by this date.

Enforcement: Coordinated guidance, not directly binding on enterprises. But this is the phase where the NIS2 implementing acts and DORA will begin flowing PQC requirements into regulated-sector compliance. For financial institutions in the EU, the practical pressure starts here.

End of 2026 — Australia ASD Planning Milestone

Who it affects: Australian government agencies and critical infrastructure operators.

What it requires: A refined PQC transition plan. The ASD ISM guidance treats this as the last acceptable date for having a plan in place before active migration begins.

Enforcement: Authoritative guidance. ASD’s ISM controls are de facto mandatory for government agencies and increasingly referenced in critical infrastructure regulation.

2027: The First Hard Gate

January 1, 2027 — CNSA 2.0 Acquisition Gate

Who it affects: Every vendor selling products or services into US National Security Systems. Every defense contractor. Every technology company in the NSS supply chain.

What it requires: All new NSS acquisitions must be CNSA 2.0 compliant. Products that do not support ML-KEM-1024, ML-DSA-87, or AES-256 (among other requirements) cannot be purchased for NSS.

Enforcement: Procurement gate. This is the sharpest PQC enforcement mechanism in the West. You don’t get fined for non-compliance. You get excluded from the market.

Why this is the anchor: The 2027 acquisition gate is the first deadline where non-compliance has immediate, measurable financial consequences. It will also set a precedent. If enforcement is strict, it sends a signal that accelerates timelines everywhere. If waivers are routine, it signals that deadlines are aspirational. I examine this dynamic in Who Actually Enforces PQC Deadlines?

~2027 — EU Cyber Resilience Act Full Compliance

Who it affects: Manufacturers of any product with digital elements sold on the EU market.

What it requires: Products must support cryptographic updates throughout their expected lifecycle. A product that ships with hardcoded RSA and no update mechanism for future algorithm changes fails the regulation. I analyzed the PQC implications in detail: the CRA mandates crypto-agility by law.

Enforcement: EU product-market-access regulation. Non-compliant products cannot carry the CE marking required for EU market access.

2027–2029 — India CII Migration Window

Who it affects: Critical Information Infrastructure operators in India.

What it requires: Migration to quantum-safe cryptography for CII during this window. India’s quantum-safe roadmap established PQC testing labs by 2026 and targets CII migration in the 2027–2029 period.

Enforcement: Authoritative guidance under the National Quantum Mission. India’s CII protection framework (IT Act Section 70) provides the regulatory backbone.

2028: The Mid-Point

End of 2028 — Australia ASD Critical Systems Migration

Who it affects: Australian government and critical infrastructure operators.

What it requires: Active transition of critical systems to pure PQC (ML-KEM-1024, no hybrid). This is not a planning date. This is the date by which critical systems should be actively migrating.

Enforcement: Authoritative guidance with increasing regulatory weight. Two years remain before ASD’s 2030 disallowance date.

End of 2028 — UK NCSC Phase 1

Who it affects: All UK organizations handling sensitive data or operating critical services.

What it requires: Phase 1 complete: full discovery of cryptographic dependencies, complete inventory, migration strategy defined.

Enforcement: Authoritative guidance. Not statutorily binding, but UK sector regulators (FCA, PRA, Ofcom) will use NCSC timelines as the benchmark for “reasonable” cybersecurity practice.

2030: The Convergence Point

The year 2030 is where the global timeline picture gets crowded. Five major milestones cluster in a single 12-month window.

January 2030 — EO 14144 TLS 1.3

Who it affects: All US federal systems.

What it requires: TLS 1.3 (or its successor) across all federal systems. EO 14144 focuses on protocol modernization, and TLS 1.3 is the vehicle through which PQC key exchange (via hybrid or pure modes) enters the federal network stack.

2030 — NIST IR 8547 Deprecation + CNSA 2.0 Exclusive Use

Who it affects: US federal agencies (IR 8547) and NSS (CNSA 2.0).

What it requires: NIST IR 8547 deprecates all 112-bit quantum-vulnerable algorithms (RSA-2048, ECC P-256). CNSA 2.0 simultaneously requires exclusive use of PQC algorithms for networking equipment and firmware signing across NSS. The hybrid transition window closes for these categories.

End of 2030 — EU Phase 2 + Germany BSI KRITIS

Who it affects: Critical infrastructure operators across the EU (Phase 2) and specifically in Germany (BSI KRITIS).

What it requires: The EU coordinated roadmap’s Phase 2 expects high-risk use cases and critical infrastructure migrated to PQC. Germany’s BSI sets the same date for KRITIS-regulated entities, with mandatory hybrid mode and an algorithm list that includes FrodoKEM and Classic McEliece.

End of 2030 — Australia Full Classical Disallowance

Who it affects: Australian government and critical infrastructure.

What it requires: Cease use of traditional asymmetric cryptography entirely. This is the most aggressive PQC deadline among major Western allies: full stop, no classical public-key crypto, pure PQC only. Five years ahead of the US/UK/EU 2035 outer boundary.

The Arithmetic Problem

Fourteen milestones across 48 months sounds manageable in the abstract. The problem is that most of them require work that should have started years ago.

The enterprise migration study’s 12–15 year estimate covers end-to-end completion, but the initial phases (inventory, risk assessment, strategy development) consume 18–24 months on their own. An organization that starts its cryptographic inventory in mid-2026 will have its migration plan ready by late 2027 or early 2028, at best. By that point, the Bank of Israel and Canada deadlines have already passed. The CNSA 2.0 acquisition gate has been enforced for a year. The EU CRA is in effect. The organization has missed the planning deadlines and is still planning.

The organizations that will meet the 2030 cluster of deadlines started their PQC programs in 2024 or 2025. If you’re reading this in mid-2026 and haven’t started, you’re not in a hopeless position, but you need to accept two things. First, you will miss some of the planning deadlines. Document why, build a credible catch-up plan, and show regulators forward motion rather than excuses. Second, you need to compress your timeline through aggressive automation of cryptographic discovery (CISA’s guidance on automated inventory is the reference) and by leveraging production-ready PQC implementations (OpenSSL 3.5 ships hybrid PQC by default) rather than waiting for further standards maturation.

The PQC Migration Framework at pqcframework.com provides the structured methodology for managing this. But no framework can give you back the time that’s already passed. The 2026–2030 window is closing, and the density of deadlines within it means that every quarter of delay puts you further behind not one deadline but several.

As I’ve argued before, the reason to act now is not a prediction about when a quantum computer will break RSA. The reason to act is that the regulatory, procurement, and market-access deadlines are already set, they’re arriving faster than most organizations can move, and the next 48 months hold more of them than the decade that follows.