Quantum-safe migration starts with cryptographic inventory and risk

At a glance

What this is: This is SSH Communications Security’s analysis of why quantum risk makes cryptographic inventory and post-quantum migration urgent for identity-dependent systems.

Why it matters: It matters because certificates, keys, and privileged access paths sit inside IAM, PAM, and workload identity programmes, so quantum readiness changes how teams assess exposure and plan migration.

By the numbers:

• According to some, Q-day can be as early as 2027, or it could also take 20 years.

👉 Read SSH Communications Security's analysis of quantum-safe migration and cryptographic risk

Context

Quantum risk is no longer just a cryptography conversation. When public key systems protect certificates, key exchange, signatures, and device trust, the migration problem reaches into IAM, PAM, and workload identity because those controls often depend on the same cryptographic foundations.

The article’s core argument is straightforward: organisations with long-lived data and long-lived infrastructure need to inventory cryptographic assets before Q-day becomes a planning bottleneck. In critical infrastructure and OT environments, that urgency is sharper because legacy systems can stay in service for decades.

Key questions

Q: How should security teams prioritise post-quantum migration?

A: Start with the identities, certificates, and systems that protect long-lived data or anchor trust for other systems. Then rank assets by confidentiality lifespan, operational criticality, and replacement complexity. That approach reduces the chance that a hidden legacy dependency blocks the broader migration programme.

Q: Why do unmanaged keys make quantum migration harder?

A: Unmanaged keys and certificates hide the exact trust points that depend on vulnerable cryptography. If teams cannot see host identities, SSH algorithms, or certificate chains, they cannot accurately scope impact, estimate effort, or sequence replacement. Discovery quality therefore becomes a migration control, not just an inventory task.

Q: When should organisations treat encrypted data as quantum-sensitive?

A: When the data must remain confidential beyond the likely lifetime of current public key cryptography. That includes regulated archives, intellectual property, industrial records, and operational data with long retention periods. If a future decryption event would still matter, the data is quantum-sensitive now.

Q: Who should own quantum migration in the enterprise?

A: Ownership should sit across identity, security architecture, infrastructure, and operational teams because the problem spans authentication, certificates, device trust, and legacy systems. A single team can coordinate the roadmap, but the migration itself crosses programme boundaries and requires shared accountability.

Technical breakdown

Where public key cryptography still underpins identity trust

Modern identity systems rely on public key cryptography for certificate-based authentication, session key exchange, and digital signatures that validate software and firmware. RSA, ECC, and related schemes do not just encrypt data. They establish trust between users, devices, workloads, and controllers. Once a cryptographically relevant quantum computer can break those schemes, the trust chain fails even if the surrounding IAM process remains unchanged. That makes quantum readiness a control-plane issue, not just an encryption refresh exercise.

Practical implication: map every identity and workload trust path that depends on RSA, ECC, or certificate validation before prioritising migration.

Why harvest now, decrypt later changes the threat model

Harvest now, decrypt later is a delayed exploitation strategy. Attackers collect encrypted traffic or stored data today, then wait until decryption becomes feasible. The risk is highest where data retains value for many years, such as operational records, regulated archives, industrial control data, and intellectual property tied to long product lifecycles. This means encryption that looks adequate today can still become a liability if confidentiality must outlast the current cryptographic era.

Practical implication: classify data by future value horizon, not only by current sensitivity, and prioritise quantum-safe protection for the longest-lived assets.

Why unmanaged keys and certificates are the real migration bottleneck

Cryptographic migration fails when organisations do not know where keys, host identities, certificates, and SSH algorithms exist. Agentless discovery matters because manual inventory misses hidden trust dependencies in estates that span servers, appliances, and OT systems. Without a complete map, teams cannot separate low-risk modern deployments from legacy dependencies that require staged replacement. The real problem is not only choosing new algorithms. It is proving which identities and assets still depend on the old ones.

Practical implication: build a complete cryptographic inventory first, then sequence remediation by exposure, business criticality, and replacement effort.

NHI Mgmt Group analysis

Quantum readiness is now an identity governance problem, not just a cryptography problem. Public key systems sit inside certificates, device authentication, session setup, and firmware validation, which means the trust layer for IAM and OT can fail together. Once those trust anchors become breakable, organisations are not just changing algorithms. They are changing how identities prove legitimacy across the estate. The implication is that quantum migration belongs in identity programme planning, not in a standalone crypto backlog.

