<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Quantum Sequrity</title>
    <description>The latest articles on Forem by Quantum Sequrity (@quantumsequrity).</description>
    <link>https://forem.com/quantumsequrity</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3873995%2Fd357c939-4c0a-4b21-a1f1-c172252b4753.png</url>
      <title>Forem: Quantum Sequrity</title>
      <link>https://forem.com/quantumsequrity</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/quantumsequrity"/>
    <language>en</language>
    <item>
      <title>Why Quantum Computers Threaten Classical Encryption</title>
      <dc:creator>Quantum Sequrity</dc:creator>
      <pubDate>Tue, 28 Apr 2026 13:00:26 +0000</pubDate>
      <link>https://forem.com/quantumsequrity/why-quantum-computers-threaten-classical-encryption-459d</link>
      <guid>https://forem.com/quantumsequrity/why-quantum-computers-threaten-classical-encryption-459d</guid>
      <description>&lt;h1&gt;
  
  
  Why Quantum Computers Threaten Classical Encryption
&lt;/h1&gt;

&lt;p&gt;Education&lt;/p&gt;

&lt;h1&gt;
  
  
  Why Quantum Computers Threaten Classical Encryption
&lt;/h1&gt;

&lt;p&gt;12 min read&lt;/p&gt;

&lt;h2&gt;
  
  
  The Foundation of Modern Encryption
&lt;/h2&gt;

&lt;p&gt;Nearly every secure communication on the internet today relies on a small set of mathematical problems that are extraordinarily difficult for classical computers to solve. Online banking, email encryption, VPNs, HTTPS, code signing, and secure messaging all depend on the assumption that these problems will remain hard to crack. That assumption is about to be challenged.&lt;/p&gt;

&lt;p&gt;To understand the quantum threat, you first need to understand what classical encryption actually relies on. There are two major categories of hard problems at the heart of modern public-key cryptography:&lt;/p&gt;

&lt;h3&gt;
  
  
  Integer Factorization (RSA)
&lt;/h3&gt;

&lt;p&gt;RSA, the most widely deployed public-key algorithm, relies on the difficulty of factoring the product of two large prime numbers. Given two primes &lt;em&gt;p&lt;/em&gt; and &lt;em&gt;q&lt;/em&gt;, computing their product &lt;em&gt;n = p * q&lt;/em&gt; is trivial. But given only &lt;em&gt;n&lt;/em&gt;, finding &lt;em&gt;p&lt;/em&gt; and &lt;em&gt;q&lt;/em&gt; is computationally infeasible when &lt;em&gt;n&lt;/em&gt; is sufficiently large (2048 bits or more). The best known classical algorithms for factoring, such as the General Number Field Sieve, require sub-exponential time. For RSA-2048, this translates to an estimated computational effort that would take billions of years on the fastest supercomputers.&lt;/p&gt;

&lt;h3&gt;
  
  
  Discrete Logarithm Problem (DH, ECDH, ECDSA, DSA)
&lt;/h3&gt;

&lt;p&gt;Diffie-Hellman key exchange, elliptic curve Diffie-Hellman (ECDH), ECDSA, and DSA all rely on variants of the discrete logarithm problem. In the finite field setting, given a generator &lt;em&gt;g&lt;/em&gt;, a prime &lt;em&gt;p&lt;/em&gt;, and a value &lt;em&gt;g^x mod p&lt;/em&gt;, finding &lt;em&gt;x&lt;/em&gt; is computationally hard. The elliptic curve variant replaces modular arithmetic with operations on points of an elliptic curve, where finding the scalar multiplier from a known base point and result point is similarly intractable. ECC achieves equivalent security to RSA with much smaller key sizes: a 256-bit ECC key provides roughly the same security as a 3072-bit RSA key.&lt;/p&gt;

&lt;p&gt;These mathematical problems have served as the bedrock of internet security for decades. RSA was published in 1977. Diffie-Hellman was described in 1976. ECC gained widespread adoption in the 2000s. All of them share one critical vulnerability: they can be solved efficiently by a sufficiently powerful quantum computer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Shor's Algorithm: Breaking Public-Key Cryptography
&lt;/h2&gt;

&lt;p&gt;In 1994, mathematician Peter Shor published a quantum algorithm that factors integers and computes discrete logarithms in polynomial time. This was a theoretical bombshell. On a classical computer, factoring a 2048-bit number is practically impossible. On a quantum computer running Shor's algorithm, it becomes feasible.&lt;/p&gt;

&lt;p&gt;Shor's algorithm works by exploiting quantum mechanical properties, specifically superposition and entanglement, to find the period of a modular exponential function. Once the period is known, classical number theory can extract the prime factors. The key insight is that quantum computers can evaluate many possibilities simultaneously through superposition, and quantum interference amplifies the correct answers while canceling out wrong ones.&lt;/p&gt;

&lt;p&gt;What does "polynomial time" mean in practice? For factoring, the best classical algorithms run in sub-exponential time, roughly proportional to &lt;em&gt;e^(n^1/3)&lt;/em&gt; where &lt;em&gt;n&lt;/em&gt; is the bit length. Shor's algorithm runs in time proportional to &lt;em&gt;n^3&lt;/em&gt;. The difference is staggering. Doubling the key size from 2048 to 4096 bits makes classical factoring dramatically harder, but only modestly increases the work for Shor's algorithm.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What Shor's Algorithm Breaks&lt;/strong&gt;&lt;br&gt;
 RSA (all key sizes), DSA, ECDSA, ECDH, Diffie-Hellman, and any cryptosystem whose security depends on integer factorization or discrete logarithms. Increasing key sizes does not help: Shor's algorithm scales polynomially regardless of key length.&lt;/p&gt;

&lt;p&gt;It is important to be precise: Shor's algorithm requires a fault-tolerant quantum computer with a sufficient number of logical qubits. Current quantum computers are noisy and error-prone, with qubit counts in the low thousands. Running Shor's algorithm against RSA-2048 is estimated to require several thousand logical qubits, which in turn require millions of physical qubits due to error correction overhead. We are not there yet, but progress is steady.&lt;/p&gt;

&lt;h2&gt;
  
  
  Grover's Algorithm: Weakening Symmetric Encryption
&lt;/h2&gt;

