Part 2 of 5

The Crypto
Threat
Explained

Two quantum algorithms — Shor's and Grover's — threaten the foundations of internet security. One breaks public-key cryptography entirely. The other halves the effective security of symmetric keys. And the threat isn't waiting for a quantum computer to be built.

Shor's impact
RSA ✗
all public-key systems based on factoring/DLP
Shor's impact
ECC ✗
elliptic-curve DH and signatures
Grover's impact
AES-256
128-bit effective PQ security — still safe
HNDL
Active
nation-states recording TLS today

Algorithm 1

Shor's Algorithm (1994)

Peter Shor's 1994 polynomial-time quantum algorithm for integer factorization and the discrete logarithm problem is the primary cryptographic threat. It does not merely speed up existing attacks — it fundamentally changes the complexity class.

What it solves

Shor's algorithm solves two related problems in polynomial time:

  • Integer factorization: Given N = p × q, find p and q. This is the basis of RSA security.
  • Discrete logarithm problem (DLP): Given g and g^x mod p, find x. This is the basis of Diffie-Hellman (DH), DSA, and — over elliptic curves — ECDH and ECDSA.

Classical complexity vs. quantum complexity

Classically, the best known algorithm for factoring an n-bit number is the General Number Field Sieve (GNFS), which runs in sub-exponential time O(exp(n^{1/3})). For RSA-2048, this requires roughly 2^112 operations — infeasible. Shor's algorithm factors the same number in O(n³) quantum operations — polynomial. The security assumption collapses entirely.

Which algorithms are broken

Algorithm Used for Classical security Post-quantum status
RSA-1024 / 2048 / 4096Key exchange, signatures, TLS80 / 112 / 140 bit✗ Broken — Shor's factors N
DH-2048 / DH-4096Key exchange (TLS, IKE)112 / 140 bit✗ Broken — Shor's solves DLP
DSA-2048Digital signatures112 bit✗ Broken — DLP
ECDH P-256 / P-384 / X25519TLS key exchange128 / 192 / 128 bit✗ Broken — ECDLP
ECDSA P-256 / Ed25519Signatures, TLS, code signing128 bit✗ Broken — ECDLP
🚨

Everything connected to the internet is at risk

HTTPS, SSH, VPN (IKEv2/IPsec), S/MIME email, code-signing certificates, PKI, JWT tokens using RS256/ES256, TLS client certificates, and X.509 certificate chains all rely on RSA or ECC. A CRQC renders every currently deployed public-key system broken simultaneously.

Algorithm 2

Grover's Algorithm (1996)

Lov Grover's 1996 algorithm provides a quadratic speedup for unstructured search. Given a black-box function f(x) = 1 for exactly one secret x, a classical computer needs O(N) evaluations to find x; Grover's algorithm needs O(√N).

Impact on symmetric cryptography

For symmetric ciphers and hash functions, the relevant attack is a brute-force key search over a keyspace of size 2^n. Grover's reduces this from 2^n to 2^{n/2}:

Algorithm Key / output size Classical security Grover-reduced security Verdict
AES-128128-bit key2^1282^64⚠ Weakened — borderline
AES-256256-bit key2^2562^128✓ Safe — 128-bit PQ security
ChaCha20-256256-bit key2^2562^128✓ Safe
SHA-256256-bit output2^256 preimage2^128 preimage⚠ Acceptable; upgrade to SHA-384 for margin
SHA-384 / SHA-512384 / 512-bit2^384 / 2^5122^192 / 2^256✓ Safe
SHA3-256 / SHA3-384256 / 384-bit2^256 / 2^3842^128 / 2^192✓ Safe (SHA3-256 marginal; prefer SHA3-384)

Practical note on Grover's

Unlike Shor's, Grover's speedup is quadratic, not exponential. Doubling the key length (e.g., AES-128 → AES-256) fully restores the security margin. The response to Grover's is straightforward: use AES-256, use SHA-384+, use longer HMAC keys. There is no need for exotic new symmetric algorithms.

Active threat

Harvest Now, Decrypt Later

The most operationally urgent threat does not require a quantum computer to exist today. It requires only that adversaries believe one will exist within the data's useful lifetime.

The attack model

A nation-state adversary intercepts and records encrypted traffic today — TLS handshakes, VPN sessions, encrypted emails, healthcare records, intellectual property transfers. The data is stored at scale. When a CRQC becomes available, the attacker decrypts it retroactively. The initial capture is cheap and persistent. The decryption capability is the only time-gated element.

Evidence of HNDL activity

Multiple US government advisories have confirmed that this threat model is credible and active. The NSA's 2022 CNSA 2.0 guidance explicitly states: "NSA is concerned about the threat of a 'harvest now, decrypt later' strategy." CISA's 2023 quantum-readiness guidance repeats this warning. Intelligence community assessments (unclassified versions) confirm nation-state adversaries are collecting encrypted data at scale.

What data is at risk

  • State secrets and classified communications (highest priority)
  • Financial transaction records, healthcare data, legal communications (long retention requirements)
  • Intellectual property in R&D, drug development, defense
  • Personal communications and metadata (surveillance targets)
  • Certificate authority private keys and HSM-protected secrets (if not air-gapped)

Today's TLS traffic is already a target

If your organization transmits long-lived sensitive data over HTTPS today, that data may already be captured and awaiting decryption. The migration window is not 2030–2040; it opened in approximately 2015 when Shor's became widely recognized as a future practical threat.

Planning framework

Mosca's Inequality

Michele Mosca formulated the key planning inequality that governs whether an organization is currently at risk:

X + Y > Z → at risk
X
Data lifetime
How long data must
remain confidential
Y
Migration time
Time to deploy
PQC across your systems
Z
Q-Day window
Time until a CRQC
is available

Applying the framework

Example: A financial institution holds transaction records that must remain confidential for 20 years (X = 20). Their legacy core banking system will take 8 years to migrate (Y = 8). If a CRQC arrives in 2033 (Z = 8 years from now), then X + Y = 28 > Z = 8: they are already at risk, and migration should have begun years ago.

Most enterprises estimating honestly will find they are in this position. That is why NIST, NSA, ENISA, and BSI all recommend beginning migration immediately, regardless of the precise CRQC timeline.

Full reference

Quantum-Vulnerable vs. Quantum-Safe Algorithms

Algorithm Category PQ status Recommended replacement
RSA (all key sizes)Asymmetric encryption / signatures✗ BrokenML-KEM ML-DSA
ECDH (all curves)Key exchange✗ BrokenML-KEM hybrid
ECDSA / Ed25519Digital signatures✗ BrokenML-DSA SLH-DSA
DH, DSAKey exchange / signatures✗ BrokenML-KEM ML-DSA
AES-128Symmetric cipher⚠ WeakenedUpgrade to AES-256
AES-256 / ChaCha20-256Symmetric cipher✓ SafeNo change needed
SHA-256 / HMAC-SHA-256Hash / MAC⚠ Reduced marginPrefer SHA-384 for new systems
SHA-384 / SHA-512 / SHA3-384Hash✓ SafeNo change needed
ML-KEM (FIPS 203)PQC KEM✓ Quantum-safe
ML-DSA (FIPS 204)PQC signatures✓ Quantum-safe
SLH-DSA (FIPS 205)PQC signatures✓ Quantum-safe

Next: PQC Algorithms & Standards

The NIST PQC standardization produced three finalized algorithms in 2024. Learn the mathematics behind them, the IETF and BSI standards landscape, and how they compare.

Algorithms & Standards →