TL;DR: Encrypted data theft is already a live threat because attackers can store it now and decrypt it later, while EY says 87% of UK business leaders expect quantum disruption by 2030 and ISACA found 56% of security and trust professionals are concerned, according to Ground Labs. The practical issue is not distant quantum capability but how long sensitive data, digital identities and certificates remain valuable and exposed.
At a glance
What this is: This is a blog post about quantum-era data risk, arguing that harvest now, decrypt later makes encrypted identity and business data vulnerable long before Q-day arrives.
Why it matters: It matters because IAM, PKI and NHI programmes must treat cryptographic lifespan, certificate exposure and identity-related data retention as current governance problems, not future ones.
By the numbers:
- 87% of UK business leaders expect disruption from quantum computing by 2030, according to EY research cited by Ground Labs.
- 56% of cybersecurity and trust professionals were concerned about the harvest now, decrypt later threat, according to ISACA research cited by Ground Labs.
Context
Harvest now, decrypt later is a data-retention and cryptographic-exposure problem, not a future-only quantum science issue. If encrypted records, identity data or certificates remain valuable for years, attackers can capture them now and wait for decryption capability to catch up.
The governance gap is that many programmes still treat encryption as a binary control rather than a time-bound protection model. Identity systems, certificates, software-signing flows and cloud integrations all create long-lived cryptographic dependencies that become more dangerous the longer they stay in circulation.
Key questions
Q: What breaks when encrypted identity data is harvested now and decrypted later?
A: The failure is not immediate access but deferred compromise. Attackers can store ciphertext until cryptography weakens, then recover identity records, certificates or other long-lived data that were assumed safe. That breaks confidentiality assumptions built on static encryption, especially where retention periods outlast current algorithm strength.
Q: Why do long-lived data and credentials increase quantum risk?
A: Long-lived data increases quantum risk because information that is safe today may still need to remain confidential after quantum-capable attackers emerge. That means the question is not only how strong encryption is now, but whether the protection will still hold across the data’s retention life. The longer the confidentiality requirement, the higher the exposure to harvest-now-decrypt-later attacks.
Q: What are the signs that cryptographic exposure is growing?
A: Look for systems with undocumented certificates, duplicated sensitive data across email and backups, long retention periods, and identity or application services that still depend on vulnerable public-key algorithms. Those are the patterns that indicate your data can be harvested now and remain decryptable later.
Q: When should organisations prioritise post-quantum migration work over waiting for final standards?
A: Organisations should begin planning now, even before every standard detail is final, because migration across certificates, validation software, and application ecosystems can take years. Waiting creates a larger backlog once production deadlines tighten. The sensible sequence is inventory, lab testing, and dependency mapping first, then staged rollout as standards and interoperability guidance stabilise.
Technical breakdown
Why harvest now, decrypt later changes cryptographic risk
Harvest now, decrypt later means adversaries do not need to break encryption immediately. They can steal ciphertext now, store it cheaply, and decrypt it later when quantum-capable algorithms or hardware make current public-key systems weaker. That changes the threat model for RSA, Diffie-Hellman and elliptic-curve cryptography because confidentiality is no longer measured only at the moment of interception. It is measured across the full lifespan of the data, the key material, and the systems that protect it.
Practical implication: Practitioners need to assess whether current protections still hold for the entire confidentiality life of the data, not just during transmission.
Why identity systems and certificates are in scope
Digital identities depend on cryptographic trust chains, certificates, signatures and key exchange. When those primitives weaken, authentication, software updates, cloud integrations and signed identity assertions become exposed alongside the underlying data. The risk is especially relevant where identity evidence, biometric data or legal records must remain confidential for many years. In that setting, the same cryptographic control that protects access today may become the weakest point in the assurance chain later.
Practical implication: Identity and PKI teams should inventory where long-lived credentials, certificates and signed identity artifacts create future confidentiality exposure.
What crypto-agility actually means in practice
Crypto-agility is the ability to swap algorithms, keys and certificates without redesigning the business service around them. It depends on separating cryptographic functions from application logic, standardising approved libraries, and tracking which systems rely on which primitives. Without that separation, migration to post-quantum cryptography becomes a programme of manual exception handling, not a controlled change. The operational challenge is therefore not only choosing new standards, but making the environment flexible enough to adopt them at pace.
Practical implication: Security architects should design for algorithm replacement and dependency tracing before a forced migration window appears.
NHI Mgmt Group analysis
Harvest now, decrypt later is a governance failure of data lifespan, not just a cryptography problem. Organisations often classify encryption as sufficient once data is protected in transit or at rest, but that assumption ignores how long the underlying information must stay confidential. When data has a multi-year or lifelong value horizon, the control has to be evaluated against future decryption capability as well as present-day interception. The practitioner conclusion is simple: confidentiality planning must align with retention reality.
Identity data carries a different quantum risk profile because it is durable and reusable. Biometric data, legal records, identity assertions and signed trust material do not age out quickly, which makes them especially exposed to delayed decryption. That creates a direct intersection between quantum readiness, IAM and PKI governance, because certificate lifecycles and identity trust chains can outlast the systems that issued them. The practitioner conclusion is to treat identity-linked cryptography as long-horizon risk.
Crypto-agility is the named capability that separates resilient programmes from static ones. In practice, it means the organisation can replace algorithms and certificate dependencies without destabilising applications, vendors or federated identity paths. This is more than a technical preference; it is a governance property that determines whether quantum migration is manageable or chaotic. The practitioner conclusion is to prioritise agility in architecture, procurement and dependency management now.
PQC migration will expose hidden cryptographic debt across identity and application ecosystems. The article correctly points to certificates, signing processes, cloud integrations and legacy platforms because those are the places where undocumented dependencies accumulate. That means the work is not just about selecting post-quantum standards, but about discovering where current trust chains still rely on vulnerable public-key assumptions. The practitioner conclusion is to start with inventory before standards selection.
What this signals
Quantum readiness should be treated as an identity governance issue as much as a cryptography issue. Certificate lifecycles, trust chains and long-lived identity records all determine whether a stolen encrypted asset remains valuable in the future. Teams that already manage IAM and PKI as separate functions need to connect them around data lifespan, not just access control.
Long-lived confidentiality is the critical design variable. If data must stay secret beyond the life of current public-key assumptions, the exposure window begins today, even if the compromise is only realised later. That is why retention policy, data discovery and cryptographic inventory need to be planned together rather than in separate workstreams.
For practitioners
- Map long-lived data and identity records Classify which records must remain confidential beyond 2030, including identity data, biometric data, legal records and sensitive business information, then rank them by confidentiality lifespan and exposure.
- Build a cryptographic inventory Document the algorithms, keys, certificates, libraries and dependencies protecting each high-value system so you can see where vulnerable public-key cryptography still underpins trust.
- Reduce unnecessary retention and duplication Delete stale copies, enforce retention rules and narrow access paths so fewer long-lived records are available for harvest-and-hold attacks.
- Design for crypto-agility Separate cryptographic functions from business logic, standardise approved libraries and plan for certificate and algorithm replacement without service redesign.
- Start controlled PQC pilots Test post-quantum replacements in limited environments first, then expand by system criticality and business risk while monitoring interoperability and performance.
Key takeaways
- Harvest now, decrypt later turns encryption into a time-based risk problem because data stolen today may only be exploitable years later.
- Identity records, certificates and other durable data are especially exposed because their confidentiality horizon often extends well beyond current cryptographic assumptions.
- The practical response is to discover what must stay secret longest, reduce unnecessary retention, and build crypto-agility into identity and certificate management.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack surface, NIST SP 800-57, NIST CSF 2.0 and CIS Controls v8 set the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-57 | Part 1 — Key Management Lifecycle | The article is fundamentally about how long cryptographic protection remains viable. |
| Recommendation — Inventory keys and certificates by lifespan so you can plan replacement before decryption risk outlasts the data. | ||
| NIST CSF 2.0 | PR.DS-10 — Confidentiality | Quantum exposure changes confidentiality planning for long-lived sensitive data. |
| Recommendation — Classify long-lived sensitive data and reduce exposure where current protection will not last long enough. | ||
| ISO/IEC 27001:2022 | A.8.24 — Use of cryptography | The article addresses cryptographic controls, algorithm change and key/certificate governance. |
| Recommendation — Document cryptographic dependencies and update cryptography so vulnerable algorithms can be replaced cleanly. | ||
| CIS Controls v8 | CIS-3 — Data Protection | Reducing retention and duplicated exposure is central to harvest now, decrypt later defence. |
| Recommendation — Limit stored copies of sensitive data and enforce retention controls to shrink harvestable exposure. | ||
| MITRE ATT&CK | TA0009;TA0010 — Collection; Exfiltration | The threat model is encrypted data collection now and deferred use later. |
| Recommendation — Map harvested ciphertext activity to collection and exfiltration behaviours in your detection logic. | ||
Key terms
- Harvest now, decrypt later: An attacker strategy where encrypted traffic or stored data is collected today and decrypted later when better computing power becomes available. It matters to NHI governance because machine identities often protect the data paths and secrets most worth preserving over time.
- Post-Quantum Cryptography: Cryptographic algorithms designed to remain secure against attacks from sufficiently powerful quantum computers. In practice, PQC is a migration problem as much as an algorithm problem because organisations must replace trust anchors, certificates, and secrets without breaking identity-dependent systems.
- Crypto-Agility: Crypto-agility is the ability to change cryptographic algorithms, certificates, and trust dependencies without redesigning production systems. It matters because cryptographic standards evolve, and organisations need accurate inventories and automated lifecycle controls before they can migrate safely.
- Cryptographic Inventory: A cryptographic inventory is a continuously updated record of keys, certificates, algorithms, libraries and trust anchors across an organisation. It is not a spreadsheet or one-time audit output. In practice, it links each asset to ownership, usage, lifecycle state and risk so teams can make remediation decisions.
Deepen your knowledge
The NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security and secrets management. It is designed for practitioners who need to connect identity controls to broader security and risk programmes.
Published by the NHIMG editorial team on August 18, 2026.
Updated on October 12, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org