The Foundation of Digital Trust Was Built for a World Without Quantum. That World Is Ending.

In the preceding articles of this series, I established the analytical framework that carries through everything that follows.

Q-Day is the moment a quantum computer achieves the capability to break modern encryption at scale. A planned-for event, not a hypothesis, serious enough that NIST finalized an entirely new suite of post-quantum cryptographic standards in 2024 and the NSA mandated migration timelines for national security systems under CNSA 2.0. A timeline that artificial intelligence is actively compressing.

C-Day, my original framing, is the capture moment: the strategic inflection point at which adversaries shift from opportunistic data theft to systematic, quantum-anticipatory collection. Harvesting encrypted data today with institutional patience, waiting for the quantum capability that will eventually make that encryption meaningless. I argued in Article 2 that C-Day has already occurred for the most sophisticated nation-state actors. The Silent Window, the period between C-Day and Q-Day, is not a warning period. It is an operational reality.

The Silent Quantum Window is the time between C-Day and Q-Day.  It started in the past and will continue in the future and it is what should be the thing in the back of your mind that has you dreading some point in the future.  It is the data that you think is safely encrypted now … but 5, 10, or 15 years in the future will still result in damages to your organization or in some cases to individuals.  It's the company's intellectual property, the files, emails, and communications that should never see the light of day.

These concepts rest on a technical foundation that most security leaders understand in general terms but have never been required to examine precisely. That changes the moment quantum computing becomes a board-level conversation, which it is, and a compliance issue — which it is becoming.

In this third article, I want to go beneath the surface on two fronts. First, the cryptographic architecture that quantum computing breaks — specifically, what it is, how it works, and what it protects. Second, and more importantly, what this means for how organizations need to think about resilience. Not just migration. Not just patching a protocol. Resilience — the capacity to absorb, adapt, and continue operating as both artificial intelligence and quantum computing fundamentally reshape the threat landscape simultaneously.

Those two forces, AI and quantum, are not independent developments on parallel tracks. They are converging. And the organizations that understand the convergence, rather than treating each as a separate workstream, are the ones that will build security architectures capable of surviving what is coming.

"The encryption protecting your organization's most sensitive communications and infrastructure was not designed to survive quantum computing. That is not a design flaw. It is a fact about physics. Resilience means building now for the world that physics is creating." — Doug Howard

The Architecture of Modern Encryption

To understand why quantum computing is a categorical threat to encryption, and why the resilience response has to be architectural rather than tactical, you first need to understand what modern encryption actually relies on.

The most widely deployed public-key cryptographic systems in the world — RSA, Elliptic Curve Cryptography (ECC), and Diffie-Hellman key exchange — share a common foundation. Their security does not come from a secret algorithm. The algorithms are publicly known. Their security comes entirely from a mathematical assumption: that certain computational problems are so difficult that no classical computer, regardless of speed or scale, could solve them in any practical timeframe.

RSA, developed in 1977 and still protecting the majority of internet communications today, derives its security from the difficulty of integer factorization — the problem of determining which two prime numbers, when multiplied together, produce a specific very large number. Factoring a 2048-bit RSA key using the best classical algorithm known would require computational effort measured in the lifetime of the universe. The security is not that factoring is impossible. It is that it is computationally impractical at the scale classical hardware can achieve.

Elliptic Curve Cryptography, which underpins modern authentication systems, HTTPS certificates, and secure messaging protocols, relies on the elliptic curve discrete logarithm problem — a different mathematical structure, but the same fundamental approach: security through computational intractability.

Diffie-Hellman key exchange, which allows two parties to establish a shared secret over a public channel without ever transmitting the secret itself, relies on the discrete logarithm problem in modular arithmetic.

All three are broken by the same quantum algorithm.  Quantum isn’t great, or even good, at a lot of things but this is what everyone agrees it will be amazing at .. decryption. 

What Shor's Algorithm Does and When It Becomes Real

In 1994, mathematician Peter Shor published an algorithm designed for quantum computers that solves integer factorization and discrete logarithm problems in polynomial time. On a sufficiently capable quantum computer, a 2048-bit RSA key that would take a classical machine longer than the age of the universe to factor could be broken in hours. Possibly minutes.

Shor's algorithm is proven. The only open question is scale: the algorithm requires fault-tolerant quantum computing at a size and stability that commercial systems have not yet achieved. That is precisely the engineering problem that IBM, Google, IonQ, and China's national quantum program are racing to solve.

