Harvest now, decrypt later risk demands post-quantum migration

At a glance

What this is: This is an analysis of harvest now, decrypt later attacks and the post-quantum migration work needed to reduce long-term cryptographic exposure.

Why it matters: It matters because IAM, NHI, and security teams must know where certificates, keys, and encrypted data live before quantum-safe migration becomes a forced, high-risk scramble.

By the numbers:

• 17 minutes

👉 Read eMudhra's analysis of harvest now, decrypt later risk and post-quantum readiness

Context

Harvest now, decrypt later is a cryptographic exposure problem: attackers capture encrypted data now and wait for future computing power to make that data readable. For identity teams, the issue is not only encryption strength, but how long certificates, keys, and protected records must remain confidential across their full lifecycle.

The governance gap is that many programmes still treat cryptography as a static control rather than an inventory-driven, migration-ready asset class. Once long-lived data is collected, the defender's only meaningful leverage is crypto-agility, because the exposure window may outlast the original system design.

NIST's 2024 publication of post-quantum cryptography standards makes the migration work concrete rather than speculative. That shifts the problem from theoretical quantum risk to operational readiness across identity, workload, and data protection programmes.

Key questions

Q: How should security teams prepare for harvest now, decrypt later attacks?

A: Start with a complete cryptographic inventory, then rank assets by confidentiality lifetime and business impact. The highest priority is any data or identity trust chain that must remain protected for years, because those records are the most exposed if quantum decryption becomes practical. Planning without inventory leaves migration decisions guesswork.

Q: Why does crypto-agility matter for identity and access programmes?

A: Identity programmes rely on certificates, signatures, and trust chains that can break when cryptographic standards change. Crypto-agility matters because it lets teams replace those primitives without rebuilding every dependent system. Without that flexibility, access and federation controls become brittle exactly when migration pressure increases.

Q: What breaks when organisations treat encryption as a static control?

A: Static encryption assumptions break when protected data must remain confidential longer than the cryptographic method can be trusted. The failure is not immediate compromise, but future exposure of archived records and signed trust relationships. Teams also lose the ability to plan migration in a controlled sequence, which raises operational risk.

Q: How do organisations know if they are ready for post-quantum migration?

A: They are ready when they can identify every place a classic algorithm is in use, change it without major downtime, and prove ownership for each trust domain. If the team cannot answer which systems depend on which certificates or keys, readiness is not there yet.

Technical breakdown

Why quantum-safe migration depends on cryptographic inventory

Post-quantum migration fails first at visibility. An organisation cannot protect what it cannot enumerate, and cryptographic inventory must cover certificates, algorithms, keys, dependencies, and the systems that rely on them. Without that map, teams cannot tell which assets are long-lived enough to be attractive harvest now, decrypt later targets, or which services will break when algorithms change. Crypto-agility is the architectural answer, but it starts with asset discovery, dependency mapping, and ownership assignment across platforms and business units.

Practical implication: build and maintain a cryptographic inventory before planning algorithm transitions.

Crypto-agility as an identity and trust control

Crypto-agility means the trust fabric can change without a full-system rebuild. In practice, that requires certificate lifecycle processes, configurable trust chains, and the ability to swap cryptographic primitives as standards evolve. This is not just a cryptography concern. It affects machine identity, service authentication, signing, and any workflow where certificates or keys anchor trust. If replacement requires emergency engineering, the environment is not agile enough for a quantum migration timeline.

Practical implication: test whether identity and trust systems can swap cryptography without breaking production workflows.

Why long-lived sensitive data creates the highest HNDL exposure

HNDL is most dangerous where confidentiality must survive for years or decades. Medical histories, intellectual property, state records, and regulated archives are prime examples because the value of the data does not expire quickly. Even if quantum computers mature slowly, the attacker's storage cost is low, so the defender loses time as a factor. That makes retention policy, encryption design, and data classification part of the quantum threat model, not just archival governance.

Practical implication: classify long-retention data first and prioritise its migration to quantum-safe protection.

Threat narrative

Attacker objective: The attacker aims to preserve encrypted material until quantum computing can reveal confidential data that is still valuable years later.

1. Entry occurs when adversaries collect encrypted communications, files, and stored records at scale without needing to break them immediately.
2. Escalation happens when those harvested assets are retained until quantum-capable decryption becomes viable, turning yesterday's protected data into today's readable intelligence.
3. Impact is delayed but severe: long-lived sensitive information can be exposed years later, including records that were assumed safe under current public-key cryptography.

Breaches seen in the wild

• Sisense breach — unauthorized GitLab access led to exfiltration of access tokens, API keys and certificates.
• MITRE ATT&CK Enterprise Matrix — MITRE ATT&CK Enterprise — adversary tactics and techniques, threat detection, attack chain mapping, credential access, lateral movement, privilege escalation.

