Introduction: Preparing for a threat without a fixed date
Organizations typically work backward from a compliance date or known vulnerability. Y2Q, short for Years to Quantum, offers no such certainty. Y2Q refers to the point when a sufficiently capable quantum computer could threaten widely used public-key cryptography. The dilemma is that systems deployed today may still be in service when that advanced quantum computer emerges. So, how early should organizations prepare for a security risk when the timeline of the technology itself is uncertain?
What would make a quantum computer a cybersecurity threat?
Quantum computers could solve mathematical problems that support modern public-key cryptography. Current versions can’t crack these systems at the scale required for a practical attack. The real threat would come from a cryptographically relevant quantum computer (CRQC) capable of running attacks against widely used public-key cryptographic systems.
Unlike classical computers that use binary bits (0 or 1), quantum computers depend on qubits. Regular bits increase computing power linearly (1+1+1), while qubits increase power exponentially (multiplying by powers of 2). This enables qubits to process multiple even massive combinations of possibilities simultaneously.
As a result, quantum computers can solve certain problems faster than classical computers. In particular, the algorithm developed by American applied math professor and computer scientist at MIT Peter Shor in 1994 demonstrates how quantum computers can outperform traditional computers on real-world tasks. When allowed to run on a sufficiently capable quantum computer, Shor’s algorithm can solve math problems underpinning popular encryption, such as RSA and elliptic-curve cryptography. This has driven the global push toward new encryption standards that can withstand quantum attacks.
Why the Y2Q timeline remains uncertain
Y2K (Year 2000 problem) was a calendar transition, from 1999 to 2000. At that time, the public feared and prepared for a global disruption on computer systems, most of which were programmed to recognize and represent years with two digits. Critical sectors, such as banking and utilities, were concerned that computers would misinterpret “00” as “1900” instead of “2000.” Y2Q has no countdown clock. Several moving parts make it hard to predict.
Hardware progress and various architectural approaches
A single breakthrough in hardware or design can accelerate CRQC development. But with research labs and major tech entities pursuing different architectures and engineering methods, scaling quantum systems still involves significant engineering challenges.
Physical vs. logical qubits and error correction/fault tolerance
To operate, quantum hardware requires qubits. They are susceptible to errors caused by noise or heat. A quantum computer may require many physical or hardware qubits to create reliable logical qubits or qubits protected against errors. As a result, a system’s physical qubit count alone doesn’t indicate whether it’s close to running the algorithms needed for CRQC operations. Google and Microsoft are pursuing projects to reduce error rates for scalability.
Algorithm optimizations
Peter Shor’s 1994 algorithm established the theoretical threat to current encryption. Research results are refining estimates on the amount of resources required to perform a quantum attack on RSA-2048. This encryption standard is widely used to secure today’s web traffic, emails, digital signatures, software packages, hardware drivers, VPNs, and enterprise wireless networks.
These combined factors can affect Y2Q estimates. Breakthroughs could bring Y2Q closer, while unresolved technical challenges could push it further.
Why uncertainty does not mean organizations can wait
Waiting for a more accurate Y2Q forecast before acting is risky because cryptography is embedded across software, networks, digital identities, certificates, communications, devices, and third-party systems.
Reasons for immediate action pre-Y2K
The following factors make it necessary for organizations to urgently prepare for Y2K now:
Data longevity
Information an organization protects today may still need to remain confidential when quantum capabilities improve. Data requiring decades-long or lifetime protection, including bank or health records and national intelligence, is particularly exposed to the “Harvest Now, Decrypt Later” (HNDL) attack strategy.
Technology/infrastructure lifecycles
Enterprises typically refresh their conventional IT hardware every few years. But many industrial and operational technology systems remain in service for 10 to 30 years or more. Some of them can still be active if a CRQC is completed within that period. Replacing components across distributed and interconnected devices can be disruptive and expensive.
Migration complexity
The shift is not a matter of “flipping the switch.” The U.S. National Institute of Standards and Technology (NIST) observed that historically, integrating a new standardized cryptographic algorithm into information systems takes 10 to 20 years. Some constrained or legacy hardware may not have enough memory for certain post-quantum cryptography implementations.
Third-party dependencies
Vendors, cloud services, software products, and devices can complicate migration. Some contain cryptographic dependencies, such as updates and security fixes, that end users cannot see or change directly.
From uncertain predictions to practical planning timelines
Cybersecurity authorities are already setting quantum-readiness migration milestones without waiting for a reliable Y2Q date.
- In 2024, NIST published its first three post-quantum cryptography (PQC) standards. Based on its draft transition timeline, quantum-vulnerable public-key algorithms at 112-bit security strength would be deprecated after 2030. Quantum-vulnerable public-key algorithms would be disallowed after 2035.
- In June 2026, Executive Order 14412, signed by U.S. President Donald Trump, establishes 2030 and 2031 milestones for federal high-value assets and high-impact systems to use PQC for key establishment and digital signatures, respectively. It also directs agencies to help critical infrastructure owners and operators develop migration plans.
- In the UK’s three-stage roadmap, the “discovery” (inventory) and assessment exercise should be completed by 2028, along with an initial migration plan. The highest-priority migration should be done by 2031, while the broader migration to PQC should be finished by 2035.
- In Europe, the European Commission has called on Member States to begin transitioning to PQC by the end of 2026 and move high-risk use cases to PQC by the end of 2030.
- The Government of Canada aims to complete PQC migration by the end of 2031 for high-priority systems and by 2035 for the remaining non-classified systems. It also advises using existing IT lifecycle planning and budgets to initiate migration.
These policy milestones serve as planning mechanisms, not predictions of Y2Q’s onset.
How organizations can assess quantum risk without predicting Y2Q
Find the exposure.
First, identify where quantum-vulnerable cryptography is used across software, hardware, data repositories, and communications networks.
Establish what matters.
From there, prioritize assets based on sensitivity and longevity. They include classified communications, confidential financial and health records, and long-lived intellectual property. Prioritize data requiring long-term protection, as the systems securing it may not last as long as the data’s security requirements. Also, assess critical services based on potential impacts of disruption or compromise.
Pinpoint hard-to-change systems and dependencies.
Next, identify systems that lack flexibility to swap out encryption without a complete overhaul, such as proprietary applications and legacy vendor appliances.
Stress-test your timeline.
Organizations can then conduct scenario testing. If Y2Q happens earlier than anticipated, which systems will still be vulnerable? If it happens later, which migrations or investments can be adjusted? Results may be assessed against the organization’s risk tolerance, and the company can decide when and how aggressively to prepare. Different organizations may face different levels of urgency even when working from the same Y2Q forecast.
Building systems that can adapt to cryptographic change
PQC provides standardized algorithms. But systems should be flexible enough to adapt if requirements, implementations, or algorithms change. Scrutiny and testing continue for new cryptographic options. In July 2026, Anthropic reported that one of its AI models had discovered a mathematical vulnerability in HAWK, prompting the team to withdraw the candidate from NIST’s standardization process.
That’s why quantum readiness should be coupled with cryptographic agility. Crypto-agility is the capability to replace or update cryptographic mechanisms without redesigning the entire system or interrupting active operations. If a newly adopted algorithm proves unsuitable, agile systems can make changes without rebuilding architecture. This flexibility is especially helpful to engineering teams when standards or security requirements change.
What Y2Q uncertainty means for long-term infrastructure decisions
Systems acquired and installed now may remain operational while cryptographic requirements change. Adaptability should then be a primary consideration in procurement and architecture design.
Government and critical infrastructure:
Long operational lifecycles can make systems difficult to replace or upgrade, which can increase the risk of disruption or compromise.
Financial systems and telecommunications:
Interconnected technology with cryptography embedded across multiple components and dependencies can make migration complex.
Digital identity:
Cryptography upholds trust mechanisms.
Long-lived investments:
Procurement and design decisions can affect future migration.
The UK’s NCSC has advised organizations to build systems that can be easily updated. IT procurement managers should start asking for supported PQC standards and compatibility with future cryptographic changes.
In Hong Kong, HKCERT says a vendor’s “post-quantum” label is insufficient. It recommends asking suppliers about their PQC roadmap, hybrid cryptography support, long-term support plan for updates, and testing guidance. Under Canada’s federal roadmap, procurement contracts should include requirements for PQC support and crypto-agility.
For countries currently expanding digital infrastructure, new deployments can offer an opportunity to specify upgrade paths and cryptographic flexibility before additional dependencies accumulate.
Looking ahead
As quantum research advances, estimates of when a CRQC could emerge will change. Tracking credible developments in post-quantum cryptography can help organizations stay ready for disruptive technological shifts. At the same time, organizations should plan around their IT infrastructure’s exposure and vulnerabilities. Next steps will depend on system or data lifetimes, migration requirements, and risk tolerance.
Conclusion
A more precise Y2Q forecast shouldn’t be a prerequisite to preparing for its arrival. Organizations should focus on how much time they would need to transition if the quantum timeline moves faster than expected. Leaders and planners can start by understanding existing cryptographic dependencies, tracking evolving standards, and making new technology decisions that leave room for cryptographic changes.