IBM's publicly published quantum roadmap makes the timeline concrete in ways the "7-to-15 years" consensus does not. IBM targets demonstrated quantum advantage — quantum outperforming classical computation on a meaningful problem — in 2026. Their Nighthawk processor, currently running 7,500 gates on 360 qubits, scales to 10,000 gates on 1,080 qubits by 2027. Their first fault-tolerant quantum computer, capable of executing 100 million gates on 200 qubits, is targeted for delivery to clients in 2029. Full-scale fault-tolerant systems running one billion gates on 2,000 qubits are projected for 2033 and beyond.

That is one company's public roadmap, built for commercial clients, subject to engineering risks that could push timelines in either direction. It does not include classified national programs operating without commercial constraints or investor scrutiny. It does not account for the AI-driven acceleration of quantum engineering that I documented in the first article of this series.

What it does tell us is that fault-tolerant quantum computing — the category that makes Shor's algorithm operationally dangerous at scale — is on a roadmap measured in years from today, not decades. The 2029 milestone for IBM's first fault-tolerant system is three years from now. Whatever credible assumptions you apply to the gap between IBM's commercial roadmap and a nation-state's classified program, the planning horizon is not 2035. It is significantly closer.

What Quantum Actually Breaks

The scope of the problem is not a single protocol or a narrow application category. The cryptographic standards that quantum computing invalidates protect the infrastructure that modern digital life depends on entirely.

Transport Layer Security (TLS). The protocol securing virtually every HTTPS connection. Every online banking session. Every electronic health record exchange. Every cloud application. Every SaaS platform. Every e-commerce transaction. The padlock in your browser exists because of TLS, and TLS rests on the cryptographic assumptions that Shor's algorithm breaks.

Virtual Private Networks (VPNs). The encrypted tunnels through which remote workforces, branch offices, and third-party vendors access corporate environments. The confidentiality of those connections depends on key exchange mechanisms quantum computing will break.

Public Key Infrastructure (PKI). The system of digital certificates that establishes trust across the internet. When your email server proves it is who it claims to be, when a software update verifies it came from a legitimate publisher, when a government system authenticates to a user, that trust is built on PKI. Quantum computing does not just break individual encrypted messages. It breaks the trust infrastructure that every digital system uses to verify identity.

Digital signatures. The cryptographic mechanism proving a document, transaction, or piece of software has not been tampered with. Code signing certificates. Legal e-signatures. Financial transaction authorization. Document integrity verification in litigation, audit, and regulatory compliance contexts.

Identity infrastructure. The authentication systems protecting access to corporate environments, government systems, financial networks, and critical infrastructure.

Q-Day does not break one system. It breaks the foundation every system is built on. And that distinction — between a single vulnerability and a foundational failure — is precisely what makes resilience the right frame for how organizations need to respond.

The Resilience Imperative: Beyond Migration

Most of the post-quantum conversation in security circles focuses on migration — replacing vulnerable cryptographic algorithms with NIST-approved post-quantum equivalents. That is necessary. It is not sufficient.

The organizations that will survive the AI-quantum convergence are not the ones that complete a cryptographic migration and consider the problem solved. They are the ones that build security architectures designed to absorb and adapt to continuous change — because both AI and quantum are not single events to prepare for, they are permanent, accelerating forces that will reshape the threat landscape on an ongoing basis.

AI is already operating at machine speed on the offensive side of the security equation. Reconnaissance, phishing generation, credential stuffing, vulnerability exploitation, lateral movement — each of these attack phases is being automated and accelerated by AI tools available to adversaries today. Agentic AI — autonomous systems that can reason, adapt, and execute multi-step attack campaigns without human intervention — is not a future threat. It is a current one. The organizations defending against it with human-speed detection and response cycles are already at a structural disadvantage.

Quantum, when it arrives at operational scale, will compound that asymmetry in a way that cannot be remediated by adding analysts or tuning rules. A quantum-capable adversary operating against a classically-defended environment is not a more powerful version of today's threat. It is a categorically different one.

The convergence of these two forces — AI acceleration of quantum development, and quantum amplification of AI capability — means that the security architecture decisions organizations make in the next three to five years are not just about surviving the next breach cycle. They are about whether the organization's security posture will be structurally viable in 2030, 2033, and beyond.

Resilience, in this context, means three things that go beyond algorithm replacement.

First, architectural adaptability. The cryptographic infrastructure an organization deploys today must be designed to change — not once, during a post-quantum migration, but continuously. Cryptography evolves. Standards are revised. Mathematical assumptions are revisited. An organization whose security architecture is tightly coupled to specific cryptographic implementations will face the same migration crisis again the next time the landscape shifts. Crypto-agility — the capacity to swap cryptographic primitives without redesigning the systems that use them — is not just a post-quantum best practice. It is the fundamental design principle of a resilient security architecture.