&lt;p&gt;Published in 1996 by Lov Grover, Grover's algorithm provides a quadratic speedup for unstructured search problems. In the context of cryptography, this means a brute-force search over a key space of size &lt;em&gt;N&lt;/em&gt; takes only &lt;em&gt;sqrt(N)&lt;/em&gt; operations on a quantum computer instead of &lt;em&gt;N&lt;/em&gt; operations on a classical computer.&lt;/p&gt;

&lt;p&gt;The practical impact on symmetric encryption is straightforward: Grover's algorithm effectively halves the security level. AES-128, which provides 128 bits of security against classical attacks, provides only 64 bits of security against a quantum attacker. Sixty-four bits is well within brute-force range and therefore insecure.&lt;/p&gt;

&lt;p&gt;However, AES-256, with 256 bits of classical security, would still provide 128 bits of security against quantum attacks. 128 bits of security remains far beyond any feasible brute-force attack, classical or quantum. This is why the cryptographic community considers AES-256 to be quantum-safe, provided the key is properly generated and managed.&lt;/p&gt;

&lt;p&gt;The same logic applies to hash functions. SHA-256 provides 128 bits of collision resistance against quantum attackers (down from 128 bits classically, since collision search benefits from a different quantum speedup). SHA-3 and BLAKE3 with 256-bit outputs similarly remain secure. The general guidance is to double the output size of symmetric primitives to maintain the same security margin against quantum attacks.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which Algorithms Are Vulnerable?
&lt;/h2&gt;

&lt;p&gt;The quantum threat is not uniform. It specifically targets public-key (asymmetric) algorithms whose security is based on factoring or discrete logarithms. Here is the breakdown:&lt;/p&gt;

&lt;h3&gt;
  
  
  Broken by Quantum Computers
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;RSA&lt;/strong&gt; (all key sizes: 1024, 2048, 3072, 4096) -- integer factorization, broken by Shor's algorithm&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DSA&lt;/strong&gt; -- discrete logarithm in finite fields, broken by Shor's algorithm&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ECDSA&lt;/strong&gt; (P-256, P-384, P-521) -- elliptic curve discrete logarithm, broken by Shor's algorithm&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ECDH / X25519&lt;/strong&gt; -- elliptic curve Diffie-Hellman, broken by Shor's algorithm&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Diffie-Hellman&lt;/strong&gt; (classical, finite field) -- discrete logarithm, broken by Shor's algorithm&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ed25519 / Ed448&lt;/strong&gt; -- elliptic curve signatures, broken by Shor's algorithm&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Resistant to Quantum Computers (with sufficient key/output sizes)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;AES-256&lt;/strong&gt; -- 128-bit quantum security via Grover's, still considered safe&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AES-192&lt;/strong&gt; -- 96-bit quantum security, considered adequate&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SHA-3 (256-bit and above)&lt;/strong&gt; -- reduced but still sufficient security margins&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SHA-512&lt;/strong&gt; -- adequate collision resistance against quantum&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;BLAKE3 (256-bit output)&lt;/strong&gt; -- 128-bit quantum collision resistance&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;HMAC with 256-bit+ keys&lt;/strong&gt; -- unaffected by known quantum algorithms beyond Grover's&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The critical takeaway: symmetric algorithms and hash functions survive the quantum transition with larger key/output sizes. Public-key cryptography based on factoring or discrete logs does not survive at any key size. For a deeper introduction to the algorithms designed to replace them, see our guide on &lt;a href="https://quantumsequrity.com/blog/what-is-post-quantum-cryptography" rel="noopener noreferrer"&gt;what post-quantum cryptography is&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Timeline: When Will This Happen?
&lt;/h2&gt;

&lt;p&gt;Predicting when a cryptographically relevant quantum computer (CRQC) will exist is inherently uncertain. Estimates vary widely among experts:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Conservative estimates (15-20+ years):&lt;/strong&gt; Many physicists and engineers point to the enormous engineering challenges of building fault-tolerant quantum computers at scale. Error correction overhead, qubit stability, and manufacturing consistency remain fundamental obstacles.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Aggressive estimates (5-10 years):&lt;/strong&gt; Some researchers and industry leaders believe rapid advances in qubit quality, error correction codes, and hybrid architectures could accelerate timelines significantly. Quantum computing investment has grown substantially, with major programs funded by governments and technology companies worldwide.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The honest answer is that nobody knows for certain. But this uncertainty itself is part of the threat. NIST noted in its report on post-quantum cryptography (NIST IR 8105, published in 2016) that the transition to quantum-resistant algorithms would take years or decades to complete across the global IT infrastructure. Waiting for certainty about quantum computing timelines means starting the migration too late.&lt;/p&gt;

&lt;h2&gt;
  
  
  The "Harvest Now, Decrypt Later" Threat
&lt;/h2&gt;

&lt;p&gt;Even if large-scale quantum computers are a decade or more away, there is an immediate and concrete threat that exists today. It is called "Harvest Now, Decrypt Later" (HNDL), also known as "Store Now, Decrypt Later."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How HNDL Works&lt;/strong&gt;&lt;br&gt;
 An adversary intercepts and stores encrypted communications today, while they are still protected by classical encryption. The adversary archives this data and waits. When a sufficiently powerful quantum computer becomes available, they use Shor's algorithm to recover the encryption keys and decrypt everything they have collected. The data does not need to be valuable today. It only needs to be valuable when it is eventually decrypted.&lt;/p&gt;

&lt;p&gt;Consider what types of data remain sensitive for years or decades: classified government communications, long-term trade secrets, medical records, legal documents, financial data, intellectual property, and personal information subject to privacy regulations. All of this data, if encrypted today with RSA or ECC alone, is potentially harvestable.&lt;/p&gt;

&lt;p&gt;Nation-state intelligence agencies have the storage capacity, network access, and strategic motivation to conduct HNDL operations at scale. This is not speculative; multiple government cybersecurity agencies have publicly warned about this threat. We cover this topic in detail in our post on the &lt;a href="https://quantumsequrity.com/blog/harvest-now-decrypt-later" rel="noopener noreferrer"&gt;Harvest Now, Decrypt Later&lt;/a&gt; attack.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Organizations Must Act Now
&lt;/h2&gt;

&lt;p&gt;The argument for immediate action does not depend on quantum computers arriving tomorrow. It depends on three factors:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Migration Takes Years
&lt;/h3&gt;

