TL;DR: The Department of War’s November memorandum makes cryptography inventory, named migration leads, test artifacts, and approval gates mandatory, while also rejecting quantum key distribution as a confidentiality substitute and setting phase-out expectations for weaker key-establishment approaches, according to DigiCert. The real message is that crypto-agility, not optimism, now determines whether identity and certificate programmes can survive post-quantum transition.
At a glance
What this is: This is DigiCert’s analysis of the Department of War’s post-quantum cryptography memorandum and the operational pressure it creates around inventory, approvals, and algorithm agility.
Why it matters: It matters because cryptography migration now touches certificate lifecycle, workload identity, and PKI governance, so IAM and NHI teams need a plan before legacy algorithms become an exposure window.
Context
Post-quantum cryptography migration is now an identity and certificate governance problem, not just a cryptography problem. The core issue is that organisations cannot defend or replace what they have not inventoried, and crypto estates are often scattered across applications, embedded systems, operational technology, and service identities.
DigiCert frames the Department of War memorandum as a forcing function because it requires component-level inventories, named migration leads, and evidence before testing or deployment. That changes the programme from abstract readiness work into owned, auditable lifecycle management for cryptographic dependencies.
For IAM and NHI practitioners, the practical question is how to treat certificates, keys, and algorithm choices as governed assets with lifecycle, ownership, and change control. The article’s message is that crypto-agility has to be designed into certificate operations before post-quantum transition becomes mandatory everywhere.
Key questions
Q: What breaks when endpoint cryptography is not included in PQC migration?
A: Migration breaks when teams cannot see where vulnerable algorithms and long-lived trust material exist on PCs, so they cannot prioritise remediation or align it to device lifecycle events. The organisation may modernise central systems while leaving the access layer exposed, which weakens both security outcomes and audit confidence.
Q: Why do pre-deployment tests matter so much for PQC rollout?
A: Algorithm changes can break certificate parsing, trust chaining, device compatibility, and signing workflows even when the cryptographic standard is sound. Test evidence shows whether the real system can survive the transition, not just whether the algorithm is approved. For that reason, approval gates belong before production deployment, not after the fact.
Q: When should organisations prioritise algorithm agility over algorithm selection?
A: They should prioritise agility as soon as cryptography spans multiple applications, embedded assets, or service identities, because the hardest problem is often changing algorithms safely rather than choosing one. Agility preserves operational continuity while standards mature. In identity and PKI programmes, that makes lifecycle design more important than a single migration choice.
Q: What is the difference between Quantum Key Distribution and post-quantum cryptography?
A: Quantum Key Distribution uses quantum states of light to distribute keys and detect interception at the physical layer. Post-quantum cryptography uses mathematical algorithms designed to resist classical and quantum attacks. QKD needs specialized links and hardware, while post-quantum cryptography can be deployed in software on existing infrastructure. They solve related problems, but through different security assumptions.
Technical breakdown
Why cryptographic inventory is now the first control
Cryptographic inventory is the discovery layer for PQC migration. It means identifying every place cryptography is used, including certificates in business applications, embedded keys in operational technology, code-signing keys, and service-to-service certificates. Without that map, teams cannot assign ownership, estimate migration risk, or sequence change safely. The memo’s requirement for component-level inventories and named migration leads turns cryptography into a governed estate rather than an invisible dependency. In identity programmes, that matters because certificates and keys are part of machine identity, not just transport security.
Practical implication: build a complete cryptographic inventory before selecting algorithms or migration timelines.
What algorithm agility means for PKI and certificate lifecycle
Algorithm agility is the ability to issue, manage, rotate, and revoke certificates without assuming one cryptographic algorithm will remain valid for the lifetime of the system. In practice, this requires PKI that can support multiple algorithm profiles, interoperability testing, and controlled rollover paths. If certificate tooling cannot accommodate algorithm change, the organisation is locked into legacy assumptions that break under post-quantum transition. For identity teams, algorithm agility is not a feature request. It is the mechanism that keeps workload identity, device identity, and service trust usable when algorithms change.
Practical implication: validate whether PKI and issuance workflows can support algorithm change without redesigning the trust model.
Why testing and approval gates matter before PQC deployment
The memo requires test plans, results, and approvals before proceeding because algorithm change can create interoperability failures, rollback problems, and hidden dependencies. A cryptographic swap that looks clean at the algorithm layer can still break certificate parsing, device compatibility, signing workflows, or trust chaining in production. That is why pre-deployment evidence matters. For IAM and NHI practitioners, this is a governance lesson as much as a technical one: migration cannot be assumed safe because a standard exists. It has to be proven in the actual dependency graph.
Practical implication: require test artifacts and interoperability evidence before any PQC production rollout.
Breaches seen in the wild
- 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
Crypto inventory is now a governance prerequisite, not a documentation task. The DoW memo makes ownership and component-level discovery mandatory because migration cannot be managed without knowing where cryptography exists. That changes the operating model for identity, PKI, and device trust programmes. The practitioner conclusion is simple: if you cannot inventory it, you cannot migrate it.
Algorithm agility is the real control objective. The point is not to pick a single post-quantum winner and wait for deployment. The point is to keep certificate and trust systems capable of changing algorithms without service interruption or identity rebuilds. That is the difference between a one-time cryptography project and a durable trust programme. The practitioner conclusion is to treat agility as a lifecycle requirement, not a later optimisation.
Quantum key distribution does not solve the governance problem the memo is trying to solve. The article is explicit that QKD is not a substitute for standard-based PQC in confidentiality and identity protection. That means the programme risk is not just technical misunderstanding but false assurance from marketing language that bypasses testable migration paths. The practitioner conclusion is to anchor decisions in auditable algorithm transition, not quantum branding.
Post-quantum migration collapses the distinction between PKI operations and identity governance. Certificates, code-signing keys, service-to-service trust, and embedded identities are all part of the same control plane once migration pressure starts. Organisations that still separate cryptography planning from IAM or NHI lifecycle management will miss dependencies and create blind spots. The practitioner conclusion is to govern cryptography as part of identity lifecycle, not as a standalone security silo.
What this signals
Crypto inventory becomes the migration control plane: organisations should expect PQC readiness to merge certificate lifecycle, asset discovery, and ownership tracking into one programme. The practical shift is away from isolated cryptography decisions and toward governed dependency management across workload identity, device identity, and application trust.
Teams that treat PQC as a standards wait-and-see exercise will fall behind the operational reality described here. The memo’s structure implies that migration readiness will be judged by evidence, testability, and accountable ownership, not by intent or roadmap language.
For practitioners
- Inventory every cryptographic dependency Map certificates, keys, embedded identities, service-to-service trust, and code-signing assets so each has a named owner and migration path.
- Assign named migration leads Give each component and business service a responsible owner who can approve scope, track dependencies, and coordinate change control.
- Demand testable migration evidence Require documented test plans, interoperability results, and deployment approval artifacts before any PQC rollout reaches production.
- Build for algorithm agility Design PKI and certificate lifecycle workflows so algorithms can change without replacing the trust model or rebuilding issuance processes.
Key takeaways
- The article shows that PQC migration is fundamentally a governance and inventory problem, not just an algorithm update.
- The DoW directive adds evidence, ownership, and approval requirements that make unsupported migration plans increasingly fragile.
- Identity and certificate teams need algorithm agility built into lifecycle processes before legacy cryptography becomes a long-lived risk.
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-53 Rev 5, NIST CSF 2.0 and NIST SP 800-57 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-05 — Overprivileged NHI | Crypto inventories expose where machine identities and certificates carry excessive trust scope. |
| NHI-07 — Long-Lived Secrets | Legacy certificates and keys become stale trust material when algorithms cannot change cleanly. | |
| Recommendation — Review certificate and service identity scope so migration does not preserve excess privilege. Shorten secret and certificate lifecycles where algorithm rollover is not yet supported. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Credential lifecycle controls apply directly to certificate and key rotation under PQC pressure. |
| Recommendation — Apply authenticator management controls to certificate issuance, rotation, and revocation workflows. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | PQC migration depends on knowing which identities and components are authorised to use each cryptographic asset. |
| Recommendation — Map entitlements to cryptographic assets so migration ownership and approval paths are clear. | ||
| NIST SP 800-57 | Part 1 — Key Management Lifecycle | The article is primarily about key and certificate lifecycle change under post-quantum pressure. |
| Recommendation — Use key management lifecycle controls to govern cryptographic inventory, rotation, and retirement. | ||
Key terms
- Crypto Inventory: A crypto inventory is the authoritative list of where cryptographic assets are used, who owns them, and what they protect. For PQC migration, it must include certificates, keys, embedded devices, service identities, and signing dependencies so organisations can sequence change and measure exposure.
- Algorithm Agility: Algorithm agility is the practical ability to move from one cryptographic algorithm to another without breaking existing identity and trust relationships. It depends on tooling, policy, and renewal automation that can accept new algorithms while preserving service continuity.
- 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.
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 8, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org