Read our 52 NHI Breaches Analysis report for a comprehensive view of breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Crypto-agility is now a governance requirement, not an architecture preference. Harvest now, decrypt later attacks turn cryptography into a lifecycle problem because the defender must be able to replace trust primitives after deployment. Systems that cannot rotate algorithms, certificates, and dependencies without service disruption are already behind the threat curve. The practical conclusion is that cryptographic change management must sit inside core identity governance.

Long-lived data creates identity risk even when access controls are working as intended. Encryption can be correctly implemented today and still fail tomorrow if the protected information remains sensitive when future decryption becomes possible. That makes data retention, key management, and certificate lifetime part of the same risk model. Security teams should treat durability of confidentiality as a programme objective, not just access denial.

Post-quantum readiness exposes the identity stack's hidden coupling. Certificate lifecycle, workload identity, application signing, and federation controls often depend on shared cryptographic assumptions. Once those assumptions change, a weak dependency map becomes an operational risk multiplier. The field should expect quantum migration to surface the same visibility problems already seen in NHI and secrets governance.

Cryptographic inventory is the named control gap that HNDL exploits. The attacker only needs to archive data once, but the defender must know every place where classic cryptography protects long-lived content. Without that inventory, organisations cannot prioritise the assets that matter most or prove readiness for migration. The practitioner takeaway is that visibility is the starting condition for every post-quantum plan.

Post-quantum timelines reward organisations that reduce cryptographic sprawl now. Multiple certificate authorities, inconsistent algorithm choices, and undocumented dependencies make migration slower and riskier. The market signal is clear: teams that standardise trust infrastructure will move faster when standards shift. Practitioners should treat simplification as a resilience control, not only a cost decision.

From our research:

• The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
• Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap.
• Forward-pivot: the same visibility problem shows up in 52 NHI Breaches Analysis, where unmanaged credentials repeatedly outlive the controls meant to contain them.

What this signals

Cryptographic sprawl will behave like NHI sprawl if it is left unmanaged. The programme challenge is not only which algorithms to adopt, but how many trust domains, certificate paths, and lifecycle owners exist today. Teams that already struggle with secrets and workload identity will feel the same pain in post-quantum migration unless they standardise ownership and reduce duplication. The operational lesson is that simplification now reduces future conversion work.

The right near-term question is whether identity, platform, and application teams can execute a cryptographic change without a service redesign. If the answer is no, then PQC readiness is still an architectural aspiration, not an operating capability. That is where migration programmes should focus their first remediation cycles.

For practitioners

• Inventory every cryptographic dependency Map certificates, keys, algorithms, and applications that depend on them so you can identify where classic cryptography still protects long-lived data. Include internal systems, third-party services, and archived stores that may outlive today’s standards.
• Prioritise long-retention data for migration Classify records that must remain confidential for years or decades, then move those systems first in your post-quantum roadmap. Focus on regulated archives, intellectual property, and identity systems that anchor trust for other services.
• Test crypto-agility before standards change Run controlled change exercises that swap algorithms or certificates without rebuilding applications. Measure whether identity, signing, and federation flows can survive a cryptographic transition without emergency exceptions.
• Build ownership for cryptographic lifecycle management Assign a named owner for each trust domain so replacement work does not stall between security, platform, and application teams. The goal is to make migration decisions executable rather than theoretical.

Key takeaways

• Harvest now, decrypt later turns today’s encryption decisions into tomorrow’s exposure problem.
• The scale of the risk is driven by long-lived data, cryptographic sprawl, and poor visibility into where trust primitives are used.
• Post-quantum readiness depends on inventory, crypto-agility, and lifecycle ownership, not on waiting for quantum computing to mature.

Key terms

• Harvest Now, Decrypt Later: A threat pattern where attackers capture encrypted data today and store it until future computing power can break the cryptography. For identity and security teams, the risk is delayed exposure, especially for records and trust chains that must remain confidential for many years.
• Crypto-Agility: The ability to change cryptographic algorithms, certificates, or trust mechanisms without rebuilding the whole environment. In practice, it means systems can move to stronger standards on a controlled timetable, which is essential when current encryption may not remain safe for the full data-retention period.
• Cryptographic Inventory: A complete map of where cryptographic assets are used, including keys, certificates, algorithms, and the applications that depend on them. It is the foundation for migration planning because teams cannot replace what they cannot locate or assign to an owner.
• Post-Quantum Cryptography: Cryptographic methods designed to resist attacks from future quantum computers. In identity programmes, the practical issue is not only adopting new algorithms, but ensuring that federation, signing, and workload trust can move without breaking business operations.

What's in the full article

eMudhra's full article covers the operational detail this post intentionally leaves for the source:

• A practical description of how to inventory certificates, keys, and algorithms across the environment.
• A migration sequence that aligns long-lived data protection with NIST post-quantum timelines.
• A closer look at how crypto-agility reduces disruption when trust primitives need replacement.
• The product context behind certificate lifecycle transition tooling and cryptographic discovery.

👉 eMudhra's full article covers the cryptographic inventory and migration detail behind PQC readiness.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or programme maturity, it is worth exploring.