NeuralWired

Breaking RSA-2048 With 100,000 Qubits | The Post-Quantum Cryptography Urgency

A new architecture just compressed the quantum threat timeline. Here’s what CISOs, CTOs, and enterprise leaders must do, and when.

Quantum Computing  |  Cybersecurity  |  Enterprise Strategy

Estimated read time: 14 minutes

<100K Qubits now needed to break RSA-20483–5 yrs Hardware partner timeline to CRQC$7–12M Enterprise PQC migration cost estimate2035 NCSC deadline for full PQC migration
The number that should keep every CISO awake tonight is 100,000.

That’s the qubit count Iceberg Quantum’s Pinnacle architecture needs to break RSA-2048, the encryption standard protecting virtually every financial transaction, secure communication, and government database on the planet. Until February 12, 2026, the consensus estimate was somewhere between one million and twenty million qubits. Pinnacle just compressed that gap by a factor of ten.

For security leaders who assumed they had a comfortable decade to migrate, the calculus changed overnight. Hardware partners including PsiQuantum, Diraq, and IonQ are projecting systems of this scale within three to five years. The store-now-decrypt-later threat, where adversaries harvest encrypted data today to decrypt it once a cryptographically relevant quantum computer arrives, is no longer a distant theoretical concern. It is an active, present-tense risk.

This isn’t a reason to panic. It is a reason to act.

This guide examines exactly what the Pinnacle breakthrough means technically, why hardware timelines make the threat credible within the decade, how NIST and the UK’s NCSC have already handed organizations a migration roadmap, and what a realistic implementation plan looks like, including costs. By the end, you’ll have both the strategic framing and the operational checklist to brief your board and begin moving.

Section 01 · Breakthrough

The Pinnacle Breakthrough — What Changed and Why It Matters

How Iceberg Quantum’s Pinnacle architecture reduced the qubit requirement for breaking RSA-2048 by a factor of ten — and what that means for every security team operating today.

To understand the significance of Iceberg Quantum’s announcement, you need context on why qubit counts have historically seemed so prohibitive.

The Pre-Pinnacle Baseline

In 2019, researchers Craig Gidney and Martin Eklera published the benchmark estimate: breaking RSA-2048 would require roughly 20 million physical qubits. At the time, state-of-the-art hardware was operating in the hundreds of qubits with error rates far too high for cryptographic applications. The gap between capability and threat felt enormous.

By October 2025, Google’s Quantum AI team published analysis reducing that estimate to approximately one million noisy qubits, a meaningful 20x reduction. Security teams updated threat models but still felt comfortable. A million qubits remained well beyond any hardware roadmap’s near-term horizon.

Then came Pinnacle.

The Quantum LDPC Innovation

Key technical finding: The Pinnacle arXiv preprint (arxiv.org/abs/2602.11457), published February 12, 2026, demonstrates RSA-2048 factoring with fewer than 100,000 physical qubits, assuming a 10⁻³ error rate and 1 microsecond gate cycle time.
The mechanism behind this reduction is quantum Low-Density Parity-Check (QLDPC) codes. Classical error correction in quantum computing has historically required enormous qubit overhead, you need many physical qubits to encode each logical qubit reliably. Surface codes, the dominant approach, are reliable but expensive in qubit count. QLDPC codes achieve comparable error correction with dramatically lower overhead, unlocking significant reductions in the physical qubit budget required for complex computations.

Iceberg’s architecture doesn’t just adopt QLDPC codes; it integrates them into a complete fault-tolerant system design, what the company calls the Pinnacle architecture, optimized specifically for the Shor’s algorithm computations needed to factor large integers.

The progression from 2019 to today:

Architecture / EstimateQubits Required for RSA-2048YearSource
Gidney-Eklera Baseline~20 million2019arXiv (peer-reviewed)
Google Quantum AI Update~1 million (noisy)Oct 2025Google Quantum AI preprint
Iceberg Pinnacle Architecture<100,000Feb 2026arXiv 2602.11457 + press release
Table 1: Qubit requirement reductions for breaking RSA-2048 (2019–2026). Each estimate uses different technical assumptions; Pinnacle’s figure assumes 10⁻³ error rate.

What the Caveats Mean