Second, detection at machine speed. C-Day Scenario 2 — the silent, persistent collection operations that never trigger a classical detection event — is only invisible until you have the detection architecture to surface it. The same AI that is accelerating quantum development is the mechanism by which those operations become discoverable. AI-native detection platforms with continuous behavioral learning, anomalous outbound telemetry monitoring, and pattern recognition operating across data volumes no human analyst can process are not a competitive advantage in this environment. They are the baseline requirement for organizations that want to know what is happening inside their environments rather than learning about it years later from a forensic investigation.

Third, operational continuity planning for a breach-assumed environment. The correct posture in the AI-quantum era is not the hope that cryptographic migration will prevent the breach. It is the assumption that some level of compromise, in some form, across some timeline, is a baseline condition — and the organizational investment in resilience, response, and recovery capability that assumption demands. The organizations that build for breach-assumed continuity now will recover faster, disclose more confidently, and face lower regulatory and litigation exposure when events occur. The ones that treat migration as a substitute for resilience planning will not.

What NIST Has Done — and What It Does Not Solve

In August 2024, NIST finalized the first three post-quantum cryptographic standards in its history. ML-KEM (formerly CRYSTALS-Kyber) for key encapsulation — replacing the Diffie-Hellman and RSA-based key exchange mechanisms that protect most encrypted communications. ML-DSA (formerly CRYSTALS-Dilithium) and SLH-DSA (formerly SPHINCS+) for digital signatures — replacing the RSA and ECC-based mechanisms that establish trust across PKI, code signing, and authentication infrastructure.

These are finished standards, designed to resist attacks from both classical and quantum computers, reviewed through an eight-year global evaluation process. The NSA endorses them. CISA has published migration guidance built on them. Federal agencies are under mandate to develop post-quantum migration roadmaps.

What the NIST standards provide: a destination. A set of quantum-resistant algorithms that, correctly implemented, will remain secure against the quantum threat as currently understood.

What they do not provide: the migration itself, the organizational inventory that makes migration possible, or the detection capability that addresses C-Day Scenario 2 while the migration is underway.

One additional point deserves emphasis. NIST's evaluation process surfaced a cautionary data point: one of the initial post-quantum candidates, SIKE, was broken by a classical computer in 2022 — after years of evaluation. The algorithms NIST ultimately standardized are believed to be quantum-resistant on strong mathematical grounds. That belief is well-founded. It is not a guarantee. An organization that migrates to post-quantum standards in a rigid, one-time implementation has made a brittle bet. An organization that achieves crypto-agility in the process of migration has built the capacity to respond when the mathematics is inevitably revisited.

The Operational Gap Most Organizations Are Not Facing

Most security leaders, when they engage seriously with the post-quantum problem, focus on the wrong question. They ask: "When do we need to migrate?"

The right question is: "Do we even know what we would need to migrate?"

A 2023 assessment found that most enterprise organizations do not have a complete, accurate inventory of where cryptography lives in their environment. Not where it should live — where it actually lives, today, including in firmware, legacy systems, third-party SaaS dependencies, and applications whose administrators have never examined the underlying cryptographic implementation.

Cryptography is embedded everywhere. It is in the TLS handshake your web applications initiate thousands of times per second. It is in the firmware of your network switches, your industrial control systems, your building management systems. It is in the certificate authorities your organization trusts, in the software signing chains that validate every update your endpoints receive, in the authentication tokens your identity provider issues. It is in legacy systems no one has opened in a decade because they work and nobody has given the underlying cryptography a second thought.

The post-quantum migration is not a software update. It is a systematic cryptographic inventory exercise followed by a phased replacement program that touches every system in the environment — including systems whose owners may not know they run cryptography, and including third-party dependencies over which your organization has no direct control.

This inventory gap is not a future quantum problem. It is an operational deficiency that exists today, regardless of when Q-Day arrives. An organization that does not know where its cryptography lives cannot protect it, cannot migrate it, and cannot accurately assess its C-Day exposure. That gap closes deliberately, with investment and effort — or it gets closed for you, under regulatory pressure or after a breach that makes the stakes impossible to ignore.

Federal Mandates and the Private Sector Cascade

The federal government has made the policy decision. The question is when and how it cascades into private-sector compliance with enforcement teeth.

NSM-10 directed federal agencies to inventory cryptographic systems, identify those most vulnerable to quantum attack, and begin migration planning. CISA published its post-quantum roadmap. CNSA 2.0 established migration timelines for national security systems, with requirements taking effect now. Apple has deployed post-quantum cryptographic protections in iMessage through the PQ3 protocol. Google is testing post-quantum cryptography in Chrome. These are not theoretical preparations — they are production deployments by organizations whose engineering teams have already concluded the threat is real and the timeline is short.

