Preparing for Harvest Now Decrypt Later threats

Harvest now decrypt later is a current data security risk, not a future quantum problem. Attackers collect encrypted traffic, backups, and archives today, then wait for better tools to expose them. Leaders should find long-lived sensitive data, harden encryption, cut retention, and prepare critical systems for quantum-resistant algorithms before harvested ciphertext becomes readable.

To address this threat, the National Institute of Standards and Technology (NIST) finalized its first post-quantum cryptography (PQC) standards in 2024, giving businesses a clearer path forward.

• NIST standards give enterprises a starting point for PQC planning.
• Long-lived records face the highest exposure from store now decrypt later campaigns.
• The data breach doesn’t trigger alarms, cause alerts, or prompt contact, leaving the breach invisible.
• Crypto-agility helps businesses swap algorithms without rebuilding core systems.

The work starts with finding sensitive data that must stay confidential for years, checking which cryptography protects it, and cutting the amount of information attackers can store for later use.

Stronger transport security, better key management, archive protection, and staged PQC pilots can shrink the harvest window while migration plans take shape.

Harvest now decrypt later (HNDL), also called store now decrypt later, is an attack strategy where adversaries collect encrypted data now and save it for future decryption. Their goal is to hold ciphertext until better technology makes decryption possible.

That delayed payoff sets HNDL apart from a standard breach. Most attacks aim for immediate access. HNDL campaigns work quietly by capturing encrypted sessions, backups, messages, or archives and waiting for protections to weaken.

The risk grows with how long data must stay private. Health records, financial histories, intellectual property, legal files, research data, government records, and executive communications can hold value for years. Data that must stay private for a decade needs stronger planning than data that loses value in weeks.

NIST's 2024 PQC standards make the timing concrete. The agency finalized standards for quantum-resistant key exchange and digital signatures, giving security, networking, compliance, and application teams a practical path to test and adopt cryptography built for a post-quantum world.¹

Understanding how HNDL attacks unfold helps organizations identify where their defenses are weakest. HNDL is a patient strategy. Campaigns follow three stages: collection, storage, and delayed decryption.

Stage 1: Collection

Attackers capture encrypted assets using multiple methods, including:

Weak access controls, exposed storage, compromised accounts, misconfigured cloud services, and vulnerable devices all create opportunities at this stage. Attackers also save certificate details, timestamps, and metadata alongside captured data to support future analysis.

Stage 2: Storage

Cheap cloud infrastructure and automated indexing make long-term retention easy. Captured data gets tagged by:

Over time, the archive becomes a library of encrypted material waiting for better decryption tools.

Stage 3: Delayed decryption

The final stage begins when breaking the encryption gets cheaper. That shift could come from:

When any one of those conditions is met, every record collected in Stage 1 becomes readable.

The data being collected today is only as safe as the cryptography protecting it will be years from now, and that calculation looks different depending on what an organization holds and for how long.

The greatest exposure sits where sensitive data holds value for a long time. Industries that often retain large stores of data with strategic, personal, or regulatory value may face the highest risk. The following are examples of data targets across industries:

Financial services

Long-term value makes financial services data a prime collection target:

Healthcare and life sciences

Much healthcare and life sciences data stays sensitive for a lifetime:

Manufacturing and technology

Competitive advantage for manufacturing and technology businesses depends on keeping this data protected:

Public sector and critical infrastructure

Operational and strategic data in the public sector and critical infrastructure carries national and public safety implications:

The common thread across every high-risk sector is time. Data collected today doesn't need to be decrypted today, and organizations that haven't assessed their data through that lens are carrying risk they haven't yet measured.

Risk assessment should follow the data lifecycle. Leaders need to know where sensitive data is created, where it travels, which systems process it, where it lands, how long it stays, and when it gets destroyed.

Legal, executive, and board communications

Some of the most strategically sensitive data in any organization never appears on a formal data classification list, including:

Hidden exposure sources

Risk isn't always where organizations expect it. Watch for:

Data that looks dormant today can become a liability the moment decryption gets cheaper, which means organizations that haven't mapped their data to its confidentiality window are already behind.

Understanding what’s at risk sets the stage for the harder question: why does HNDL demand action now?

Much of today's digital security relies on public key cryptography. Rivest-Shamir-Adleman (RSA) and elliptic-curve cryptography (ECC) protect key exchange, digital signatures, certificates, secure web sessions, VPNs, and software updates. Large-scale quantum computing could change that significantly.

Quantum computers aren't breaking enterprise cryptography today. The concern is timing. Shor's algorithm can crack the math that RSA and ECC rely on far faster than any classical computer can. That creates a harvest window: attackers collect encrypted data now and decrypt it once quantum capability matures.

Symmetric encryption such as the Advanced Encryption Standard (AES) holds up better, but public key cryptography remains the bigger problem. In 2024, NIST finalized new encryption standards designed to resist quantum attacks, covering data in transit and digital signatures.²

Waiting leaves already-harvested data exposed. Migration will take years across applications, networks, devices, public key infrastructure (PKI), certificates, suppliers, and compliance processes.

[Read: What is quantum computing?]

Organizations can take concrete steps today that reduce exposure, shrink the harvest window, and build the foundation for a longer-term migration.

Step 1: Build visibility first

You can't protect what you can't see. Start with a full inventory that covers:

Step 2: Harden what you have

Short-term hardening can start while the inventory is being built. Security teams should:

Step 3: Protect backups and archives

Stored data is a primary collection target. Archives should have:

Tokenization, anonymization, and minimization can reduce the value of records that can't be deleted.

Step 4: Enforce policies at scale

Software-defined wide area networking (SD-WAN) and centralized security tools make it easier to apply consistent encryption policies across branches, cloud connectivity, and remote sites. That same model supports PQC pilots on high-value routes before broader rollout, letting teams test and validate before committing to full migration.

These steps make harvested data significantly harder to use, and implementing post-quantum cryptography today can strengthen your defenses.

Post quantum cryptography (PQC) resists attacks from both classical and quantum computers, protecting data whose value outlasts today's algorithms.

NIST's 2024 standards provide a clear starting point. FIPS 203 (ML-KEM) covers a key-encapsulation mechanism based on the CRYSTALS-Kyber algorithm family.³ FIPS 204 (ML-DSA) covers a lattice-based digital signature algorithm based on CRYSTALS-Dilithium.⁴ FIPS 205 (SLH-DSA) covers a stateless hash-based signature approach based on SPHINCS+.⁵

For HNDL defense, key exchange is the priority. Post-quantum key encapsulation protects shared-secret negotiation against future quantum attacks. Digital signatures also need migration because they support certificates, code signing, device identity, and software supply chains.

Hybrid cryptography pairs classical and post-quantum algorithms, maintaining compatibility during migration while reducing future risk. Staged rollouts and capacity testing help manage the operational impact of larger post-quantum keys on handshake size, bandwidth, and latency.

Crypto-agility underpins PQC readiness. Systems that swap algorithms and certificate profiles through configuration rather than full rewrites are better positioned for the transition. NIST guidance stresses inventory, prioritization, and coordinated rollout because cryptographic dependencies run deep.⁶

Leaders need to fund, govern, and measure the cryptography program. HNDL risk spans cybersecurity, networking, legal, compliance, procurement, and operations. Clear ownership prevents drift.

Phase 1: Assessment

Map algorithms, key lengths, libraries, certificates, VPNs, TLS endpoints, signing systems, and key management tools. Identify assets relying on RSA, ECC, older protocols, or systems that can't easily be upgraded.

Phase 2: Hardening

Enforce forward secrecy, remove old ciphers, patch cryptographic libraries, rotate keys on set schedules, and re-encrypt high-value archives during storage refresh cycles.

Phase 3: Crypto-agility

Build systems that support algorithm changes through configuration and tested libraries. Prepare PKI and key management for larger keys and automated lifecycle management.