The 100,000-qubit figure is not a guarantee, it’s a simulation-validated estimate with specific technical assumptions that hardware must eventually meet. The 10⁻³ error rate (one error per thousand gate operations) is aggressive but within the target envelope of advanced quantum hardware programs. The one-microsecond gate cycle time is similarly demanding.

Neither Iceberg Quantum nor any partner has built a system demonstrating these capabilities at scale. Peer review of the preprint is still in progress. These are important caveats, and they don’t neutralize the urgency. The architectural blueprint is published. Multiple hardware programs are racing toward the necessary specifications. The question is no longer if, but when.

“Iceberg’s advances in qLDPC-based architectures will bring forward utility-scale applications on our devices by years. This is a deeply challenging area, and Iceberg has assembled the rare expertise required to make real progress.” — Andre Saraiva, Head of Theory, Diraq — via Iceberg Quantum press release

Section 02 · Timeline

The CRQC Timeline — When Should Enterprises Be Worried?

Hardware partners PsiQuantum, Diraq, and IonQ are projecting cryptographically relevant quantum computers within 3–5 years. Here’s what that window actually means — and why store-now-decrypt-later makes it urgent today.

A Cryptographically Relevant Quantum Computer (CRQC) is a machine capable of running Shor’s algorithm at a scale sufficient to break deployed encryption. For RSA-2048, that threshold just moved significantly closer. But how close, realistically?

Hardware Partner Projections

Iceberg Quantum’s Pinnacle announcement came alongside confirmation of active partnerships with three of the most credible quantum hardware programs in the world: PsiQuantum, Diraq, and IonQ. These aren’t marketing relationships. These are hardware companies that have reviewed the Pinnacle architecture and believe their development roadmaps intersect with its requirements.

According to the Iceberg Quantum press release, hardware partners project ‘timelines to build systems of this scale within the next three to five years.’ At current trajectories, that puts a credible CRQC threat window between 2029 and 2031.
PsiQuantum is developing photonic quantum computing and has published roadmaps targeting fault-tolerant operation in the latter half of this decade. Diraq, an Australian-UK quantum spinout, focuses on silicon-spin qubits with density advantages that could facilitate large-scale qubit arrays. IonQ’s trapped-ion architecture currently leads on error rates among commercially available systems.

None of these companies is guaranteed to hit aggressive targets. Hardware development routinely slips. But the convergence of multiple credible programs moving toward the same technical threshold, and doing so in coordination with a team that has shown how to dramatically reduce the qubit requirement, is a qualitatively different situation than existed even six months ago.

The Store-Now-Decrypt-Later Problem

Here’s the threat that makes even a 2029-2031 timeline actionable today: adversarial actors can harvest encrypted data now and decrypt it once a CRQC becomes available.

This attack vector is known as harvest now, decrypt later (HNDL), or store-now-decrypt-later (SNDL). Nation-state actors with long-horizon intelligence goals have operational incentive to stockpile encrypted communications, financial records, intellectual property, and government data captured today. Classified assessments from multiple intelligence agencies have flagged this as an active, ongoing collection activity.

If your encrypted data has value in 2030, trade secrets, long-term contracts, health records, national security information, financial models, it should be treated as potentially compromised today. That’s the operating posture post-Pinnacle demands.

“Our ambition is to help accelerate the transition to, and ultimately power, the fault-tolerant era of quantum computing.” — Felix Thomsen, Co-founder and CEO, Iceberg Quantum

The Uncertainty Principle (And Why It Doesn’t Provide Comfort)

Will the CRQC actually arrive in 2029? Possibly not. Hardware timelines slip. Error correction improvements may plateau. Engineering challenges not yet visible may emerge. There are genuine, substantive reasons to maintain calibrated uncertainty about any specific timeline.

The problem with using that uncertainty as a reason to wait is asymmetric. If migration is delayed until the threat materializes, the window to act may have closed, or will require crisis-mode spending at multiples of the cost of orderly migration. If migration happens and the quantum threat proves slower to materialize, the cost is a compliance investment that also reduces classical cryptographic risk and satisfies regulatory mandates now coming into force.

The risk calculus is not close. Migration wins even under optimistic quantum timelines.