The defense industrial base is the first private-sector category in the path of this regulatory wave. CMMC has been revised before and will be revised again. Post-quantum cryptographic requirements for defense contractors handling Controlled Unclassified Information are a logical and likely near-term evolution. Organizations in the defense industrial base treating post-quantum migration as a future problem are making the same miscalculation those organizations made about multi-factor authentication before it became a hard CMMC requirement.

Beyond defense: the SEC's 2023 cybersecurity disclosure rules create a materiality framework that applies to known, foreseeable risks. The NSA, CISA, and NIST have established a documented knowledge baseline on quantum risk. An organization's argument that its board was unaware of a known, material cybersecurity risk is increasingly difficult to sustain.

The Howard Projection

By 2027, CMMC will incorporate post-quantum cryptographic requirements as a condition of certification for contractors handling sensitive Controlled Unclassified Information categories. The initial requireme

By 2027, CMMC will incorporate post-quantum cryptographic requirements as a condition of certification for contractors handling sensitive Controlled Unclassified Information categories. The initial requirement will demand a documented cryptographic inventory and migration roadmap with milestones — not full migration. Organizations that cannot produce that documentation will face certification risk. The defense industrial base will spend 2027 and 2028 conducting the cryptographic inventory they should have started in 2024.

By 2028, at least one major class-action lawsuit will be filed against a financial institution or healthcare system for failure to implement post-quantum cryptographic protections following a breach where forensic evidence demonstrates quantum-assisted decryption of previously harvested data. The legal argument will be straightforward: the organization had documented notice of the quantum risk through NSA, CISA, and NIST guidance; had access to NIST-standardized mitigations; and chose not to act. That argument will be legally viable, and it will permanently reshape how boards treat post-quantum migration as a fiduciary matter.

By 2029, IBM's publicly stated target for delivering its first fault-tolerant quantum computer to clients, the security implications of quantum computing will shift from theoretical to demonstrated. Whether IBM's roadmap holds precisely or slips by twelve to eighteen months, the arrival of fault-tolerant commercial quantum capability in this timeframe will be the event that forces every board conversation from "when should we start?" to "why haven't we finished?" Organizations that have not completed their cryptographic inventories by 2029 will be initiating emergency migrations under conditions they could have managed strategically.

By 2030, post-quantum cryptographic posture will be a standard due diligence line item in M&A transactions involving regulated industries, critical infrastructure, or defense-adjacent sectors. An incomplete or undocumented cryptographic inventory will be treated the same way an unresolved regulatory finding or an unpatched critical vulnerability is treated today — as a deal-pricing factor. Organizations that have made documented progress will command a premium. Those that have not will accept the discount.

By 2040, organizations still operating legacy RSA or ECC-based cryptographic infrastructure for sensitive communications will face effective uninsurability for quantum-related breach events, non-compliance with every major regulatory framework in the United States and European Union, and exclusion from federal contracting. That outcome is not speculative. It is the logical conclusion of a regulatory and market trajectory that is already moving. The only variable is whether individual organizations get ahead of it or are caught by it.

What Comes Next

The next installment of this series addresses the dimension of the quantum threat that is simultaneously the most underestimated and the most consequential for how security operations will evolve over the next two decades.

Artificial intelligence and quantum computing are not developing on separate timelines that eventually converge. They are accelerating each other now. AI is solving the hardest engineering problems in quantum hardware development. Quantum computing, at scale, will amplify certain AI capabilities in ways that will reshape the offense-defense balance in security operations entirely.

I will argue, in that article, that the organizations building AI-native security infrastructure now are not just addressing today's threat landscape. They are making the only architectural investment that will remain structurally viable as these two forces converge — and that the gap between organizations that understand this and those that do not will be the defining fault line in enterprise security over the next decade.

The foundation of digital trust we rely on today was built for the computational landscape of 1977, refined over decades, and deployed at a scale its designers could not have imagined. It has served us extraordinarily well. It will not survive Q-Day intact.

Resilience is not a synonym for migration. It is the capacity to operate, detect, respond, and recover in a world where the cryptographic assumptions have changed and the adversary is operating at machine speed. Building that capacity is the work of the Silent Window. The window will not stay open.

This is the third article in the series "The Quantum Clock Is Ticking." Previous articles are available at pondurance.com/blog/the-quantum-clock-is-ticking and pondurance.com/blog/the-quantum-clock-is-ticking-c-day.

About the Author: Doug Howard is the CEO of Pondurance, an AI-powered managed detection and response firm providing MDR, digital forensics and incident response, and cyber advisory services. He previously served in the U.S. Air Force and held roles at the Pentagon. He writes on cybersecurity, artificial intelligence, and emerging threats at the intersection of national security and enterprise risk.