--- title: Harvest-Now-Decrypt-Later — The Quantum Threat to Long-Shelf-Life Data | RGM® url: https://realgrowthmatters.com/learn/privacy/harvest-now-decrypt-later-threat/ updated: 2026-06-10 source_html: https://realgrowthmatters.com/learn/privacy/harvest-now-decrypt-later-threat/ --- # Harvest-Now-Decrypt-Later — Why Adversaries Are Stockpiling Today's Encrypted Data for Tomorrow's Quantum Decryption Harvest-now-decrypt-later (HNDL) is an adversarial strategy: collect encrypted traffic and stored data today, archive it, decrypt when sufficiently powerful quantum computers become available — likely 2030–2040. Data with long shelf life (PII, health records, IP, legal documents, M&A materials, customer financial data) is already at risk. The marketing implication is that data classification and PQC migration are not future problems — they are current problems with future consequences. Most discussion of quantum computing in security frames it as a future threat — 'when quantum computers exist, RSA breaks'. The harvest-now-decrypt-later threat reframes the timeline. The attack happens today: an adversary intercepts encrypted traffic, stores it, and waits. The decryption happens when the technology arrives. Data with shelf life longer than the wait is already compromised; the compromise simply hasn't been disclosed yet. ## Who runs HNDL operations The threat actors capable of HNDL operations are nation-state intelligence agencies and well-resourced criminal organizations. Public reporting confirms: - **NSA** — multiple historical programs (TURMOIL, XKEYSCORE) collected internet traffic at scale; reasonable inference that PQC-vulnerable encrypted traffic has been retained - **China's MSS** — operates large-scale collection; the 2015 OPM breach exfiltrated 21.5 million federal employee records, suggesting interest in identity data with multi-decade shelf life - **Russia's FSB / GRU** — historical collection programs - **Other state actors** — Israel (Unit 8200), UK (GCHQ), France (DGSE), Germany (BND) - **Criminal organizations** — ransomware groups have begun exfiltrating data before encryption, often retaining copies; HNDL is a natural extension ## Why long-shelf-life data is the highest priority The threat actor's calculation is simple: encrypted data has value if it remains valuable when decrypted. Categories at highest risk: - **Personal identity records** — name, DOB, SSN, biometric data. Identity doesn't change; a 2026 SSN is still identifying in 2040. - **Health records** — medical history is permanent; HIPAA violations decades old still matter. - **Financial records** — banking history, investment positions, tax records remain sensitive long-term. - **Government clearance materials** — security clearance applications, polygraph results. - **Legal documents** — M&A diligence, intellectual property filings, sealed court records. - **Corporate secrets** — trade secrets, source code, strategy documents. - **Diplomatic and military communications** — long-term strategic intelligence value. - **Personal communications** — for blackmail or political leverage. ## What's at lower HNDL risk Data with short shelf life is at lower HNDL risk: - **Real-time transaction signals** — ad bid prices from 2024 don't matter in 2040 - **Session-bound data** — TLS keys are ephemeral; capturing them gives session content, but the content quickly stales - **Time-stamped operational data** — log files from yesterday's deploys - **Ephemeral messaging** — disappearing messages, properly implemented, may use forward-secret keys derived after capture - **One-time tokens and authorizations** — already expired #### RGM Experts Say The conversation we keep having with security teams is about data classification. Most marketing organizations don't classify data by shelf life. They classify by 'PII vs not-PII'. The HNDL threat forces a different question: 'How long does this data need to be confidential?' A customer's name is sensitive for life. A campaign performance report is sensitive for a quarter. The encryption migration priorities should reflect that ordering. ## Mitigation strategies - **PQC migration priorities by shelf life** — encrypt high-shelf-life data with PQC first; defer low-shelf-life systems - **Hybrid TLS for in-transit data** — adopt hybrid Kyber+ECDH; protects all in-transit data against HNDL going forward - **Re-encrypt data at rest with PQC** — for long-shelf-life archives, re-encrypt rather than leaving encrypted with vulnerable algorithms - **Reduce data retention** — every quarter spent retaining data unnecessarily increases HNDL exposure; data retention policies become a security control - **Key rotation cadence** — frequent rotation reduces the window of exposure for any single key - **Out-of-band channels for highest-sensitivity material** — paper, in-person, air-gapped systems for the highest-sensitivity material - **Data masking and tokenization** — replace PII with tokens in non-essential systems; reduces the value of intercepted data ## Vendor diligence questions - What cryptographic algorithms protect customer data in transit and at rest? - Is there a documented PQC migration roadmap? - What is the key rotation cadence? - Are encryption keys stored in hardware security modules (HSMs) or cloud KMS? - What audit and compliance certifications attest to the cryptographic implementation? - How long is customer data retained, and what is the deletion procedure? - Is the vendor preparing for hybrid TLS / PQC migration? - Are subprocessors required to meet the same cryptographic standards? ## Related guides - See [quantum-secure cryptography](/learn/privacy/quantum-secure-cryptography/) - See [data classification](/learn/governance/data-classification-frameworks/) - See [data retention policy](/learn/governance/data-retention-policy-design/) ## Sources 1. [1]NSA / CISA "Quantum-Readiness: Migration to Post-Quantum Cryptography" guidance; Cloudflare and AWS post-quantum blog posts ### Related guides - [Quantum-secure cryptography](/learn/privacy/quantum-secure-cryptography/) - [Data classification frameworks](/learn/governance/data-classification-frameworks/) - [Data retention policy design](/learn/governance/data-retention-policy-design/)