Section 03 · Roadmap

The Post-Quantum Cryptography Migration Roadmap

NIST finalized three post-quantum standards in 2024. The UK’s NCSC published milestone deadlines through 2035. The framework is built — here’s how to navigate it.

The good news: governments and standards bodies didn’t wait for Pinnacle to start building the migration framework. NIST finalized the first three post-quantum encryption standards in August 2024. The UK’s National Cyber Security Centre published official migration timelines with specific milestones. Organizations that start now are working within an established, well-resourced framework, not pioneering into the unknown.

NIST’s Post-Quantum Standards: What Was Finalized

After a multi-year evaluation process involving global cryptographers, NIST published three finalized post-quantum cryptography standards in August 2024:

  • ML-KEM (Module-Lattice Key Encapsulation Mechanism), the primary standard for general encryption and key exchange. Based on the CRYSTALS-Kyber algorithm. Suitable for TLS, VPNs, and most enterprise encryption use cases.
  • ML-DSA (Module-Lattice Digital Signature Algorithm), the primary standard for digital signatures. Based on CRYSTALS-Dilithium. Suitable for code signing, certificate authorities, and authentication systems.
  • SLH-DSA (Stateless Hash-Based Digital Signature Algorithm), a conservative, hash-based signature standard providing a security guarantee independent of lattice assumptions. Serves as a backup if lattice cryptography is later found vulnerable.
These standards are not provisional, they’re finalized, published, and ready for implementation. The NIST post-quantum cryptography standards represent eight years of international cryptographic scrutiny. Enterprises can implement against them with confidence.

The NCSC Migration Timeline: Official Milestones

The UK’s National Cyber Security Centre has published the most explicit government migration timeline currently available. It provides three concrete milestones that serve as useful benchmarks for enterprise planning globally:

NCSC MilestoneTarget DateWhat It Means for Your Organization
Full Cryptographic DiscoveryBy 2028Complete inventory of all systems using classical public-key cryptography. Know what you’re protecting and where it runs.
Highest-Priority MigrationBy 2031Critical infrastructure, financial systems, health data, government systems migrated to PQC standards.
Complete PQC MigrationBy 2035All organizational systems migrated. Classical RSA/ECC encryption fully retired from production environments.
Table 2: UK NCSC PQC Migration Milestones (Source: NCSC PQC Migration Timelines Guidance, 2025). These milestones apply to UK critical infrastructure but serve as global best-practice benchmarks.

The 2028 discovery milestone deserves emphasis. Most large organizations don’t have a complete, current inventory of their cryptographic dependencies. Libraries, APIs, cloud services, SaaS platforms, IoT devices, and legacy systems all use encryption, and most IT teams can’t enumerate them precisely. Building that inventory is the essential first step, and 2028 gives two years to complete it. That clock is running.

The PQC Migration Timeline at a Glance

YearEvent / Milestone
2024NIST finalizes ML-KEM, ML-DSA, SLH-DSA, the three core PQC standards
2026Iceberg Quantum Pinnacle: CRQC qubit threshold drops to <100,000 qubits
2028NCSC target: Complete cryptographic asset discovery across all systems
2031NCSC target: Highest-priority systems fully migrated to PQC
2029–2031 (est.)Credible CRQC hardware window per hardware partner projections
2035NCSC target: Full migration complete, classical RSA/ECC retired
Table 3: PQC Migration Timeline (NIST, NCSC, Iceberg Quantum projections). The overlap of the credible CRQC window and the 2031 priority migration deadline creates a narrow execution window.

The NSA CNSA 2.0 Suite

For US federal contractors and defense-adjacent enterprises, the timeline is even more prescribed. The NSA’s Commercial National Security Algorithm Suite 2.0 (CNSA 2.0) has established specific deadlines for transitioning national security systems to post-quantum algorithms. The NSA’s posture is unambiguous: RSA and elliptic-curve cryptography are being deprecated for national security applications. Organizations in the defense industrial base need to treat compliance with CNSA 2.0 requirements as a non-negotiable operational mandate, not a future roadmap item.

“The path to fault-tolerant quantum computing needs exactly the type of innovations we’ve seen from the Iceberg team.” — Prineha Narang, DCVC (Investor in Iceberg Quantum)

