Artificial intelligence is on the verge of transforming our lives; however, another emerging technology, quantum computing, could profoundly change the landscape of cybersecurity. This is no longer a theoretical debate: the US government has finalized encryption standards to replace today’s algorithms and set a federal deadline to do it. This article explains what quantum computing changes for cryptography, the real timeline businesses are now working against, and what to do about it.
Quantum Computing and its Implications for Cybersecurity
Quantum computing, also covered from a different angle in our piece on its practical challenges and changes, uses qubits instead of classical binary bits, letting it run certain calculations at a scale ordinary computers cannot match. That capability is also what makes it a threat to current encryption.
Traditionally, cryptographic systems have relied on mathematical complexity to secure data; for instance, encryption based on the RSA algorithm is grounded in the difficulty of factoring large prime numbers, and ECC relies on the difficulty of the elliptic-curve discrete logarithm problem. With Shor’s algorithm, a sufficiently powerful quantum computer could solve both problems efficiently, which is why RSA and ECC — the algorithms behind most of today’s HTTPS traffic, VPNs, and digital signatures — are the ones security agencies name explicitly as at risk.

That threat is not only about the future. Security agencies describe “harvest now, decrypt later”: an adversary can record encrypted traffic today and simply store it, waiting until a quantum computer capable of breaking it exists. For any data that needs to stay confidential for years — health records, trade secrets, long-term government or legal data — that attack works even if the quantum computer only arrives a decade from now.

