TL;DR: Quantum computing threatens current public key cryptography, and attackers can already preserve encrypted data for future decryption, according to SSH Communications Security. Long-lived systems, unmanaged keys, and slow migration cycles make cryptographic inventory and prioritisation an identity and access problem, not just a standards exercise.
At a glance
What this is: This is an analysis of quantum-safe migration risk that argues visibility into cryptographic assets, unmanaged keys, and legacy dependencies is the first control problem.
Why it matters: It matters because IAM, PAM, and NHI teams often own the certificates, keys, and access paths that will determine whether migration can happen before quantum risk outpaces remediation.
Context
Quantum-safe migration is the process of identifying where public key cryptography is used, understanding which assets depend on it, and prioritising the systems that need replacement first. The article frames this as a resilience issue because many current authentication, key exchange, and signature workflows still depend on RSA, ECC, and certificate-based trust.
The governance gap is not only algorithm choice. Long-lived OT environments, unmanaged keys, and slow change windows create a migration backlog that can outlast the security assumptions built into today’s identity and access controls. In practice, cryptographic inventory becomes the prerequisite for any credible post-quantum programme.
Key questions
A: Without a complete inventory, teams miss certificates and keys hidden in TLS endpoints, code-signing, VPNs, databases, embedded devices, and third-party integrations. That creates blind spots, inconsistent rollout, and unmanaged dependencies that can break services during migration. Discovery is the foundation for classification, prioritisation, and safe execution of every later phase.
Q: Why does harvest now, decrypt later risk make post-quantum planning urgent for long retention data?
A: Harvest now, decrypt later creates risk because encrypted data stolen today may remain valuable for years, especially in sectors that retain records for decades. If the underlying algorithms age out before the data loses sensitivity, confidentiality collapses retroactively. That is why long retention data, regulated records, and critical infrastructure systems need early quantum readiness rather than waiting for a crisis.
Q: Where do post-quantum migration programmes fail most often in OT environments?
A: They fail where long equipment lifecycles, limited maintenance windows, and legacy certificate trust chains make change slow. In those environments, migration slips from a technology refresh into a coordination problem across engineering, security, and operations.
Q: How should security teams start a post-quantum migration program?
A: Start by inventorying where cryptography is actually used, then measure external exposure first. Public domains, certificates, SSH keys, and service accounts should be mapped to owners and replacement paths before standards deadlines force a rushed program. A quick scan is useful, but the real work is governance, sequencing, and lifecycle control.
Technical breakdown
Why public key inventory is the real dependency
Public key cryptography underpins authentication, key exchange, and digital signatures across certificates, firmware validation, and secure sessions. The security problem is that organisations often know which protocols they use but not where those algorithms appear in the wider estate, which keys are unmanaged, or which systems still depend on legacy trust chains. Without that inventory, teams cannot judge exposure by business criticality, data retention horizon, or replacement complexity. That makes cryptographic risk a governance problem as much as a cryptography problem.
Practical implication: build a complete inventory of certificate, key, and algorithm dependencies before assigning migration priorities.
How harvest now, decrypt later changes the timeline
Harvest now, decrypt later means adversaries can collect encrypted data today and wait for future quantum capability to decrypt it later. This shifts the threat model away from immediate compromise and toward the lifespan of the information being protected. Data that seems safe now may still be exposed if it has long retention value, such as intellectual property, regulated records, or OT telemetry. The longer the data must remain confidential, the more urgent post-quantum planning becomes.
Practical implication: rank systems by how long their secrets and records must remain confidential, not only by current attack surface.
Why OT and critical infrastructure face the hardest migration path
Operational technology environments often combine long equipment lifecycles, limited maintenance windows, and legacy cryptographic dependencies that are difficult to replace quickly. That creates a mismatch between the pace of quantum-risk planning and the pace at which OT systems can be changed without disrupting operations. Certificate validation, device authentication, and firmware trust can all become migration blockers when the underlying equipment cannot be refreshed on normal enterprise schedules. The result is a structured backlog, not a single upgrade project.
Practical implication: treat OT cryptographic migration as a phased programme tied to asset lifecycle and maintenance windows.
Threat narrative
Attacker objective: The attacker aims to defer exploitation until quantum decryption becomes practical, then reveal or misuse data that was harvested years earlier.
- Entry occurs when adversaries harvest encrypted data now from systems that still rely on public key cryptography.
- Escalation happens later if those captured secrets, records, or sessions are decrypted once quantum capability matures.
- Impact is delayed confidentiality loss across long-lived data, authentication trust, and infrastructure records that were assumed to remain protected.
Breaches seen in the wild
- Sisense breach 2024: A credential in Sisense's GitLab reportedly opened S3 buckets of customer tokens, passwords and certificates; CISA urged a full reset.
- Colonial Pipeline ransomware attack: A dormant VPN account with a leaked password and no MFA let DarkSide shut down a major US fuel pipeline for six days.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Cryptographic inventory has become an identity governance control, not a background hygiene task. The article is right to frame visibility as the first prerequisite because identity and access systems are full of certificate trust, key exchange, and signed assertion dependencies. Without a complete inventory, migration planning is guesswork and risk prioritisation is arbitrary. Practitioners should treat unknown cryptographic dependencies as governance debt, not as a future optimisation problem.
Harvest now, decrypt later turns retention policy into a security control. Data that must remain confidential for years or decades is the real driver of post-quantum urgency, because the attacker’s timeline no longer matches the defender’s. That changes the way teams should think about certificates, tokens, archives, and signed records. The practical conclusion is that confidentiality duration now matters as much as present-day access scope.
Quantum-safe migration backlog: legacy cryptographic dependencies outlast normal remediation cycles in OT and other long-lived environments. This is the failure mode the article exposes most clearly. Systems that cannot be changed on enterprise timeframes create a persistent window in which today’s encryption may be harvested for tomorrow’s decryption. The implication is that teams need to map migration readiness to asset lifespan, not just to crypto strength.
PQC readiness is now a cross-functional identity programme. The subject is no longer owned by cryptography specialists alone because device identity, certificate operations, PAM-adjacent key stewardship, and compliance evidence all sit in the same chain. That makes NIST-aligned planning a governance issue with operational consequences. Practitioners should expect post-quantum programmes to reshape ownership across IAM, infrastructure, and platform teams.
Long-lived trust chains create a new form of exposure asymmetry. The organisations most able to absorb change are rarely the ones with the highest exposure, while the systems that depend on the oldest cryptography are often the least flexible. That mismatch is why inventory, prioritisation, and remediation sequencing matter more than blanket migration slogans. Security teams should target the oldest trust dependencies first, not the easiest.
What this signals
Cryptographic inventory is the control plane for post-quantum readiness. Teams cannot govern what they cannot see, and that is especially true when certificates, SSH keys, and trust chains are spread across infrastructure, OT, and legacy platforms. The practical shift is from periodic review to continuous mapping of cryptographic dependencies.
Post-quantum programmes will increasingly be judged by sequencing, not by policy statements. The organisations that move first on high-retention data and hard-to-change systems will reduce exposure faster than those that wait for a perfect standards lock-in.
For practitioners
- Map cryptographic assets across the estate Catalogue certificates, public key algorithms, SSH keys, host keys, and any unmanaged key material so migration scope is visible before planning starts.
- Prioritise long-retention data and systems Rank the environments whose confidentiality must last for years or decades, including regulated archives, engineering data, and OT records, because these are most exposed to harvest-now, decrypt-later risk.
- Inventory OT cryptographic dependencies early Identify firmware validation, device authentication, and session setup flows in critical infrastructure before maintenance windows force rushed decisions.
- Separate managed from unmanaged keys Flag keys and certificates that sit outside normal lifecycle control, then assign ownership and retirement paths before they become migration blockers.
- Build an audit-ready migration backlog Document which systems can move now, which require compensating controls, and which depend on vendor or equipment refresh cycles to become post-quantum ready.
Key takeaways
- Quantum risk is no longer a distant standards issue, because encrypted data can be harvested now and exposed later.
- The hardest part of post-quantum migration is finding every place where cryptography underpins identity, access, and trust.
- Cryptographic inventory and asset prioritisation are the controls that turn PQC planning into an executable programme.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST SP 800-57 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-57 | Part 1 — Key Management Lifecycle | The article centres on cryptographic asset inventory and lifecycle planning for keys and certificates. |
| Recommendation — Inventory key lifecycles and classify which cryptographic assets need replacement before quantum exposure widens. | ||
| NIST CSF 2.0 | PR.DS-10 — Integrity and confidentiality of data are protected | Post-quantum planning is about preserving confidentiality of data that must remain safe for years. |
| Recommendation — Map long-retention data to confidentiality controls and prioritise it for post-quantum remediation. | ||
| OWASP Non-Human Identity Top 10 | NHI-07 — Long-Lived Secrets | Certificates, SSH keys, and other long-lived credentials are the cryptographic risk the article discusses. |
| NHI-02 — Secret Leakage | Unmanaged keys and certificate material can remain exposed outside normal governance and inventory. | |
| Recommendation — Find long-lived cryptographic secrets and retire or replace them before they become future decryption targets. Scan for exposed key material and remove any cryptographic secrets that are not under lifecycle control. | ||
| MITRE ATT&CK | TA0006 — Credential Access | Harvest-now, decrypt-later is a credential and data capture strategy aimed at future access. |
| Recommendation — Map encrypted-data harvesting to credential access and protect long-retention secrets accordingly. | ||
Key terms
- 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.
- 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.
- Unmanaged Key Material: Unmanaged key material is cryptographic material that exists outside normal ownership, rotation, or retirement processes. In practice, these keys and certificates create hidden migration risk because they can persist long after teams think the environment is under control.
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 building or maturing an IAM programme, it is worth exploring.
Published by the NHIMG editorial team on June 24, 2026.
Updated on October 11, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org