TL;DR: Google’s internal move to a 2029 post-quantum migration horizon compresses planning runway for RSA and ECC-dependent systems, while Keyfactor cites a 48% readiness gap and 91% of organisations lacking a PQC roadmap. The real issue is cryptographic agility: infrastructure that cannot swap algorithms cleanly will turn future migration into a long, brittle recovery project.
At a glance
What this is: This analysis says Google’s 2029 post-quantum deadline shifts the planning problem from long-range theory to immediate cryptographic agility and inventory work.
Why it matters: It matters because identity, signing, and trust systems that cannot swap algorithms cleanly will turn PQC migration into a prolonged governance and operational risk for IAM, PKI, and NHI programmes.
Context
Post-quantum cryptography planning is no longer a distant architecture exercise. When a major platform operator moves its internal migration horizon to 2029, the real issue becomes whether organisations can discover, classify, and replace RSA and ECC dependencies before the window closes.
The governance gap is cryptographic agility, meaning the ability to change algorithms, certificates, and trust dependencies without redesigning applications or replacing infrastructure. That gap cuts across identity signing, workload authentication, and software trust, so it affects human IAM, NHI, and platform security programmes at the same time.
Key questions
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.
Q: Why do digital signatures matter more than encryption in PQC planning?
A: Digital signatures validate software, devices, federation, and workload trust, so failure affects the mechanism that proves something is genuine. Encryption loss is serious, but signature compromise can collapse trust across infrastructure. That is why signature systems and certificate chains should be prioritised early in migration planning.
Q: What breaks when cryptographic systems are not agile?
A: Systems that hardcode algorithms or bind trust to one certificate format become expensive and slow to replace. When post-quantum standards change, those environments cannot adapt cleanly, and migration turns into a multi-year operational project. In identity terms, brittle crypto creates trust debt that eventually has to be repaid.
Q: When should organisations prioritise PQC planning over waiting for final standards?
A: They should start now when key identity, signing, or long-lived data protection depends on RSA or ECC. Waiting for every standard to settle risks missing the preparation window, especially where inventories are incomplete and dependencies span multiple systems. Early planning reduces rework and disruption.
Technical breakdown
Why crypto agility is the real control gap
Crypto agility is the ability to swap cryptographic algorithms, policies, and trust anchors without rebuilding the surrounding system. That matters because many environments hardcode RSA or ECC assumptions into applications, certificate lifecycles, device firmware, and signing pipelines. Once those assumptions are embedded, migration becomes a multi-year dependency project rather than a controlled change. For IAM and NHI teams, the problem is not just the algorithm in use but where trust decisions are fixed in code, policy, and operational workflow.
Practical implication: Map where cryptographic choices are hardcoded so migration work starts with dependency removal, not algorithm replacement.
Why digital signatures are a harder PQC problem than encryption
Encryption protects confidentiality, but signatures protect trust, provenance, and authentication. That distinction makes signatures more disruptive because they sit in certificate chains, software signing, identity federation, and workload attestation. A broken signature model does not create one exposed dataset; it undermines the ability to verify who or what should be trusted across the stack. That is why signature migration needs earlier attention than many teams give it, especially where long-lived keys authenticate systems or sign code.
Practical implication: Prioritise signing workflows, certificate chains, and workload trust paths before treating data encryption as the main PQC workstream.
Why inventory determines whether PQC is manageable
A PQC programme starts with visibility into every algorithm, certificate, key, and dependency in scope. Without that inventory, teams cannot separate low-risk dependencies from long-lived trust anchors that support critical services. This is especially important in identity infrastructure, where a single certificate profile may support authentication, signing, and federation across multiple systems. If the inventory is incomplete, the migration timeline becomes guesswork and the operational blast radius grows as soon as standards shift.
Practical implication: Build a complete cryptographic inventory that includes certificates, signing paths, and downstream systems that inherit those trust relationships.
Threat narrative
Attacker objective: The objective is to undermine confidentiality and trust by exploiting cryptographic systems that were assumed to remain safe for years.
- Entry occurs through long-lived RSA and ECC dependencies embedded in applications, signatures, certificates, and trust systems before quantum risk is fully visible to operators.
- Escalation happens when those cryptographic assumptions remain unchanged while quantum capability improves, widening the window in which harvested data and embedded trust can be broken later.
- Impact is systemic trust failure, where authentication, software provenance, and encrypted data protection all become exposed to future decryption or forgery.
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
Crypto agility has become the governing control, not a nice-to-have capability. The article shows why algorithm choice alone is too narrow a frame. Organisations need systems that can change cryptographic primitives without breaking applications, certificate chains, or signing trust. The practitioner conclusion is simple: if crypto cannot be swapped cleanly, PQC migration becomes operational debt rather than resilience.
Long-lived signature keys are the highest-value PQC exposure. Encryption loss is serious, but signature compromise is more structural because it breaks authentication, provenance, and federation trust across many systems at once. That means identity programmes should treat signing dependencies as a first-class migration risk, not a background certificate hygiene issue. The practitioner conclusion is to prioritise trust anchors that authenticate systems and software, not just data-at-rest controls.
The 2029 horizon exposes a crypto inventory problem as much as a quantum problem. The article’s real warning is that many organisations still cannot answer where RSA, ECC, or certificate dependencies live across their environment. That is a governance failure because you cannot sequence migration without visibility into what depends on what. The practitioner conclusion is to treat inventory as the prerequisite control for every downstream PQC decision.
Q-Day planning now intersects directly with identity and software trust governance. This is not only a cryptography issue for platform teams. It affects workload identity, certificate issuance, federation, code signing, and the lifecycle of trust across human and machine systems. The practitioner conclusion is that IAM, PKI, and platform security teams need a shared migration model, not separate plans.
Cryptographic migration windows are shrinking faster than most governance cycles can absorb. The article’s message is that deadline uncertainty is itself the risk, because waiting for perfect standard stability guarantees late action. Organisations that defer work until the final algorithm settles will face the most expensive and disruptive transition path. The practitioner conclusion is to design for continuous cryptographic change now, not one-off replacement later.
What this signals
Crypto inventory is the gating control for PQC readiness: if an organisation cannot identify where RSA, ECC, certificates, and signing dependencies live, it cannot sequence migration or measure exposure. For IAM and PKI teams, that means the first programme signal is not algorithm choice but whether discovery covers every trust anchor and downstream system.
The migration lesson extends beyond cryptography into identity governance. Workload identity, federation, and code-signing paths all inherit cryptographic assumptions, so PQC planning should be owned as a shared control problem across platform, PKI, and IAM rather than a standalone security project.
For practitioners
- Map every cryptographic dependency Inventory certificates, algorithms, signing services, federation dependencies, and embedded trust assumptions across applications and infrastructure.
- Prioritise long-lived signature keys Rank systems that use signatures for authentication, software trust, or workload attestation ahead of routine encryption-only use cases.
- Design for algorithm substitution Remove hardcoded cryptographic choices from applications and control planes so algorithms can be changed without re-architecting services.
- Align PKI and IAM planning Coordinate certificate lifecycle, identity federation, and workload trust owners around one migration roadmap instead of separate remediation tracks.
Key takeaways
- Google’s 2029 timeline shows that post-quantum planning is moving from future concern to current governance work.
- The hardest risk is not encryption alone but the identity, signing, and provenance systems that depend on long-lived cryptographic trust.
- Organisations need cryptographic inventory and algorithm agility before they can make PQC migration predictable.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-57, NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-57 | Part 1 — Key Management Lifecycle | The article is centered on cryptographic lifecycle planning and algorithm transition. |
| Recommendation — Use Part 1 to govern crypto inventory, algorithm transition, and key lifecycle planning for PQC. | ||
| NIST CSF 2.0 | PR.DS-01 — Data-at-Rest | PQC readiness affects how data confidentiality is protected over time. |
| Recommendation — Apply PR.DS-01 to review how long-lived data protection depends on current cryptographic choices. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Identity and signature dependencies rely on lifecycle control of authenticators and related cryptographic material. |
| Recommendation — Use IA-5 to manage credential and authenticator lifecycles that depend on cryptographic transition planning. | ||
| ISO/IEC 27001:2022 | A.8.24 — Use of Cryptography | The article directly concerns cryptographic governance and transition. |
| Recommendation — Apply A.8.24 to inventory cryptographic use and plan controlled migration to PQC-ready mechanisms. | ||
Key terms
- 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.
- 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.
- Digital Signature: A verifiable cryptographic result created with a private key and checked with the matching public key. In identity systems, it is used to prove possession of a secret without revealing that secret, which makes it useful for authentication and non-repudiation.
- 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 responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.
Published by the NHIMG editorial team on June 12, 2026.
Updated on October 10, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org