Section 04 · Costs & ROI

The Cost Reality — What PQC Migration Actually Runs

Enterprise migration runs $7M–$12M for large financial institutions. Here’s where the budget goes, how to model ROI, and the CFO framing that gets migration approved.

CFOs will ask the question that CISOs need to be ready to answer: What does this cost, and how do we justify it? The honest answer is that migration is expensive. The complete answer is that the alternative is potentially catastrophic, and regulatory mandates are making investment involuntary for most industries.

Enterprise Cost Estimates

Migration costs vary enormously by organization size, sector, and cryptographic dependency footprint. For illustrative purposes, analysis of enterprise migration projects and budget modeling for large financial institutions provides a useful benchmark.

Organization TypeEstimated PQC Migration CostKey Cost Drivers
Large Multinational Bank$7M – $12MCore banking systems, payment rails, HSM upgrades, certificate authority overhaul, compliance testing
US Federal Agency (aggregate)$7.1B (total govt)Per White House/OMB analysis; includes all civilian agencies, legacy system remediation
Mid-Market Enterprise (1,000–5,000 employees)$500K – $2M (est.)SaaS migration, VPN/TLS updates, PKI refresh, training
Critical Infrastructure (Energy/Utilities)$2M – $8M (est.)OT/ICS systems, SCADA encryption, long hardware lifecycle
Table 4: Enterprise PQC Migration Cost Estimates. Large bank figures from PQC Budget Calculator (December 2025); federal aggregate from White House OMB analysis. Mid-market and infrastructure figures are modeled projections.

Where the Money Goes

Migration costs break across five primary categories:

  • Cryptographic Asset Discovery (15–20%): Inventory tooling, code scanning, dependency mapping, external audit. Often the most time-intensive phase due to undocumented legacy dependencies.
  • Algorithm Migration and Development (35–40%): Updating libraries, APIs, protocols, and applications to PQC standards. Includes hybrid deployment, running classical and PQC simultaneously during transition.
  • Hardware Security Module (HSM) Upgrades (15–20%): HSMs are the physical root of trust for most enterprise cryptography. Many current-generation HSMs don’t support PQC algorithms and require either firmware updates or replacement.
  • Testing and Compliance Validation (15%): Performance testing (PQC algorithms carry computational overhead), interoperability testing, regulatory certification.
  • Training and Organizational Change (10–15%): Development teams, security operations, third-party vendors, and supply chain partners all need updated practices.

The ROI Frame That Works With CFOs

The correct framing for CFOs isn’t ‘this is a new cost.’ It’s ‘this is regulatory compliance investment with a risk-reduction payoff, and the alternative is potential multi-billion-dollar breach liability or regulatory sanction.’
Three financial arguments strengthen the migration business case:

  1. Regulatory inevitability: NSA CNSA 2.0, NCSC guidance, and anticipated EU mandates make this a matter of when, not if. Delaying adds complexity and cost without reducing liability.
  2. Breach cost benchmarks: IBM’s 2025 Cost of a Data Breach Report found the global average breach cost exceeded $4.5M. A quantum-enabled decryption event affecting multi-year harvested data could produce liability, regulatory fines, and reputational damage orders of magnitude larger.
  3. Classical security co-benefits: Cryptographic discovery and modernization reduce classical vulnerabilities simultaneously. Many organizations find the migration process uncovers outdated libraries, weak key management, and certificate hygiene issues that were pre-existing risks.
Section 05 · Action Plan

Your 5-Step PQC Migration Action Plan

From cryptographic asset discovery to crypto-agility architecture — the complete operational checklist security and technology leaders can begin executing immediately.

The Pinnacle architecture didn’t create the post-quantum cryptography problem, it compressed the timeline in ways that make delay untenable. The framework for response already exists. NIST has finalized the standards. NCSC has published the milestones. The question is execution.

Here is the five-step plan that security and technology leaders can begin immediately:

Step 1: Cryptographic Asset Discovery (Start Now, Complete by 2028)