&lt;p&gt;Transitioning an organization's cryptographic infrastructure is not a software update. It involves inventorying every system that uses public-key cryptography, updating protocols, replacing certificates, testing interoperability, and retraining staff. For large enterprises and government agencies, this process takes 5 to 15 years. NIST began its post-quantum cryptography standardization process in 2016, and the first standards (FIPS 203, FIPS 204, and FIPS 205) were finalized on August 13, 2024 -- an eight-year effort just for standardization alone.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Data Has a Long Shelf Life
&lt;/h3&gt;

&lt;p&gt;If your encrypted data needs to remain confidential for 10, 20, or 30 years, and a quantum computer could emerge within that window, then that data is already at risk. The protection window of your encryption must exceed the combined time until a quantum computer exists plus the time to actually perform the decryption. For many types of sensitive data, this calculation already fails.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Compliance Is Moving
&lt;/h3&gt;

&lt;p&gt;Regulatory and compliance frameworks are beginning to incorporate post-quantum requirements. Organizations that wait will face both security risk and compliance gaps. The U.S. government has already directed federal agencies to begin transitioning to post-quantum cryptography.&lt;/p&gt;

&lt;h2&gt;
  
  
  The NIST Post-Quantum Solution
&lt;/h2&gt;

&lt;p&gt;Recognizing the quantum threat, NIST launched its Post-Quantum Cryptography Standardization Process in 2016, evaluating submissions from researchers worldwide. After multiple rounds of analysis and public review, NIST finalized three standards on August 13, 2024:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;FIPS 203 (ML-KEM)&lt;/strong&gt; -- Module-Lattice Key Encapsulation Mechanism, replacing RSA/ECDH for key exchange. Based on the hardness of the Module Learning With Errors problem. See our detailed explanation of &lt;a href="https://quantumsequrity.com/blog/ml-kem-explained" rel="noopener noreferrer"&gt;how ML-KEM works&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;FIPS 204 (ML-DSA)&lt;/strong&gt; -- Module-Lattice Digital Signature Algorithm, replacing RSA/ECDSA/DSA for digital signatures. Also based on lattice problems.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;FIPS 205 (SLH-DSA)&lt;/strong&gt; -- Stateless Hash-Based Digital Signature Algorithm, providing a conservative alternative for signatures based purely on hash function security.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These algorithms are designed so that no known quantum algorithm can break them efficiently. Their security is based on mathematical problems (lattice problems for ML-KEM and ML-DSA, hash function properties for SLH-DSA) that are believed to be hard for both classical and quantum computers. For a complete walkthrough of these standards, see our &lt;a href="https://quantumsequrity.com/blog/nist-fips-guide" rel="noopener noreferrer"&gt;NIST FIPS 203/204/205 guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Hybrid Approach: Belt and Suspenders
&lt;/h2&gt;

&lt;p&gt;Because post-quantum algorithms are relatively new compared to classical algorithms that have been studied for decades, many security experts recommend a hybrid approach: combining a post-quantum algorithm with a classical algorithm so that the system remains secure even if one of them is broken.&lt;/p&gt;

&lt;p&gt;For example, combining ML-KEM (quantum-resistant) with X25519 (classically proven) for key exchange means an attacker must break both the lattice problem and the elliptic curve discrete logarithm problem. If quantum computers never materialize, X25519 provides tried-and-true security. If they do, ML-KEM provides the quantum resistance. Neither failure mode leaves data exposed.&lt;/p&gt;

&lt;p&gt;This is the approach QNSQY takes for all encryption operations. We discuss the rationale in depth in our post on &lt;a href="https://quantumsequrity.com/blog/hybrid-encryption" rel="noopener noreferrer"&gt;why hybrid encryption matters&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What You Should Do Today
&lt;/h2&gt;

&lt;p&gt;Regardless of when you believe quantum computers will arrive, the following steps reduce your risk:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Inventory your cryptographic dependencies.&lt;/strong&gt; Know which systems use RSA, ECC, DH, DSA, and similar algorithms. Identify where keys are exchanged, where signatures are verified, and where long-term secrets are stored.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prioritize data by sensitivity and lifespan.&lt;/strong&gt; Data that must remain confidential for 10+ years is at the highest risk from HNDL attacks and should be migrated first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Begin adopting post-quantum or hybrid encryption for new systems.&lt;/strong&gt; New deployments should use NIST-standardized algorithms (ML-KEM, ML-DSA) in hybrid mode with classical algorithms.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Encrypt stored data with quantum-resistant algorithms.&lt;/strong&gt; Files and archives encrypted today with RSA or ECC alone are vulnerable. Re-encrypting with hybrid PQC provides long-term protection.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Follow NIST guidance.&lt;/strong&gt; NIST IR 8105 and the FIPS 203/204/205 standards provide authoritative guidance on algorithm selection and migration planning.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;

&lt;p&gt;Classical public-key encryption, the kind that protects nearly all internet communications today, is built on mathematical problems that quantum computers can solve efficiently. Shor's algorithm breaks RSA, ECC, DH, and DSA. Grover's algorithm weakens symmetric encryption but does not break it at 256-bit key sizes. The timeline for a cryptographically relevant quantum computer is uncertain, but the "Harvest Now, Decrypt Later" threat means data encrypted today is already at risk. NIST has published new post-quantum standards to address this. The migration will take years. The time to start is now.&lt;/p&gt;

&lt;h3&gt;
  
  
  Sources
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/publications/detail/nistir/8105/final" rel="noopener noreferrer"&gt;NIST IR 8105 -- Report on Post-Quantum Cryptography (2016)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/projects/post-quantum-cryptography" rel="noopener noreferrer"&gt;NIST Post-Quantum Cryptography Standardization Process&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/fips/203/final" rel="noopener noreferrer"&gt;NIST FIPS 203 -- Module-Lattice-Based Key-Encapsulation Mechanism Standard (2024)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/fips/204/final" rel="noopener noreferrer"&gt;NIST FIPS 204 -- Module-Lattice-Based Digital Signature Standard (2024)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/fips/205/final" rel="noopener noreferrer"&gt;NIST FIPS 205 -- Stateless Hash-Based Digital Signature Standard (2024)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Shor, P. "Algorithms for Quantum Computation: Discrete Logarithms and Factoring." Proceedings of the 35th Annual Symposium on Foundations of Computer Science, 1994.&lt;/li&gt;
&lt;li&gt;Grover, L. "A Fast Quantum Mechanical Algorithm for Database Search." Proceedings of the 28th Annual ACM Symposium on Theory of Computing, 1996.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Related Articles
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/what-is-post-quantum-cryptography" rel="noopener noreferrer"&gt;What is Post-Quantum Cryptography?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/classical-vs-quantum-safe-encryption" rel="noopener noreferrer"&gt;Classical vs Quantum-Safe Encryption Compared&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/harvest-now-decrypt-later" rel="noopener noreferrer"&gt;Harvest Now, Decrypt Later Threat&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/quantum-computing-encryption-timeline" rel="noopener noreferrer"&gt;When Will Quantum Computers Break Encryption?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Protect Your Data Against Quantum Threats
&lt;/h3&gt;

