A harvest now, decrypt later quantum threat is the risk that attackers collect encrypted data today and store it for future decryption when quantum computers become powerful enough. In practice, long-lived secrets, sensitive records, and intercepted traffic face exposure unless organizations adopt quantum-resistant cryptography and reduce data retention.
Why harvest now, decrypt later matters
This threat matters because encrypted material can remain valuable for years even when it is unreadable today. Attackers are betting that a future quantum capability, or a cryptanalytically relevant quantum computer, will turn captured traffic, archives, and long-lived records into plain text later.
The practical consequence is that confidentiality is time-bound. Data that looks safe under current cryptography may still be exposed if it must remain secret across long retention windows, especially when adversaries can collect it quietly and wait.
What attackers target in a harvest now, decrypt later scenario
The most attractive targets are high-value data sets that age poorly, including regulated records, intellectual property, credentials, signing material, and intercepted network traffic. The longer the data must stay confidential, the more likely it is to fall within the window that quantum-capable decryption could eventually break.
This is why the issue is not only about one algorithm choice. It is also about where encrypted data flows, who can copy it, and how much of it remains worth storing for future exploitation. CISA cyber threat advisories remain a useful place to track broader threat activity while organisations assess their exposure and retention assumptions.
How organisations assess exposure
Exposure assessment starts with cryptographic inventory. You need to know which systems use quantum-vulnerable algorithms, where encrypted data is stored, how long it must remain protected, and which external suppliers or integrations can extend the exposure window.
That review should cover data at rest, data in transit, backups, logs, archives, and any service that may retain captured ciphertext for a long time. A useful next step is mapping those dependencies into a migration view such as Post-Quantum Cryptography Migration Guide, supported by a current inventory of algorithms, keys, and certificates such as the Cryptographic Inventory and CBOM Guide.
Why long-lived secrets and records are the real problem
The threat becomes most serious when secrecy must last beyond the expected life of the current cryptographic assumptions. Long-lived secrets, archival records, and captured sessions create a gap between present-day protection and future decryptability.
In practice, that means organisations should think in terms of confidentiality lifespan, not just encryption status. Q-Day Planning Guide is a natural fit for this problem because it focuses on harvest-now-decrypt-later priorities, supplier readiness, and migration planning around quantum timelines.
Risk and Threat Considerations
Attackers do not need quantum capability today to create damage later. They only need enough access to collect ciphertext now, then patience. That makes this a storage-and-retention risk as much as a cryptography risk, especially for sensitive information that remains valuable for many years.
Failure mechanism: An adversary captures encrypted data, retains it until quantum decryption becomes practical, and then retroactively recovers material that defenders assumed would stay confidential.
Impact: Previously protected records, messages, or secrets can be exposed long after collection, creating delayed breach impact, regulatory exposure, and lasting trust damage.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-57 and NIST CSF 2.0 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-57 | Key Management | Quantum threat directly depends on key lifecycle and cryptoperiod planning. |
| Recommendation — Review key lifetimes and rotate or retire material before long-term confidentiality is lost. | ||
| NIST CSF 2.0 | PR.DS-10 — Confidentiality and integrity are protected | Harvest-now-decrypt-later is a confidentiality protection problem for stored and transmitted data. |
| GV.RM-01 — Risk management strategy is established and monitored | Quantum exposure requires an organisation-wide risk strategy for long-lived confidential data. | |
| ID.AM-02 — Assets are inventoried | Exposure assessment depends on knowing where encrypted data, keys, and dependent systems exist. | |
| Recommendation — Strengthen data protection so captured ciphertext stays unreadable over its full retention period. Add quantum exposure to the risk strategy and track migration progress against it. Inventory cryptographic assets and map where long-lived protected data is stored or transmitted. | ||
| ISO/IEC 27001:2022 | A.8.24 — Use of cryptography | The subject turns on selecting and operating cryptography that fits the confidentiality horizon. |
| Recommendation — Select and govern cryptography according to the period data must remain confidential. | ||
Practitioner Guidance
Why practitioners should care: Treat quantum migration as a data-longevity problem, not only a cryptography upgrade. The highest priority is data and sessions that must remain secret for the longest period, because those are the most exposed to future decryption risk.
Common misunderstanding: It is not enough to say “the data is encrypted.” If the algorithm, key lifecycle, or retention period is wrong for the confidentiality horizon, the protection is only temporary.
Practitioner takeaway: Focus first on crypto inventory, retention reduction, and post-quantum transition planning for the data with the longest security lifetime.
Related resources from NHI Mgmt Group
- Why does harvest now, decrypt later risk make post-quantum planning urgent for long retention data?
- Why does harvest now, decrypt later make quantum migration a current risk even before quantum computers exist?
- Why does harvest-now, decrypt-later matter for NHI governance?
- Why does harvest-now, decrypt-later matter for IAM and NHI programmes?