You cannot migrate what you haven’t inventoried. Begin a comprehensive cryptographic asset discovery program covering:

  • All public-key cryptography in use (RSA, ECC, DH key exchange)
  • Certificate authorities, PKI infrastructure, and expiry schedules
  • Third-party SaaS, APIs, and cloud services with encryption dependencies
  • Hardware with embedded cryptography (HSMs, TPMs, IoT devices, OT/ICS systems)
  • Data classified as long-term sensitive, anything with a shelf life beyond 2030
Tools from vendors including Cryptosense, Quantum Xchange, and IBM Crypto Discovery accelerate this phase. The NCSC cryptographic asset discovery guidance provides a practical framework for prioritizing this work. Build a living cryptographic inventory that updates continuously, not a one-time audit.

Step 2: Risk-Tier Your Assets

Not all encrypted assets carry equal risk. Prioritize migration by two dimensions: sensitivity of the data and longevity of the risk horizon. High-priority candidates include:

  • Long-lived sensitive data: IP, contracts, health records, national security information
  • Critical infrastructure systems: payment processing, grid management, identity systems
  • Defense and government systems subject to NSA CNSA 2.0 mandates
  • Any system storing data with multi-decade value to a nation-state adversary
Lower-priority candidates include systems handling short-lived data with minimal breach consequence. Not everything needs to move by 2031, but the high-priority tier does.

Step 3: Implement Hybrid Cryptography for High-Priority Systems

Hybrid deployment, running classical and PQC algorithms simultaneously, is the recommended transition architecture. It maintains backward compatibility while providing quantum-resistant protection. IETF standards for hybrid TLS are already published. NIST’s guidance supports hybrid deployment as the primary migration pattern.

Begin hybrid deployment with ML-KEM for key encapsulation and ML-DSA for digital signatures. Test performance overhead (PQC algorithms carry higher computational costs) and validate interoperability with partners and vendors.

Step 4: Update the Supply Chain

Your PQC migration is only as strong as your partners’ migrations. Assess cryptographic practices of critical vendors, SaaS providers, and supply chain partners. Include PQC migration requirements in vendor contracts and procurement standards. Engage cloud providers on their PQC roadmaps, AWS, Azure, and Google Cloud all have post-quantum programs in various stages of deployment.

This step is underweighted in most migration plans and represents a significant residual risk for organizations that complete their own migration without addressing the supply chain exposure.

Step 5: Build Crypto-Agility Into Architecture

The deepest organizational change post-Pinnacle is architectural: build systems that can update their cryptographic primitives without full redeployment. Crypto-agility, the ability to swap algorithms rapidly, is the long-term defense against a cryptographic landscape that will continue evolving.

This means abstracting cryptographic functions into updatable libraries, avoiding hard-coded algorithm assumptions, and establishing a cryptographic governance function that monitors standards evolution and can trigger migration rapidly when needed.

What to Watch in the Next 12 Months

Three developments will shape the post-Pinnacle landscape through 2027:

  • Peer review of the Pinnacle preprint. The arXiv paper is under review. Independent cryptographic scrutiny may validate, refine, or challenge specific assumptions. Watch for formal publication and response from the cryptographic research community.
  • Hardware milestone announcements from PsiQuantum, Diraq, and IonQ. Concrete demonstrations of qubit scale and error rate progress will provide the most direct signal on CRQC timeline credibility. Any announcement of fault-tolerant operation at scale should trigger immediate escalation of migration plans.
  • Regulatory action in the EU and Asia-Pacific. The EU’s NIS2 directive and DORA framework are expanding cybersecurity mandates. Expect post-quantum requirements to appear in regulatory guidance within 18–24 months, following the NCSC and NSA lead. Organizations operating in multiple jurisdictions should expect compliance timelines to converge around the NCSC 2031 milestone.
The pattern is clear: every major cryptographic transition in computing history has taken longer and cost more than expected. The organizations that win are the ones that started early, before the timeline became a crisis. Pinnacle reset the clock. The organizations starting their migration now will be the ones writing case studies in 2031, not emergency incident reports.

Sources & References

All sources used in this analysis, verified and current as of February 2026:

NeuralWired  |  Frontier Intelligence. Decoded for a Neural-Wired World.

This article was produced in accordance with NeuralWired editorial standards. All claims verified against primary sources. Human editorial oversight applied throughout.

Written by

Team_Neuralwired

in

More posts