&lt;p&gt;QNSQY uses ML-KEM + X25519 hybrid encryption by default, providing quantum resistance today.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://quantumsequrity.com/blog/why-quantum-threatens-classical-encryption" rel="noopener noreferrer"&gt;quantumsequrity.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>postquantumcryptography</category>
      <category>harvestnowdecryptlater</category>
      <category>cybersecurity</category>
      <category>security</category>
    </item>
    <item>
      <title>What is Post-Quantum Cryptography?</title>
      <dc:creator>Quantum Sequrity</dc:creator>
      <pubDate>Mon, 27 Apr 2026 13:00:49 +0000</pubDate>
      <link>https://forem.com/quantumsequrity/what-is-post-quantum-cryptography-m3b</link>
      <guid>https://forem.com/quantumsequrity/what-is-post-quantum-cryptography-m3b</guid>
      <description>&lt;h1&gt;
  
  
  What is Post-Quantum Cryptography?
&lt;/h1&gt;

&lt;p&gt;Education&lt;/p&gt;

&lt;h1&gt;
  
  
  What is Post-Quantum Cryptography?
&lt;/h1&gt;

&lt;p&gt;14 min read&lt;/p&gt;

&lt;h2&gt;
  
  
  What Cryptography Actually Protects
&lt;/h2&gt;

&lt;p&gt;Before we talk about "post-quantum" anything, it helps to understand what cryptography does for you right now, every single day, without you ever thinking about it.&lt;/p&gt;

&lt;p&gt;When you check your bank balance on your phone, cryptography prevents the person sitting next to you at the coffee shop from seeing your account number. When your doctor sends your blood test results to a specialist, cryptography keeps that data private as it crosses the internet. When a company stores its customer database, cryptography makes sure that a hacker who steals the hard drive gets a pile of unreadable noise instead of millions of credit card numbers.&lt;/p&gt;

&lt;p&gt;Cryptography is not just about passwords or spy movies. It protects banking transactions (trillions of dollars per day flow through encrypted channels), medical records (governed by laws like HIPAA in the US and GDPR in Europe), government communications (military orders, diplomatic cables, intelligence reports), legal documents (attorney-client privilege relies on encrypted email and storage), and personal data (your photos, messages, browsing history, and location data).&lt;/p&gt;

&lt;p&gt;All of this protection depends on mathematical problems that are very hard for computers to solve. The entire system works because breaking the math would take a conventional computer longer than the age of the universe. Post-quantum cryptography exists because quantum computers threaten to change that equation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key Point:&lt;/strong&gt; Post-quantum cryptography runs on regular computers today. You do not need a quantum computer to use it. You need it to defend against quantum computers.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Quantum Computers Actually Change
&lt;/h2&gt;

&lt;p&gt;A quantum computer is not just a faster version of your laptop. It works on fundamentally different principles. Where a classical computer stores information as bits (each bit is either 0 or 1), a quantum computer uses qubits, which can exist in a superposition of both 0 and 1 simultaneously. This allows quantum computers to explore many possible solutions at the same time, rather than checking them one by one.&lt;/p&gt;

&lt;p&gt;For most everyday tasks (browsing the web, editing documents, playing games), quantum computers offer no advantage. They are not universally faster. But for certain very specific mathematical problems, they are devastatingly effective.&lt;/p&gt;

&lt;p&gt;The two quantum algorithms that matter for cryptography are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Shor's Algorithm (1994)&lt;/strong&gt;: This can factor large numbers and compute discrete logarithms exponentially faster than any known classical algorithm. RSA, ECDH, DSA, and every other widely-used public-key algorithm today relies on one of these two problems. Shor's algorithm breaks all of them. An RSA-2048 key that would take a classical supercomputer 300 trillion years to break could fall in hours on a sufficiently large quantum computer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Grover's Algorithm (1996)&lt;/strong&gt;: This provides a quadratic speedup for unstructured search problems. It effectively halves the security of symmetric algorithms like AES. AES-256, which has 256-bit security against classical computers, would have 128-bit security against a quantum attacker. 128-bit security is still considered strong enough to be safe, so &lt;strong&gt;AES-256 does not need to be replaced&lt;/strong&gt;. The threat is specifically to public-key algorithms.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The critical distinction: Shor's algorithm does not just speed up existing attacks. It fundamentally changes the game. Problems that were computationally impossible become easy. This is why we cannot simply use bigger RSA keys. No matter how large you make the key, Shor's algorithm scales to crack it. We need entirely different math.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Three Families of Post-Quantum Cryptography
&lt;/h2&gt;

&lt;p&gt;Post-quantum cryptography (PQC) uses mathematical problems that remain hard even for quantum computers. There are three major families, each based on different math. This diversity is important: if one family turns out to have an unexpected weakness, the others provide backup.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Lattice-Based Cryptography
&lt;/h3&gt;

&lt;p&gt;This is the most widely adopted family and includes the primary NIST standards (ML-KEM for encryption, ML-DSA for signatures). Lattice problems involve finding short or close vectors in high-dimensional geometric structures called lattices.&lt;/p&gt;

&lt;p&gt;Think of a lattice as a grid of evenly spaced points, like the intersections on graph paper. In two dimensions, you can easily see the pattern and find the closest point to any location. But extend this to hundreds or thousands of dimensions, and the problem becomes extraordinarily difficult. No known quantum algorithm provides a significant speedup for lattice problems.&lt;/p&gt;

&lt;p&gt;The specific problem used by ML-KEM is called "Module Learning With Errors" (Module-LWE). You are given a system of approximate equations (equations with small random errors added) and need to recover the hidden variables. The added noise makes this problem brutally hard in high dimensions. Lattice-based algorithms are fast and produce reasonably compact keys, which is why they won the NIST competition.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Code-Based Cryptography
&lt;/h3&gt;