Phase 4: PQC pilots 

Start with controlled, high-value traffic such as selected VPN paths or sensitive application flows. Track latency, processor load, handshake size, failure rates, and rollback options.

Phase 5: Scale

Apply proven patterns across priority systems. Require crypto-agility, current protocols, and clear PQC roadmaps in procurement standards. External services handling long-lived sensitive data should demonstrate cryptographic readiness.

Leaders should track long-lived data coverage, legacy exposure, forward secrecy adoption, archive re-encryption status, and PQC pilot results on a shared dashboard.

Security and business leaders often ask similar questions when they first encounter HNDL risk. These answers address the most common points of confusion and connect each question to a practical response.

What does harvest now decrypt later mean?

Attackers collect encrypted data today and save it for future decryption. The attack succeeds at the point of collection, even if the intelligence value doesn't appear until years later.

How does a harvest now decrypt later attack work?

Attackers capture encrypted traffic, backups, or archives along with metadata and system context, then use stronger computing, stolen keys, or quantum methods to decrypt it later.

Why are encrypted communications vulnerable?

Communications are vulnerable when data must stay private longer than the cryptography protecting it is expected to remain strong. Weak settings, poor key management, and old protocols increase that exposure today.

How can organizations protect archived data?

Inventory archives by confidentiality lifespan, re-encrypt high-value stores, restrict access, rotate keys, and cut retention where possible. Archive protection should fit into the broader PQC migration plan.

Does forward secrecy stop HNDL?

Forward secrecy reduces risk by preventing retroactive decryption of captured sessions, but it doesn’t prevent a future quantum computer from breaking the captured exchange directly. It also doesn't protect data taken from endpoints, backups, or applications after decryption. Closing the HNDL gap needs a post quantum key exchange in addition to forward secrecy.

Harvest now decrypt later is a present-day risk, not a future one. Attackers are already collecting encrypted material they expect to read later, and the most exposed organizations are those holding sensitive data protected by cryptography that won't remain secure for as long as the data must remain confidential.

Your response starts now: inventory long-lived data, harden current controls, enforce forward secrecy, improve key management, and reduce unnecessary retention. NIST's 2024 PQC standards give organizations a real path to begin pilots and plan migration before a rushed transition becomes unavoidable.

Prepare your network for the post-quantum era with AT&T Business. Explore secure, agile connectivity with AT&T SD-WAN and strengthen your protection strategy with AT&T Business cybersecurity solutions. To connect with an expert who knows business, contact your AT&T Business representative.

See how ultra-fast, reliable fiber, protected by built-in security, and 5G connectivity give you a new level of confidence in the possibilities of your network. Let our experts work with you to solve your challenges and accelerate outcomes. Your business deserves the AT&T Business difference—a new standard for networking.

[1] “NIST Releases First 3 Finalized Post-Quantum Encryption Standards,” National Institute of Standards and Technology, August 13, 2024, https://www.nist.gov/news-events/news/2024/08/nist-releases-first-3-finalized-post-quantum-encryption-standards.

² Ibid.

3 National Institute of Standards and Technology, Module-Lattice-Based Key-Encapsulation Mechanism Standard, Federal Information Processing Standards Publication 203, August 13, 2024, https://doi.org/10.6028/NIST.FIPS.203.

4 National Institute of Standards and Technology, Module-Lattice-Based Digital Signature Standard, Federal Information Processing Standards Publication 204, August 13, 2024, https://doi.org/10.6028/NIST.FIPS.204.

5 National Institute of Standards and Technology, Stateless Hash-Based Digital Signature Standard, Federal Information Processing Standards Publication 205, August 13, 2024, https://doi.org/10.6028/NIST.FIPS.205.

6 National Institute of Standards and Technology, Transition to Post-Quantum Cryptography Standards, NIST Internal Report 8547, initial public draft, November 2024, https://doi.org/10.6028/NIST.IR.8547.ipd.