TL;DR: Google's 2029 quantum-safe target compresses the post-quantum cryptography timeline and exposes how few organisations have a migration roadmap, according to AppViewX. Crypto-agility now matters because identity, certificates and signed tokens all depend on algorithms that may fail before most programmes are ready.
At a glance
What this is: NHI Mgmt Group's analysis, drawing on AppViewX's blog post: Google's 2029 quantum-safe target compresses PQC migration planning, and most organisations still lack the inventory and roadmap needed to move.
Why it matters: Identity, machine identity and workload programmes depend on cryptography that must be discoverable, swappable and governed before algorithm changes become operationally urgent.
By the numbers:
- Google is targeting 2029 to be quantum-safe.
Context
Post-quantum cryptography is no longer a distant standards question. It is a programme-design problem about how quickly organisations can discover where RSA and ECC are embedded, then replace them without breaking identity, certificates, signing flows or dependent systems.
The key governance gap is visibility: many enterprises cannot map their cryptographic estate across certificates, code signing, HSMs, SaaS, legacy applications and machine identities. That creates a migration blind spot long before the first PQC rollout begins.
For identity and security teams, the issue is not simply algorithm change. It is whether the organisation can inventory, prioritise and rotate cryptographic dependencies quickly enough to stay ahead of Q-day pressure.
Key questions
Q: How should teams inventory cryptographic assets before PQC migration?
A: Teams should inventory every cryptographic asset by key type, algorithm, certificate issuer, key length, usage, expiry, and where it is embedded, including code, HSMs, secrets stores, and device firmware. A machine-readable form means a structured asset register that can be queried and matched to owners, dependencies, and renewal workflows. Without that inventory, PQC migration misses hidden certificates, API keys, and signing chains.
Q: Why does PQC migration depend on crypto-agility?
A: PQC migration depends on crypto-agility because systems must be able to swap algorithms, key sizes and certificate formats without redesigning the whole service. Crypto-agility uses abstraction layers, configurable libraries, protocol negotiation and certificate lifecycle controls so organisations can move from legacy algorithms to post-quantum ones as standards, vendors and interoperability requirements change.
Q: Why is harvest now, decrypt later a current risk?
A: Because the attacker does not need quantum capability today to create value from stolen ciphertext. If encrypted data can be exfiltrated and stored now, it may become readable later when quantum techniques mature. That means the risk window already exists for long-lived sensitive information, especially where retention periods are measured in years.
Q: What should teams prioritise before the 2029 quantum-safe deadline?
A: Teams should first prioritise high-value data, long-lived secrets, and systems that handle public-key encryption, digital signatures or certificate-based trust. Those dependencies usually take the longest to change, so inventory them early, identify protocol and library constraints, and plan hybrid deployments, certificate replacement and testing before the 2029 quantum-safe deadline.
Technical breakdown
Why cryptographic inventory is the first PQC control
Post-quantum migration starts with an inventory of every place cryptography is used, including certificates, signing keys, TLS endpoints, code-signing pipelines, HSM-backed keys and embedded device identities. Without that map, teams cannot assign ownership, sequence migration waves or identify dependencies that will break when algorithms change. The problem is not just volume. Cryptographic use is often hidden inside application libraries, managed services and older operational tooling, so the real scope is larger than the asset list most organisations keep today. See the Machine Identity, PKI and Certificate Lifecycle Guide.
Practical implication: Build a cryptographic asset inventory that tracks owner, purpose, algorithm, expiry and system dependency for every identity-bearing credential.
Crypto-agility is the architectural requirement behind PQC
Crypto-agility means the environment can swap one approved algorithm for another without redesigning every dependent application or trust chain. In practice, that requires abstraction in certificate management, clean key boundaries, policy-driven issuance and testing paths that can validate new algorithms before production cutover. The architectural challenge is that many identity and application stacks assume static algorithms for years at a time, which makes replacement expensive when standards move quickly. See the Crypto-Agility Guide.
Practical implication: Design issuance, validation and trust workflows so algorithm changes can be introduced by policy rather than by rebuild.
Harvest now, decrypt later turns long-lived data into a current risk
Harvest now, decrypt later is the strategy of collecting encrypted traffic or stored data today and waiting until quantum-capable decryption becomes practical. That matters because confidentiality risk is determined by data lifetime, not just current cipher strength. Records with long retention, such as IP, biometrics, M&A material and government communications, are already exposed to future decryption if they remain protected only by legacy public-key schemes. See the Harvest Now Decrypt Later Risk Assessment Template.
Practical implication: Classify data by confidentiality shelf life and treat long-retention information as the first migration priority.
Threat narrative
Attacker objective: The attacker aims to preserve encrypted material now so it can be decrypted or reinterpreted later when quantum capability closes the current protection gap.
- Entry occurs through passive collection of encrypted traffic, stored records or signed material that remains protected under current algorithms.
- Credential or data value is preserved in encrypted form until future quantum capability makes the captured material economically recoverable.
- Impact would arrive later, when decrypted records, signatures or trust chains can be reused to expose confidential information or undermine authenticity.
Breaches seen in the wild
- Google API Keys Exposure — Gemini AI: Google API keys exposed in client-side code via Gemini AI integrations, creating data leak risk.
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 is now an identity governance control, not a pure crypto task. Every certificate, signed token and machine identity depends on algorithms that will not age evenly across the estate. That means ownership, lifecycle and dependency mapping matter as much as cipher choice. Practitioners should treat visibility into cryptographic assets as a prerequisite for any credible PQC programme.
Crypto-agility is the new assumption test for identity infrastructure. The old assumption was that algorithms could remain stable for the lifetime of a platform. That assumption fails when standards shift within a migration window shorter than many platform refresh cycles. The implication is that teams must re-evaluate which identity and trust flows can be changed by policy alone and which are structurally hard-coded.
Quantum-safe readiness exposes a standing privilege problem for cryptography. Long-lived certificates, keys and signed trust chains behave like standing access: they remain usable long after the conditions that created them change. That makes rotation, expiry and algorithm substitution part of the same governance conversation, not separate workstreams.
Harvest now, decrypt later is a programme-level risk, not a future scenario. Data with long confidentiality shelf life already carries quantum exposure today because the attacker only needs persistence, not immediate decryption. Security leaders should treat retention, cryptographic dependence and migration sequencing as one control problem, with the highest priority on the information that must stay secret longest.
Google's 2029 target compresses the market's tolerance for ambiguity. The field no longer has the luxury of framing PQC as a research topic or a future standardisation exercise. Practitioners now need a governed migration path that begins with discovery and ends with algorithm flexibility across the identity estate.
From our research library:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
- 96% of security operations teams report critical blind spots, most commonly in cloud infrastructure (74%) and identity and access behaviour (67%).
- Read next: Machine Identity, PKI and Certificate Lifecycle Guide
What this signals
Cryptographic visibility debt: most migration failures begin long before the algorithm change itself, when teams cannot see where cryptography is embedded across identity, application and infrastructure layers. The practical consequence is that PQC programmes will be won or lost on inventory quality, not on the final cutover date.
PQC planning now needs to align with asset life rather than project milestones. If an identity trust chain or data set must remain confidential for a decade, the organisation has to treat quantum-safe replacement as a near-term governance issue, not a future research item.
The market will keep moving from awareness to dependency management. Organisations that can separate discoverability, algorithm flexibility and retirement timing will be able to govern the transition; those that cannot will discover their exposure only when they are already behind schedule.
For practitioners
- Inventory cryptographic assets first Map every certificate, key, signed token, TLS endpoint, HSM dependency and code-signing flow before setting migration priorities.
- Rank assets by confidentiality shelf life Prioritise data and trust chains that must remain secret for years, including IP, biometrics, government material and M&A records. See the Harvest Now Decrypt Later Risk Assessment Template.
- Design for algorithm substitution Separate identity issuance and validation logic from hard-coded algorithms so new PQC choices can be introduced without platform redesign.
- Build a pilot path before 2029 Test PQC algorithms in non-critical environments and validate application compatibility before any broad production cutover.
Key takeaways
- The core risk is not abstract quantum theory but the gap between a 2029 target and the time required to discover, prioritise and replace cryptographic dependencies.
- Evidence cited in the source shows that most organisations still lack a PQC roadmap, which means migration planning is behind the threat curve.
- A credible response starts with cryptographic inventory, then moves to crypto-agility and phased testing so algorithm changes do not force a redesign.
Related NHI Mgmt Group resources: Machine Identity, PKI and Certificate Lifecycle Guide · Crypto-Agility Guide · Harvest Now Decrypt Later Risk Assessment Template · Post-Quantum Cryptography Deadlines Tracker
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 addresses 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 |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-07 — Long-Lived Secrets | Long-lived cryptographic trust material creates the same exposure window this article warns about. |
| NHI-05 — Overprivileged NHI | Certificates, keys and machine identities can accumulate more trust than they need over time. | |
| Recommendation — Shorten the lifetime of cryptographic trust material and track when algorithms must be replaced. Review machine identity scope so cryptographic credentials only carry the access they actually require. | ||
| NIST SP 800-57 | Part 1 — Key Management Lifecycle | The article is about planning the lifecycle transition for cryptographic keys and algorithms. |
| Recommendation — Govern key lifecycle decisions so replacement, retirement and algorithm migration happen on a managed schedule. | ||
| NIST CSF 2.0 | ID.AM-02 — Software, Hardware, Data, and Systems Are Inventory Managed | PQC migration starts with discovering where cryptography lives across the environment. |
| PR.DS-01 — Data-at-Rest Is Protected | Harvest now, decrypt later creates future exposure for retained data protected by current algorithms. | |
| Recommendation — Inventory cryptographic dependencies so migration scope, ownership and risk can be assigned accurately. Classify stored data by retention horizon and align stronger protection with long-lived confidentiality needs. | ||
Key terms
- 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.
- 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.
- 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
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 November 6, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org