&lt;p&gt;Code-based cryptography uses error-correcting codes, the same mathematical structures used to fix transmission errors in wireless communications, satellite links, and data storage. The hard problem is "decoding a random linear code." You are given a noisy codeword and must figure out the original message, but without knowing the specific error-correcting structure that was used to encode it. This problem has been studied since the 1970s (the McEliece cryptosystem dates to 1978) and remains hard for quantum computers.&lt;/p&gt;

&lt;p&gt;NIST selected HQC (Hamming Quasi-Cyclic) as a backup standard for key encapsulation. Code-based algorithms tend to have larger key sizes than lattice-based ones, but they offer cryptographic diversity. If lattice problems are somehow broken, code-based alternatives provide a safety net.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Hash-Based Signatures
&lt;/h3&gt;

&lt;p&gt;Hash-based signatures are the most conservative approach. Their security depends only on the properties of hash functions (like SHA-3), which are well-understood and have been studied for decades. NIST standardized SLH-DSA (based on SPHINCS+) as FIPS 205 for exactly this reason: even if lattice math turns out to have unforeseen weaknesses, hash-based signatures remain secure.&lt;/p&gt;

&lt;p&gt;The trade-off is that hash-based signatures are larger (tens of kilobytes per signature) and slower to generate than lattice-based signatures. They serve as a critical backup rather than a primary choice for high-volume operations.&lt;/p&gt;

&lt;h2&gt;
  
  
  The NIST Standardization Process
&lt;/h2&gt;

&lt;p&gt;The standards for post-quantum cryptography did not come from a single company or research lab. They emerged from one of the most thorough and transparent evaluation processes in the history of cryptography.&lt;/p&gt;

&lt;p&gt;In 2016, NIST (the U.S. National Institute of Standards and Technology) published a call for proposals. They asked the global cryptography community to submit algorithms that could resist quantum computers. Eighty-two teams from universities, government labs, and private companies worldwide responded.&lt;/p&gt;

&lt;p&gt;Over the next eight years, NIST ran three rounds of public evaluation. During each round, cryptographers worldwide tried to break the submitted algorithms. They published papers, presented attacks, and debated trade-offs. Algorithms that showed weaknesses were eliminated. After Round 1 (2017-2019), 26 algorithms advanced. After Round 2 (2019-2020), 15 survived. After Round 3 (2020-2022), NIST selected the winners.&lt;/p&gt;

&lt;p&gt;In August 2024, NIST published the first three final standards:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Standard&lt;/th&gt;
&lt;th&gt;Algorithm (Original Name)&lt;/th&gt;
&lt;th&gt;Family&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;FIPS 203&lt;/td&gt;
&lt;td&gt;ML-KEM (CRYSTALS-Kyber)&lt;/td&gt;
&lt;td&gt;Lattice&lt;/td&gt;
&lt;td&gt;Key encapsulation (establishing shared secrets)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;FIPS 204&lt;/td&gt;
&lt;td&gt;ML-DSA (CRYSTALS-Dilithium)&lt;/td&gt;
&lt;td&gt;Lattice&lt;/td&gt;
&lt;td&gt;Digital signatures (proving identity and integrity)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;FIPS 205&lt;/td&gt;
&lt;td&gt;SLH-DSA (SPHINCS+)&lt;/td&gt;
&lt;td&gt;Hash-based&lt;/td&gt;
&lt;td&gt;Digital signatures (conservative backup)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Additional standards are in progress. FIPS 206 (draft) (FN-DSA, based on FALCON) covers lattice-based signatures with smaller signature sizes. NIST also selected HQC as a backup key encapsulation mechanism from the code-based family, providing algorithm diversity. The selection of algorithms from multiple mathematical families is a deliberate strategy: if one family of math turns out to be weaker than expected, the others still provide protection.&lt;/p&gt;

&lt;h2&gt;
  
  
  Post-Quantum vs. Quantum Cryptography
&lt;/h2&gt;

&lt;p&gt;These two terms sound similar but refer to completely different things. Confusing them is one of the most common mistakes people make.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Term&lt;/th&gt;
&lt;th&gt;What It Is&lt;/th&gt;
&lt;th&gt;Hardware Required&lt;/th&gt;
&lt;th&gt;Practical Today?&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Post-Quantum Cryptography&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Software algorithms that run on regular computers, using math that quantum computers cannot crack&lt;/td&gt;
&lt;td&gt;Your existing laptop, phone, or server&lt;/td&gt;
&lt;td&gt;Yes. NIST standards published. Widely deployed.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Quantum Cryptography (QKD)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Uses quantum physics (individual photons) to distribute keys. An eavesdropper disturbs the quantum state, alerting the parties.&lt;/td&gt;
&lt;td&gt;Specialized quantum hardware, fiber optic links, single-photon detectors&lt;/td&gt;
&lt;td&gt;Limited. Point-to-point only. Very expensive. Cannot protect stored data.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Post-quantum cryptography is what you can use right now, on your existing hardware, to protect your files and communications. It is a software solution. Quantum Key Distribution (QKD) is a physics experiment that works over short distances between specialized equipment. QKD cannot protect a file sitting on your hard drive, cannot work over the general internet, and costs orders of magnitude more than software-based solutions.&lt;/p&gt;

&lt;h2&gt;
  
  
  How We Got Here: A Brief History
&lt;/h2&gt;

&lt;p&gt;The story of post-quantum cryptography begins with a single paper. In 1994, mathematician Peter Shor, then at AT&amp;amp;T Bell Labs, published "Algorithms for Quantum Computation: Discrete Logarithms and Factoring." This paper demonstrated that a quantum computer could factor large integers and compute discrete logarithms in polynomial time. The implications were staggering: RSA, Diffie-Hellman, and all elliptic curve cryptography would be broken.&lt;/p&gt;

&lt;p&gt;At the time, quantum computers were purely theoretical. No one had built one that could run Shor's algorithm on anything larger than trivially small numbers. But cryptographers recognized that if large quantum computers were ever built, the consequences for global security would be catastrophic. Every encrypted communication in the world would become retroactively vulnerable.&lt;/p&gt;

&lt;p&gt;Research into "quantum-resistant" or "post-quantum" algorithms began almost immediately. Lattice-based cryptography, one of the primary post-quantum approaches, draws on mathematical work dating back to the 1990s. The Ajtai-Dwork cryptosystem (1997) and the NTRU encryption scheme (1998) were among the earliest practical proposals. Code-based cryptography is even older; the McEliece cryptosystem dates to 1978, predating the quantum threat by 16 years.&lt;/p&gt;