Why This Is Not Theoretical Anymore: The Real Timeline (2024–2031)
In August 2024, the US National Institute of Standards and Technology (NIST) finalized its first three post-quantum cryptography standards: FIPS 203 (ML-KEM, for general encryption, formerly known as CRYSTALS-Kyber), FIPS 204 (ML-DSA, for digital signatures, formerly CRYSTALS-Dilithium), and FIPS 205 (SLH-DSA, a hash-based signature scheme, formerly SPHINCS+). NIST’s own announcement urged system administrators to “start integrating them into their systems immediately, because full integration will take time” (NIST, August 13, 2024).
That guidance became a legal deadline in 2026. On June 22, 2026, the White House signed Executive Order 14412, “Securing the Nation Against Advanced Cryptographic Attacks,” which requires US federal agencies to migrate their most sensitive systems (High Value Assets and high-impact systems) to post-quantum encryption by December 31, 2030, and to post-quantum authentication by December 31, 2031 (reported by Cloudflare, June 2026). Large suppliers to government and regulated industries — cloud providers, browser vendors, telecoms — are moving on the same clock, since any product they sell into that market needs to meet it.
The infrastructure is already shifting in production, not just on paper:
- Apple shipped PQ3, a post-quantum protocol for iMessage, in February 2024 — the first consumer messaging protocol to protect both the initial key exchange and the ongoing message ratchet against a future quantum attacker.
- Google Chrome enabled a hybrid post-quantum key exchange (X25519Kyber768) by default starting with Chrome 124, in April 2024.
- Cloudflare reports that more than two-thirds of the human browser traffic crossing its network is now protected with post-quantum key agreement, and has moved its own internal target for full post-quantum migration to 2029 — a year ahead of the US federal deadline (Cloudflare, 2026).
In other words: the organizations that run the encryption most of the internet depends on have already started the transition. The practical question for any other business is no longer “if,” but how fast to move before the deadline reaches them through a supplier, an auditor, or a client contract.
How This Works in Practice
Implementing quantum-safe strategies begins with a thorough assessment of existing cryptographic systems and their vulnerabilities in the context of quantum computing. The steps to achieve a quantum-safe environment involve several key actions:
- Cryptographic inventory: organizations must find every place RSA, ECC (ECDSA/ECDH), or similar classical algorithms are used — TLS certificates, VPNs, code-signing, API tokens, internal services — before deciding what to replace first.
- Prioritize by data lifetime, not by system age: data that must stay confidential for 10+ years (health, legal, long-term contracts) is exposed to “harvest now, decrypt later” today, even though no quantum computer can break it yet — it should move first.
- Adopt the standardized algorithms: ML-KEM (FIPS 203) for key exchange and ML-DSA (FIPS 204) or SLH-DSA (FIPS 205) for signatures are now final NIST standards, not experimental proposals — most major TLS libraries and cloud providers already support them in hybrid mode (classical + post-quantum together).
- Start with hybrid mode: the same approach Chrome and Cloudflare use — running the post-quantum algorithm alongside the classical one — gives protection against future quantum attacks without removing the fallback that today’s systems still rely on.
- Testing and validation: before fully deploying new systems, organizations must conduct rigorous testing to validate the effectiveness of the implemented quantum-safe measures, since some post-quantum algorithms use larger keys and signatures than RSA/ECC and can affect performance or compatibility.
- Continuous monitoring: cryptographic migration is multi-year work. Treat it as an ongoing program with an owner and a deadline tied to the federal timeline above, not a one-time project.
Key stakeholders involved in this process typically include IT security teams, cryptographic researchers, compliance officers, and executive leadership. Their collaboration is essential to ensure that the transition to quantum-safe systems is both effective and aligned with the organization’s strategic goals.
What to Watch Out For
While transitioning to quantum-safe strategies is critical, there are several limitations and trade-offs to consider:
- Compatibility Issues: existing systems may face compatibility challenges when integrating post-quantum algorithms, particularly older hardware (IoT, embedded devices, legacy VPN appliances) that cannot be updated remotely.
- Performance Trade-offs: ML-KEM and ML-DSA use larger keys and signatures than RSA/ECC, which can add latency or bandwidth overhead — this matters for high-throughput or constrained-device applications and should be tested, not assumed.
- Cost Implications: the research, development, and implementation of quantum-safe measures can be costly. Organizations must be prepared to allocate budget and resources effectively, which may strain smaller entities.
- Treating 2030 as “someone else’s deadline”: the federal deadline directly binds US agencies and their suppliers, but it is already reshaping what cloud providers, browsers, and enterprise software support by default — a business that waits until the deadline applies directly to it will be migrating under far more pressure than one that starts now, in hybrid mode, at its own pace.
- Overconfidence in Current Systems: some organizations may believe their existing security measures are sufficient to withstand quantum threats. This complacency can result in exposure that is not addressed in time, especially for the long-lived data described above.
It is essential for decision-makers to critically analyze these factors and develop a comprehensive strategy that addresses both the immediate and long-term implications of quantum computing on cybersecurity.
Frequently Asked Questions
Q: What is post-quantum cryptography?
A: Post-quantum cryptography is the set of cryptographic algorithms designed to remain secure even against an attacker with a quantum computer. Three such algorithms are now official US federal standards — FIPS 203, 204, and 205, finalized by NIST in August 2024 — not an experimental proposal.
Q: How soon should organizations start preparing for quantum threats?
A: Now, in hybrid mode. US federal agencies already face a December 31, 2030 deadline for encryption and December 31, 2031 for authentication under Executive Order 14412 (June 2026), and major infrastructure providers — Cloudflare, Google Chrome, Apple — have already deployed post-quantum protection in production rather than waiting for that date.
Q: Will all current encryption methods become obsolete with quantum computing?
A: Not all. Symmetric encryption (like AES-256) is considered largely resistant with a sufficiently long key. The algorithms at real risk are the ones based on factoring or discrete logarithms — chiefly RSA and ECC (ECDSA/ECDH) — which secure most of today’s TLS connections, VPNs, and digital signatures.
Q: Are there any regulations regarding quantum-safe practices?
A: Yes, and they are no longer proposals. NIST finalized FIPS 203/204/205 in August 2024, and the US Executive Order 14412 (June 2026) set binding 2030/2031 deadlines for federal systems. Businesses outside that direct mandate are affected indirectly, as their cloud providers, browsers, and software vendors adopt the same standards by default.
Want to know where you are exposed? We run a free security assessment — you get a written report on your exposure whether or not you work with us afterwards. For the wider risk picture beyond cryptography, see our cybersecurity services.
Related Articles
- Quantum Computing: Challenges and Changes in Cybersecurity
- What Is OT Cybersecurity? A 2026 Guide for Industry
- The AI Revolution in Modern Computing and Its Future
- AI: Revolution and Challenges in Modern Cybersecurity
Get our new articles by email
One email per article. Unsubscribe anytime.