Harvest now, decrypt later creates a long-tail exposure window that current risk models undercount. Encryption that protects data for months may be adequate today, but data that must stay confidential for 10 or 20 years needs a different threshold. This is especially relevant for critical infrastructure and regulated environments where retention outlasts technology cycles. Practitioners should treat confidentiality lifespan as a first-class risk variable.

Cryptographic inventory is the named control gap this article exposes. The article assumes organisations can migrate what they can see, yet unmanaged keys, host identities, and certificate sprawl make that assumption false. That control gap is what turns PQC planning into a multi-year remediation effort rather than a standard upgrade. The implication is that inventory quality determines migration speed.

OT and long-lived infrastructure make quantum migration structurally harder than standard enterprise refresh cycles. Legacy systems, delayed maintenance windows, and embedded device trust chains reduce the tolerance for fast replacement. In those environments, quantum-safe readiness is constrained by lifecycle, vendor support, and operational uptime rather than by standards availability alone. The implication is that infrastructure age must shape prioritisation logic.

Post-quantum migration should be sequenced by trust dependency, not by technology preference. Organisations that start with the newest systems often miss the identities and certificates whose compromise would matter most. A better ordering starts with assets that anchor authentication, control access, or sign firmware across long-lived environments. The implication is that programme sequencing should follow identity criticality and data lifespan together.

From our research:

• 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
• Lack of credential rotation is cited as the top cause of NHI-related attacks by 45% of organisations, followed by inadequate monitoring and logging at 37% and over-privileged accounts at 37%.
• For the migration angle, Ultimate Guide to NHIs , Key Challenges and Risks gives the broader control context for visibility, sprawl, and unmanaged credentials.

What this signals

Cryptographic inventory will become a programme-level dependency for any serious PQC roadmap. The organisations that move fastest will be the ones that already know where identity trust depends on certificates, host keys, and legacy algorithms. Without that map, migration effort turns into discovery debt, then into delayed remediation.

A useful way to think about the transition is as a trust-lifecycle problem: where does authentication depend on cryptography that will not survive the next hardware era? That question belongs alongside access reviews and key management, especially in estates with long-lived OT and regulated records.

For teams that need a broader NHI lens, the inventory problem is the same pattern seen in unmanaged service credentials and OAuth sprawl. The control failure is visibility first, then governance. That is why quantum readiness should be planned with identity lifecycle, not isolated cryptography workstreams.

For practitioners

• Inventory cryptographic dependencies across identity paths Map where certificates, keys, host identities, SSH algorithms, and firmware signatures support authentication or trust decisions. Include OT and legacy systems, because those dependencies are often the hardest to replace and easiest to miss in manual reviews.
• Prioritise data by confidentiality lifespan Classify information by how long it must remain secret, then place long-lived records and industrial data ahead of short-retention assets in your PQC roadmap.
• Sequence migration by trust criticality Start with the identities and systems that anchor access, session setup, and code validation. That reduces the chance that a single legacy trust point delays the broader programme.
• Use discovery to build audit-ready remediation plans Create a defensible inventory of unmanaged keys and associated risk levels so the migration plan can support compliance, change management, and budget decisions.

Key takeaways

• Quantum risk reaches identity governance because certificates, keys, and signatures underpin how systems prove trust.
• Harvest now, decrypt later makes retention length part of the threat model, so long-lived data deserves priority now.
• A complete cryptographic inventory is the practical prerequisite for any credible post-quantum migration plan.

Key terms

• Post-Quantum Cryptography: Post-quantum cryptography is cryptographic protection designed to resist attack from a cryptographically relevant quantum computer. In practice, it means replacing or augmenting current public key systems with algorithms intended to preserve authentication, key exchange, and signatures after quantum decryption becomes feasible.
• Harvest Now, Decrypt Later: Harvest now, decrypt later is a delayed attack strategy in which adversaries steal encrypted data today and wait until future compute power can decrypt it. The risk depends on how long the data remains valuable, which makes retention horizon and confidentiality lifespan critical governance inputs.
• Cryptographic Inventory: A cryptographic inventory is a complete record of where keys, certificates, algorithms, and trust dependencies are used across systems. For identity teams, it is the prerequisite for assessing exposure, planning migration, and proving which authentication or signing paths still rely on legacy cryptography.

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.

This post draws on content published by SSH Communications Security: quantum-safe migration, cryptographic visibility, and PQC readiness. Read the original.