&lt;p&gt;For the next two decades, post-quantum cryptography remained an active but niche research area. That changed in 2016, when NIST issued its formal call for proposals. The eight-year evaluation that followed brought post-quantum cryptography from the academic realm into the world of international standards. The publication of FIPS 203, 204, and 205 in August 2024 marked the transition from research to deployment.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Hybrid Approach: Belt and Suspenders
&lt;/h2&gt;

&lt;p&gt;Most security organizations recommend using post-quantum algorithms &lt;strong&gt;alongside&lt;/strong&gt; classical algorithms, not as a replacement. This is called the "hybrid" approach, and it is the most conservative strategy available.&lt;/p&gt;

&lt;p&gt;The logic is simple. Classical algorithms like X25519 have been studied for over 15 years and deployed in billions of devices. We are extremely confident they are secure against regular computers. Post-quantum algorithms like ML-KEM have passed rigorous evaluation and are believed to be secure against quantum computers, but they are newer and have seen less real-world deployment.&lt;/p&gt;

&lt;p&gt;By combining both, you get protection that is at least as strong as the stronger of the two. If ML-KEM has a hidden flaw, X25519 still protects your data against classical attackers. If a quantum computer breaks X25519, ML-KEM still protects your data against quantum attackers. An adversary must break both to succeed.&lt;/p&gt;

&lt;p&gt;NIST published specific guidance on hybrid approaches in SP 800-227. QNSQY implements this approach in every encryption: ML-KEM + X25519 for key encapsulation, ML-DSA + Ed25519 for digital signatures. Both key components are fed into a key derivation function so that the final encryption key depends on both algorithms being secure.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Myths About the Quantum Threat
&lt;/h2&gt;

&lt;h3&gt;
  
  
  "Quantum computers are decades away, so this is not urgent"
&lt;/h3&gt;

&lt;p&gt;The quantum computer itself may be decades away, but the threat is already here. The "harvest now, decrypt later" strategy means adversaries can record encrypted data today and store it until quantum computers can decrypt it. If your data must remain secret for 15 years, and a quantum computer arrives in 15 years, you needed quantum-safe encryption yesterday. NIST began the standardization process in 2016 specifically because cryptographic transitions take many years. Waiting until quantum computers exist would leave a multi-year gap during which all encrypted data is retroactively vulnerable.&lt;/p&gt;

&lt;h3&gt;
  
  
  "We can just use bigger RSA keys"
&lt;/h3&gt;

&lt;p&gt;Shor's algorithm breaks RSA in polynomial time. This means the attack scales efficiently regardless of key size. Doubling the RSA key size does not double the difficulty for a quantum attacker. It adds only a modest increase to the computation time. There is no RSA key size large enough to resist a quantum computer running Shor's algorithm. The mathematical structure that makes RSA work is the same structure that makes it vulnerable. The only solution is different math entirely, which is what post-quantum algorithms provide.&lt;/p&gt;

&lt;h3&gt;
  
  
  "AES-256 is enough"
&lt;/h3&gt;

&lt;p&gt;AES-256 is quantum-safe as an encryption algorithm. Grover's algorithm only reduces its effective security from 256 bits to 128 bits, which is still strong. But AES-256 is a symmetric cipher. Both the sender and receiver must already possess the same secret key. The hard part is establishing that shared key over an insecure channel. This is where RSA, ECDH, and other public-key algorithms come in, and these are the algorithms that quantum computers break. ML-KEM replaces the quantum-vulnerable key agreement step. AES-256 handles the actual data encryption. They solve different problems and are both necessary.&lt;/p&gt;

&lt;h3&gt;
  
  
  "Only governments need to worry about this"
&lt;/h3&gt;

&lt;p&gt;Government agencies are the most obvious targets, but healthcare organizations hold patient data that must remain confidential for decades under HIPAA. Law firms hold attorney-client privileged communications with no expiration date. Financial institutions hold transaction data and account information that criminals can monetize. Pharmaceutical companies hold drug research data worth billions. Any organization with long-lived sensitive data faces the same fundamental risk.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Should You Do About It?
&lt;/h2&gt;

&lt;p&gt;The urgency of switching to post-quantum cryptography depends on how long your data needs to stay secret. Think about three questions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;How long does this data need to remain confidential?&lt;/strong&gt; Medical records might be sensitive for 50+ years. A corporate strategy document might matter for 5 years. A credit card number expires in 3 years.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How soon could a quantum computer break current encryption?&lt;/strong&gt; Expert estimates range from 10 to 20 years, though some believe it could happen sooner.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Could someone be recording this data now to decrypt later?&lt;/strong&gt; Nation-state intelligence agencies have both the motivation and the storage capacity to do this.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If the sensitivity lifetime of your data exceeds the expected arrival of quantum computers, you should already be using post-quantum cryptography. For most sensitive data (medical records, legal documents, government secrets, long-term business plans), the math says the time to switch is now.&lt;/p&gt;

&lt;p&gt;Practically, transitioning does not have to be painful. Tools like &lt;a href="https://quantumsequrity.com/blog/quantum-encryption-software" rel="noopener noreferrer"&gt;QNSQY&lt;/a&gt; use post-quantum algorithms by default, with no configuration required. You encrypt a file, and it automatically receives ML-KEM + X25519 hybrid protection. The free tier provides full post-quantum encryption with ML-KEM-512.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Performance Question
&lt;/h2&gt;

&lt;p&gt;A common concern about post-quantum cryptography is performance. Post-quantum algorithms generally have larger keys and signatures than their classical counterparts. An ML-KEM-768 public key is 1,184 bytes, compared to 32 bytes for X25519. An ML-DSA-65 signature is 3,293 bytes, compared to 64 bytes for Ed25519.&lt;/p&gt;

&lt;p&gt;However, the computational speed tells a different story. ML-KEM key generation and encapsulation are faster than RSA operations at comparable security levels. On modern hardware, an ML-KEM-768 encapsulation takes approximately 40 microseconds. AES-256-GCM data encryption, which runs at several gigabytes per second on hardware with AES-NI support, dominates the total encryption time for any file larger than a few kilobytes. The post-quantum key agreement step is a one-time cost per encryption, and it is negligible compared to the data encryption itself.&lt;/p&gt;

