TL;DR: Core post-quantum infrastructure migration will finish by 2029, with TLS and certificate systems moving in stages to avoid breaking existing customers while reducing harvest-now, decrypt-later exposure, according to DigiCert. The shift shows that cryptographic agility and certificate lifecycle governance are now identity security priorities, not future research.
At a glance
What this is: This is DigiCert’s analysis of its 2029 post-quantum migration plan, with the main finding that certificate lifecycle and TLS modernization have become identity governance priorities, not just cryptography work.
Why it matters: IAM, PKI, and NHI teams need to treat post-quantum readiness as a lifecycle and governance problem because certificate automation, vendor coordination, and legacy dependency management now shape security outcomes.
Context
Post-quantum cryptography migration is the process of moving TLS and certificate infrastructure to algorithms designed to resist future quantum attacks. In this article, DigiCert frames that migration as an operational programme that touches internal PKI, customer-facing services, browser support, and certificate lifecycle automation.
For identity teams, the important shift is that cryptographic transition is no longer isolated from governance. Certificate issuance, algorithm agility, dependency inventory, and offboarding of legacy key exchange all sit inside the same lifecycle discipline that already governs NHI credentials and workload identities.
Key questions
Q: How should IAM and infrastructure teams prioritise post-quantum migration?
A: Prioritise internet-facing assets, then move to the cryptographic assets with the longest replacement lead times and the weakest inventory. That sequencing reduces exposure quickly while avoiding the mistake of treating every system as equally urgent.
Q: Why does post-quantum migration matter for identity governance?
A: Because identity governance does not stop at user access. It also governs the trust chain behind certificates, signing keys, and time-stamping services that prove identity over long periods. If those artefacts outlive their cryptographic assumptions, the programme inherits hidden exposure that only lifecycle planning can surface.
Q: What breaks when classical key exchange stays in place too long?
A: Harvest-now, decrypt-later risk remains active, and the organisation keeps protecting sensitive traffic with trust assumptions that are already on borrowed time. The longer legacy support lasts, the larger the archive of ciphertext that may become readable later.
Q: Should organisations use hybrid post-quantum deployments during migration?
A: Yes, if hybrid support is the bridge that preserves service continuity, but it should not become the destination. Hybrid deployments can reduce disruption during transition, yet they still leave the organisation managing two trust models at once, which raises lifecycle complexity.
Technical breakdown
Why TLS migration has to happen in stages
TLS post-quantum migration cannot be treated as a single flag flip because existing clients, libraries, embedded systems, and vendor termination services will not all support the same cipher suites at the same time. In practice, organisations need universal TLS 1.3 support first, then customer migration, and only later removal of classical key exchange. That sequencing matters because compatibility debt becomes a security constraint, not just an operational inconvenience. If legacy support stays in place too long, harvest-now, decrypt-later risk remains alive while infrastructure appears modernised.
Practical implication: inventory TLS dependencies before changing cipher policy, because migration sequencing is the control.
Certificate automation is the real governance boundary
Post-quantum certificates are not just a new cryptographic format. They push the governance boundary into issuance workflows, lifecycle automation, and ecosystem acceptance from CAs, browsers, TLS libraries, and standards bodies. Once certificate sizes grow and algorithms change, manual handling becomes harder and lifecycle drift becomes more dangerous. That is why certificate operations, not only cryptographic selection, determine whether PQC adoption stays controlled or becomes fragmented across environments.
Practical implication: treat certificate automation and inventory accuracy as part of the PQC control plane.
Harvest-now, decrypt-later is an identity risk as well as a crypto risk
Harvest-now, decrypt-later threats exploit the delay between data capture and future decryption capability. The exposure is often created by identity systems that still depend on classical certificates, long-lived trust chains, and delayed migration across internal and customer environments. In that sense, PQC readiness is a governance problem about how long sensitive trust material remains usable under legacy assumptions. The article’s key point is that the risk exists before a CRQC is publicly confirmed, because the collection of traffic and certificates is happening now.
Practical implication: prioritise high-value trust paths and long-retention data first, not just the most visible certificate estate.
Threat narrative
Attacker objective: The attacker wants to accumulate ciphertext and trust artifacts now so they can decrypt protected communications later.
- entry via continued collection of encrypted traffic and certificate-bearing trust material before post-quantum migration is complete.
- credential_harvested through long-lived classical key exchange and legacy certificate dependencies that remain usable for future decryption.
- escalation occurs when delayed migration preserves recoverable ciphertext across internal and customer-facing systems.
- impact is future disclosure of sensitive data once quantum capability or equivalent cryptanalytic power makes recovery practical.
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.
- GitHub code signing certificate theft 2022: A machine account's compromised token cloned GitHub's Desktop and Atom repos, exposing encrypted signing certificates later revoked.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 150+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Certificate lifecycle governance is now a post-quantum identity control, not a peripheral PKI task. The article shows that PQC migration spans issuance, automation, dependency inventory, and retirement of legacy trust paths. That means certificate governance now sits inside the same operational discipline as NHI lifecycle management, where ownership, rotation, and offboarding determine exposure. Practitioners should treat cryptographic agility as a governance capability, not a one-time migration project.
Legacy key exchange creates trust debt that compounds until it is removed. DigiCert’s staged approach is a reminder that coexistence periods are not neutral. Every retained classical connection extends the window in which harvest-now, decrypt-later collection remains worthwhile. The implication for the field is that migration programmes must measure how much trust remains dependent on older algorithms, not just whether PQC support exists somewhere in the stack.
Post-quantum readiness exposes the weakness of static lifecycle assumptions. Certificate programmes have often assumed that cryptographic primitives change slowly enough for periodic refresh cycles to be sufficient. That assumption breaks when standards, browsers, libraries, and vendors must all move together under deadline pressure. The governance lesson is that lifecycle management must be able to absorb coordinated ecosystem change, or the identity plane becomes the slowest part of security modernisation.
Hybrid support is a transition strategy, not a governance destination. The article makes clear that some customers will need hybrid deployments during migration, but also that hybrid arrangements do not solve the underlying long-term problem. They delay a final decision about trust architecture while preserving operational continuity. Practitioners should therefore evaluate hybrid mode as a controlled bridge, not as the end state for certificate governance.
Merkle Tree Certificates highlight that PQC changes the shape of trust, not just the algorithm behind it. The article’s discussion of MTCs shows that larger certificates and transparency scalability are now architecture-level issues. That shifts the conversation from single-certificate management to system-level trust scalability across issuance, observability, and validation. Identity teams should expect PQC programmes to affect architecture choices far beyond cipher selection.
What this signals
Certificate lifecycle management will increasingly sit inside identity governance roadmaps. PQC forces IAM, PKI, and platform teams to coordinate around issuance automation, dependency mapping, and retirement planning. The programme question is no longer whether certificates are secure today, but whether the trust lifecycle can be changed at the pace the ecosystem now requires.
Post-quantum readiness is a supply-chain and lifecycle problem before it is a standards problem. Browser support, library support, vendor readiness, and internal automation all need to move together. Teams that only track algorithm names will miss the operational dependencies that determine whether migration succeeds.
Legacy cryptography creates a hidden exposure window that grows with retention time. If sensitive traffic is likely to be valuable later, keeping classical key exchange alive extends the useful life of captured data. That is why prioritisation should follow data value and retention, not just endpoint visibility.
For practitioners
- Inventory certificate and TLS dependencies Map all internal and external TLS endpoints, certificate chains, termination services, and legacy client dependencies before changing crypto policy.
- Classify systems by migration readiness Separate browser-supported paths, modern libraries, embedded systems, and long-lived platforms so sequencing reflects actual compatibility constraints.
- Automate certificate issuance and lifecycle workflows Extend PKI automation to cover issuance, renewal, algorithm transition, and retirement so PQC certificates do not create manual bottlenecks.
- Prioritise high-value encrypted data paths Focus first on systems that protect sensitive or long-retention traffic, because those are the assets most exposed to harvest-now, decrypt-later collection.
- Coordinate migration with vendors and standards bodies Track browser, IETF, CA/B Forum, and library readiness as external dependencies that can accelerate or delay practical deployment.
Key takeaways
- Post-quantum migration is now a certificate governance issue because identity systems depend on the same lifecycle controls that manage trust at scale.
- The article’s 2029 plan shows that compatibility, automation, and external ecosystem readiness will determine migration success more than algorithm choice alone.
- Practitioners should inventory TLS dependencies early, automate certificate lifecycle changes, and retire classical key exchange on a staged basis.
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 | Classical certificates and long-lived trust paths extend exposure during PQC migration. |
| NHI-01 — Improper Offboarding | Legacy trust material must be removed cleanly when migration completes. | |
| Recommendation — Reduce long-lived trust exposure by shortening certificate lifetimes and retiring classical key exchange on schedule. Offboard classical cryptographic paths as deliberately as any other identity credential. | ||
| NIST SP 800-57 | Part 1 — Key Management Lifecycle | The article centres on cryptographic lifecycle planning, transition, and retirement. |
| Recommendation — Apply key lifecycle governance to plan migration, transition, and destruction of obsolete cryptographic material. | ||
| NIST CSF 2.0 | PR.DS-01 — Data-at-rest is protected | PQC migration is meant to preserve confidentiality of protected data against future decryption. |
| PR.AA-05 — Access Permissions, Entitlements and Authorizations | Certificates are authentication artifacts that govern trusted access across systems. | |
| Recommendation — Reassess data-protection controls where encrypted data may remain valuable long enough to face future decryption. Treat certificate-based authentication as an authorisation boundary that must be governed through lifecycle controls. | ||
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.
- Certificate Lifecycle Management: The governance of digital certificates from issuance through renewal and revocation, ensuring certificates are valid, monitored, and rotated before expiry. Expired certificates are a leading cause of outages and unplanned security gaps.
- 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 agility: The ability to change cryptographic algorithms, key lengths, or trust models without reworking every application. For machine identities, it reduces the risk that long-lived services will fail when standards shift or when post-quantum migration becomes necessary.
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 23, 2026.
Updated on October 8, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org