
Imagine a financial institution or a healthcare provider backing up its encrypted customer records and proprietary research across a public cloud link. Every packet is wrapped in TLS 1.3 using Elliptic Curve Diffie-Hellman (ECDH) and RSA-2048 signatures. By every traditional security metric, the traffic is unreadable, compliant, and safe.
Yet an adversary sitting on a compromised transit node or tapping an undersea fiber cable is quietly copying those encrypted payloads to a massive storage cluster. They cannot read a single byte of that data today. They do not need to. They are simply waiting for a Cryptographically Relevant Quantum Computer (CRQC) to come online, at which point yesterday's intercepted ciphertext becomes plain text.
This strategy is known as a "Harvest Now, Decrypt Later" (HNDL) attack, and it changes the math of enterprise risk management. Because data stolen today can be exposed years from now, post-quantum cryptography (PQC) is no longer a theoretical research topic for physicists. For CISOs and enterprise architects, the transition has already begun.
Modern public-key cryptography relies on mathematical problems that are easy to compute in one direction but practically impossible for classical computers to reverse. RSA relies on the difficulty of factoring large prime numbers, while Elliptic Curve Cryptography (ECC) depends on the elliptic curve discrete logarithm problem. A classical supercomputer would need millions of years to break a properly implemented RSA-2048 key.
Quantum computers operate on fundamentally different physics. Using quantum bits (qubits) and algorithms such as Shor's algorithm, a sufficiently powerful fault-tolerant quantum computer can solve prime factorization and discrete logarithms exponentially faster than any classical machine. Once a CRQC reaches sufficient scale and error-correction stability, asymmetric encryption protocols like RSA, ECDH, and ECDSA will collapse completely.
In a Harvest Now, Decrypt Later campaign, threat actors intercept and archive encrypted traffic, VPN sessions, database backups, and intellectual property today with the explicit goal of decrypting them once quantum hardware matures.
Security architects evaluate this urgency using Mosca's Theorem, which compares three timelines:
If X + Y > Z, your organization is already exposed. Even if a large-scale quantum computer does not arrive until the early 2030s, any data with a 10-year confidentiality requirement transmitted today is at immediate risk if your migration takes several years to complete.
For years, enterprise IT teams postponed quantum readiness because cryptographic standards were still in flux. That excuse no longer holds.
In August 2024, the U.S. National Institute of Standards and Technology (NIST) finalized its first three core post-quantum cryptographic standards:
In October 2026, NIST reinforced these standards by releasing NIST IR 8547 (Transition to Post-Quantum Cryptography Standards), which establishes clear deprecation timelines for quantum-vulnerable algorithms and recommends ML-KEM-768 as the baseline parameter set for general key establishment. Meanwhile, additional backup standards such as FN-DSA (FIPS 206, based on Falcon) and HQC (a code-based key encapsulation mechanism) are advancing through final standardization to ensure long-term mathematical diversity.
European regulators are moving on a parallel track. Under the EU Coordinated Implementation Roadmap for the Transition to Post-Quantum Cryptography, Member States and critical infrastructure operators face their first major milestone at the end of 2026: completing cryptographic awareness, governance setup, and initial asset inventories. High-risk systems and critical sectors under NIS2 and DORA are scheduled to complete their transition to quantum-resistant protections by 2030, with broader ecosystem migration extending through 2035.
Most organizations treat cryptography as invisible plumbing. Over the past two decades, developers and vendors hardcoded specific algorithms, key lengths, and cipher suites directly into application source code, firmware, API gateways, and hardware security modules (HSMs).
When organizations previously migrated from SHA-1 to SHA-256 or deprecated TLS 1.0, the process took years of manual code rewrites and emergency patching. Repeating that manual approach for post-quantum cryptography is a recipe for operational paralysis. PQC algorithms have significantly larger key sizes and signature payloads than ECC, meaning blind drop-in replacements can break packet fragmentation, exceed certificate buffer limits, or degrade TLS handshake latency.
Furthermore, cryptographic research continues to evolve. If a mathematical breakthrough weakens a specific lattice-based parameter set in the future, organizations must be able to pivot rapidly to an alternative algorithm without re-architecting their entire application stack.
This capability is crypto-agility: the architectural design principle that decouples cryptographic logic from business applications. In a crypto-agile environment, algorithms, keys, and certificates are managed through centralized abstraction layers and policy engines rather than hardcoded libraries. Security teams can swap cipher suites, adjust key lengths, or enable hybrid encryption through configuration updates rather than code deployments.
You cannot migrate cryptography you cannot see. Before purchasing new security appliances or rewriting TLS configurations, IT and security leaders must build a Cryptographic Bill of Materials (CBOM).
Just as a Software Bill of Materials (SBOM) catalogs open-source dependencies, a CBOM provides a machine-readable inventory of every cryptographic asset across your infrastructure. A thorough CBOM documents:
Modern cryptographic discovery tools combine passive network traffic inspection, static code analysis, and endpoint agents to map these dependencies automatically. Once the CBOM is populated, teams can rank systems by data shelf-life and external exposure, prioritizing internet-facing key exchanges that are actively exposed to Harvest Now, Decrypt Later collection.
Transitioning an enterprise to post-quantum security does not happen in a single weekend cutover. Security architects should execute a phased, risk-driven rollout:
Because confidentiality against HNDL attacks is the most urgent priority, start with key encapsulation (TLS 1.3 and VPN tunnels). Rather than relying solely on a brand-new PQC algorithm, deploy hybrid key exchange (such as X25519 combined with ML-KEM-768). Hybrid mode combines a proven classical algorithm with a standardized PQC algorithm into a single shared secret. Even if an unforeseen flaw emerges in one algorithm, the session remains protected by the other.
Public Key Infrastructure (PKI) carries the longest migration lead time because reissuing root CAs and updating trust stores across thousands of endpoints requires strict coordination. Implement automated Certificate Lifecycle Management (CLM) platforms capable of issuing short-lived certificates and supporting larger ML-DSA signature payloads.
Enterprise hardware refreshes typically span five to seven years. Any firewall, load balancer, VPN concentrator, or HSM purchased today will still be in production past the 2030 regulatory deadlines. Update your RFPs and vendor contracts to require documented support for NIST FIPS 203, 204, and 205, alongside crypto-agile firmware upgrade paths.
Larger PQC public keys and signatures increase network bandwidth overhead during TLS handshakes and mutual TLS (mTLS) microservice authentication. Test PQC cipher suites in staging environments to identify latency bottlenecks, MTU packet fragmentation issues, or legacy middleware buffers that truncate larger certificates.
A Harvest Now, Decrypt Later attack occurs when an adversary intercepts and stores encrypted data today with the intention of decrypting it in the future once cryptographically relevant quantum computers become available. It poses an immediate threat to any sensitive data whose confidentiality must outlast the timeline for quantum computing maturity.
No, not in the same way. While Grover's algorithm provides a quadratic speedup against symmetric ciphers, doubling the key size effectively neutralizes the threat. AES-256 and SHA-384 are widely considered quantum-resistant, whereas asymmetric algorithms like RSA, ECDH, and ECDSA are completely broken by Shor's algorithm.
NIST finalized three foundational PQC standards in August 2024: FIPS 203 (ML-KEM) for key encapsulation and key exchange, FIPS 204 (ML-DSA) for general-purpose digital signatures, and FIPS 205 (SLH-DSA) as a stateless hash-based backup signature scheme. In October 2026, NIST published NIST IR 8547 to guide organizations through the transition away from classical public-key algorithms.
Crypto-agility is the ability of an organization's software and infrastructure to switch cryptographic algorithms, protocols, and keys rapidly without requiring major code rewrites or service disruptions. It prevents vendor lock-in, simplifies compliance with evolving standards, and allows rapid response if a cryptographic algorithm is compromised.
A CBOM is a structured inventory of all cryptographic algorithms, keys, certificates, protocols, and libraries used across an organization's IT environment. Building a CBOM is the mandatory first step in identifying where quantum-vulnerable encryption exists and prioritizing systems for remediation.
Hybrid PQC combines a traditional classical algorithm (such as X25519 or ECDSA) with a standardized post-quantum algorithm (such as ML-KEM-768) within the same cryptographic handshake. This dual-layer approach protects against Harvest Now, Decrypt Later threats while maintaining backward compatibility and defending against potential implementation bugs in newer algorithms.
The EU Coordinated Implementation Roadmap aligns with NIS2 and DORA to require Member States and critical sectors to establish cryptographic inventories and transition plans by the end of 2026, migrate high-risk use cases to quantum-safe cryptography by 2030, and complete full ecosystem transitions by 2035.
Organizations should prioritize external-facing key exchanges (TLS 1.3 web gateways, IPsec VPNs, and API endpoints) that transmit long-lived sensitive data such as healthcare records, financial data, trade secrets, and government communications, as these are prime targets for passive traffic harvesting today.
Waiting until quantum computers make headlines for breaking RSA-2048 means waiting until it is far too late. For data with multi-year confidentiality requirements, the window to prevent retroactive decryption is closing right now, and regulatory timelines across both Europe and North America are already enforcing accountability.
By treating the post-quantum transition as an exercise in crypto-agility rather than a one-off patching project, security leaders gain a lasting advantage. You eliminate hardcoded technical debt, gain complete visibility over machine identities and certificates, and build an infrastructure capable of adapting to whatever mathematical or regulatory shifts arrive next.