&lt;p&gt;For network protocols like TLS, the larger key sizes add bytes to the handshake, but real-world deployments (Google Chrome, Cloudflare) have confirmed that the impact on page load times is imperceptible to users. The additional 1-2 kilobytes in the TLS handshake are absorbed within the noise of normal network latency.&lt;/p&gt;

&lt;p&gt;For data encryption specifically, the overhead is even less significant. QNSQY stores the ML-KEM ciphertext and X25519 public key in the file header, adding roughly 1,200 bytes to the total file size. For a 1 MB file, that is 0.12% overhead. For a 100 MB file, it rounds to zero.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/fips/203/final" rel="noopener noreferrer"&gt;NIST FIPS 203: Module-Lattice-Based Key-Encapsulation Mechanism Standard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/fips/204/final" rel="noopener noreferrer"&gt;NIST FIPS 204: Module-Lattice-Based Digital Signature Standard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/fips/205/final" rel="noopener noreferrer"&gt;NIST FIPS 205: Stateless Hash-Based Digital Signature Standard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/publications/detail/nistir/8105/final" rel="noopener noreferrer"&gt;NIST IR 8105: Report on Post-Quantum Cryptography&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/projects/post-quantum-cryptography" rel="noopener noreferrer"&gt;NIST Post-Quantum Cryptography Standardization Project&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Related Articles
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/ml-kem-explained" rel="noopener noreferrer"&gt;ML-KEM: Future of Key Encapsulation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/why-quantum-threatens-classical-encryption" rel="noopener noreferrer"&gt;Why Quantum Computers Threaten Classical Encryption&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/nist-fips-guide" rel="noopener noreferrer"&gt;NIST FIPS 203/204/205: The Complete Guide&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/harvest-now-decrypt-later" rel="noopener noreferrer"&gt;Harvest Now, Decrypt Later Threat&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://quantumsequrity.com/blog/security" rel="noopener noreferrer"&gt;Learn More About Security&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://quantumsequrity.com/blog/what-is-post-quantum-cryptography" rel="noopener noreferrer"&gt;quantumsequrity.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cryptography</category>
      <category>postquantum</category>
      <category>quantumsafe</category>
    </item>
    <item>
      <title>Shor's Algorithm in Plain English: How Quantum Breaks RSA and Why Post Quantum Cryptography Replaces It</title>
      <dc:creator>Quantum Sequrity</dc:creator>
      <pubDate>Sun, 26 Apr 2026 17:53:03 +0000</pubDate>
      <link>https://forem.com/quantumsequrity/shors-algorithm-in-plain-english-how-quantum-breaks-rsa-and-why-post-quantum-cryptography-420n</link>
      <guid>https://forem.com/quantumsequrity/shors-algorithm-in-plain-english-how-quantum-breaks-rsa-and-why-post-quantum-cryptography-420n</guid>
      <description>&lt;h1&gt;
  
  
  Shor's Algorithm in Plain English: How Quantum Breaks RSA and Why Post Quantum Cryptography Replaces It
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Category&lt;/strong&gt;: Education&lt;/p&gt;

&lt;h1&gt;
  
  
  Shor's Algorithm in Plain English: How Quantum Breaks RSA and Why Post Quantum Cryptography Replaces It
&lt;/h1&gt;

&lt;p&gt;11 min read&lt;/p&gt;

&lt;h2&gt;
  
  
  The One Paragraph Version
&lt;/h2&gt;

&lt;p&gt;Shor's algorithm is a quantum program, written in 1994 by mathematician Peter W. Shor, that can factor large numbers and solve discrete logarithms exponentially faster than any known classical algorithm. RSA, Diffie-Hellman, and Elliptic Curve Cryptography (ECC, including ECDSA and Ed25519) all rely on the assumption that these math problems are intractable for a normal computer. Shor's algorithm shows that a sufficiently large quantum computer would solve them in hours, not the billions of years current encryption assumes. That is why the world needs Post Quantum Cryptography (PQC), and why NIST finalized FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA) on August 13, 2024.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why RSA Works Today (And Why It Will Not Tomorrow)
&lt;/h2&gt;

&lt;p&gt;RSA encrypts data by picking two large prime numbers, multiplying them to get a big composite number N, and using N as part of a public key. If an attacker can factor N back into those two primes, they can read every message encrypted with the key. The best classical algorithm we know, the General Number Field Sieve, takes sub-exponential time. On a laptop, factoring a 2048-bit RSA key would take longer than the age of the universe.&lt;/p&gt;

&lt;p&gt;Shor's algorithm changes the equation. It reduces factoring to a problem called &lt;strong&gt;period finding&lt;/strong&gt;, which a quantum computer can solve efficiently using the quantum Fourier transform. The polynomial time cost (roughly cubic in the number of bits) means doubling the RSA key size does not double the attack time, it merely adds a modest amount. There is no RSA key size that survives Shor.&lt;/p&gt;

&lt;h2&gt;
  
  
  Discrete Logarithms: The Same Story for Diffie-Hellman and ECC
&lt;/h2&gt;

&lt;p&gt;Diffie-Hellman key exchange and the entire Elliptic Curve Cryptography family (ECDH, ECDSA, Ed25519, X25519) rely on a problem called the &lt;strong&gt;discrete logarithm problem&lt;/strong&gt;. Given the result of modular exponentiation, find the exponent. On classical machines, this is hard. Shor's algorithm cracks it in the same polynomial time as factoring.&lt;/p&gt;

&lt;p&gt;This is why the cryptographic community cannot "just pick a bigger curve" to survive quantum. The math that makes elliptic curves efficient is the same math that makes them vulnerable.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Actual Mechanics, Without the Math
&lt;/h2&gt;

&lt;p&gt;Skipping the linear algebra, Shor's algorithm works in three phases:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Reduce the problem to period finding.&lt;/strong&gt; Factoring N is equivalent to finding the period of a particular function f(x) that involves modular exponentiation of a random base.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run the period finder on a quantum computer.&lt;/strong&gt; Prepare a superposition over many inputs, apply f(x) in parallel across the entire superposition, then apply the quantum Fourier transform to extract the period.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Classical post-processing.&lt;/strong&gt; A small amount of classical math converts the period into the factors of N.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The heavy lifting, the part that would crush any classical computer, happens in step 2. This is where quantum's exponential speedup lives.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Big a Quantum Computer Do You Need?
&lt;/h2&gt;

&lt;p&gt;This is the critical question for post-quantum timing. Estimates for breaking RSA-2048 with Shor range widely. A well-cited 2021 analysis by Craig Gidney and Martin Ekera (arXiv:1905.09749) estimates around &lt;strong&gt;20 million noisy physical qubits&lt;/strong&gt; for a day-scale attack, with specific assumptions about error-corrected code distance.&lt;/p&gt;

&lt;p&gt;For comparison, the largest quantum processors publicly announced as of April 2026 are:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;System&lt;/th&gt;
&lt;th&gt;Qubits&lt;/th&gt;
&lt;th&gt;Type&lt;/th&gt;
&lt;th&gt;Cryptographically relevant?&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;IBM Condor (Dec 2023)&lt;/td&gt;
&lt;td&gt;1,121&lt;/td&gt;
&lt;td&gt;Superconducting&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google Willow (Dec 2024)&lt;/td&gt;
&lt;td&gt;105&lt;/td&gt;
&lt;td&gt;Superconducting&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Zuchongzhi 3.0 (Mar 2025)&lt;/td&gt;
&lt;td&gt;105&lt;/td&gt;
&lt;td&gt;Superconducting&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Atom Computing (Oct 2023)&lt;/td&gt;
&lt;td&gt;1,180&lt;/td&gt;
&lt;td&gt;Neutral atom&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;None of these can run Shor on a real RSA key. The Global Risk Institute 2025 expert survey puts the likelihood of a cryptographically relevant quantum computer within 10 years between 28 percent (pessimistic) and 49 percent (optimistic), the highest 10-year estimate in the survey's seven-year history.&lt;/p&gt;

&lt;h2&gt;
  
  
  What PQC Does Instead
&lt;/h2&gt;

&lt;p&gt;Post Quantum Cryptography uses mathematical problems that neither classical nor quantum computers are known to solve efficiently. The standardized families are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Lattice-based&lt;/strong&gt; (ML-KEM, ML-DSA, FN-DSA). Relies on the Learning With Errors and related problems on high-dimensional lattices.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hash-based&lt;/strong&gt; (SLH-DSA, LMS). Relies only on the security of the underlying hash function.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Code-based&lt;/strong&gt; (HQC, Classic McEliece). Relies on the hardness of decoding random linear codes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each family uses a different hard problem, giving defense in depth against a future mathematical breakthrough in any one family.&lt;/p&gt;

&lt;h2&gt;
  
  
  What You Should Do About It
&lt;/h2&gt;

&lt;p&gt;If you are running a system that needs to protect data for more than a few years, the answer is hybrid PQC. Combine a classical algorithm like X25519 with a post-quantum algorithm like ML-KEM. An attacker must break both, not either, to read your data. Signal deployed this approach in September 2023 with PQXDH. Google Chrome shipped it by default in Chrome 131 in November 2024. Cloudflare reports over 60 percent of human-initiated TLS traffic now uses hybrid ML-KEM.&lt;/p&gt;

&lt;h2&gt;
  
  
  Frequently Asked Questions
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Frequently Asked Questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  When did Peter Shor publish Shor's algorithm?
&lt;/h3&gt;

&lt;p&gt;Peter W. Shor's algorithm was presented at the 35th Annual Symposium on Foundations of Computer Science (FOCS) in November 1994, with an expanded journal version appearing in SIAM Journal on Computing 26(5) in 1997.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does Shor's algorithm break symmetric encryption like AES?
&lt;/h3&gt;

&lt;p&gt;No. Shor's algorithm attacks public-key cryptography that relies on integer factorization or discrete logarithms. Symmetric ciphers like AES are affected by Grover's algorithm, which provides only a quadratic speedup, effectively halving the key strength. AES-256 remains secure even in a post-quantum world.&lt;/p&gt;

&lt;h3&gt;
  
  
  How many qubits are needed to run Shor on RSA-2048?
&lt;/h3&gt;

&lt;p&gt;Estimates vary widely. Craig Gidney and Martin Ekera's 2021 analysis (arXiv:1905.09749) estimates approximately 20 million noisy physical qubits for a day-scale attack. The exact number depends on error correction assumptions and implementation choices. As of April 2026 no quantum computer approaches this scale.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is hybrid PQC slower than classical encryption?
&lt;/h3&gt;

&lt;p&gt;The overhead is small. ML-KEM-768 hybrid with X25519 adds roughly 1 to 2 kilobytes per TLS handshake and a handful of milliseconds of CPU time. For most applications this is unmeasurable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;a href="https://ieeexplore.ieee.org/document/365700/" rel="noopener noreferrer"&gt;Shor, P. W. (1994). Algorithms for quantum computation. FOCS proceedings&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://arxiv.org/abs/quant-ph/9508027" rel="noopener noreferrer"&gt;Shor arXiv preprint (1995)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://arxiv.org/abs/1905.09749" rel="noopener noreferrer"&gt;Gidney &amp;amp; Ekera (2021). How to factor 2048-bit RSA in 8 hours&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://csrc.nist.gov/pubs/fips/203/final" rel="noopener noreferrer"&gt;NIST FIPS 203 (ML-KEM) Final&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://globalriskinstitute.org/publication/quantum-threat-timeline-2025-executive-perspectives-on-barriers-to-action/" rel="noopener noreferrer"&gt;Global Risk Institute Quantum Threat Timeline 2025&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Related Articles
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/grover-algorithm-explained-layman" rel="noopener noreferrer"&gt;Grover's Algorithm Explained&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/ml-kem-explained" rel="noopener noreferrer"&gt;ML-KEM Explained (FIPS 203)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/why-rsa-2048-will-break" rel="noopener noreferrer"&gt;Why RSA-2048 Will Break&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/hybrid-encryption" rel="noopener noreferrer"&gt;Why Hybrid Encryption Matters&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://quantumsequrity.com/blog/what-is-post-quantum-cryptography" rel="noopener noreferrer"&gt;What is Post-Quantum Cryptography?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;
  
  
  Protect Your Data Before Q-Day Arrives
&lt;/h3&gt;

&lt;p&gt;QNSQY's NIST-standardized post-quantum encryption protects files against both current and quantum-era threats.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://quantumsequrity.com/blog/shor-algorithm-explained-layman" rel="noopener noreferrer"&gt;quantumsequrity.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cryptography</category>
      <category>postquantum</category>
      <category>quantumsafe</category>
    </item>
  </channel>
</rss>
