TL;DR: Quantum computing is compressing the timeline for breaking today’s cryptography, with Google moving its internal post-quantum migration target to 2029 and NIST already finalizing the first post-quantum standards, according to Keyfactor and NIST. The shift turns cryptography inventory, crypto-agility, and trust lifecycle governance into core IAM and NHI priorities, not specialist infrastructure work.
Editorial analysis by NHI Mgmt Group, based on content published by Keyfactor: “World Quantum Day: What We’re Not Talking About Enough”.
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.
Q: Why does post-quantum risk matter for NHI and workload identity?
A: Because service accounts, certificates, and signed machine-to-machine assertions all depend on cryptographic trust.
Q: What breaks when cryptography is hard-coded into identity platforms?
A: Hard-coded cryptography breaks migration because the organisation cannot replace algorithms, keys, or signing methods without redesigning applications and trust flows.
Practitioner guidance
- Inventory cryptographic dependencies across identity flows Build a full register of where RSA, elliptic-curve, certificate chains, signed updates, and federated trust are embedded in human and machine identity workflows.
- Prioritise long-lived trust material first Rank systems by data retention, certificate lifetime, and authentication criticality so the longest-lived trust dependencies move earliest to post-quantum planning.
- Test algorithm replacement in controlled environments Validate whether applications, PKI services, and workload authentication paths can swap algorithms without breaking interoperability or revocation handling.
Bottom line: Post-quantum cryptography moves identity teams from static trust assumptions to active governance of certificates, signatures, and machine authentication.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Post-quantum cryptography is an identity governance problem before it is a cryptography problem. The article is right to frame PQC as trust infrastructure, because identity systems depend on certificates, signatures, and authenticated channels that must be governed over time. What matters for practitioners is not only which algorithms are approved, but whether the organisation can inventory, approve, migrate, and retire them as part of normal identity lifecycle governance.
A question worth separating out:
Q: How do teams know whether crypto-agility is actually working?
A: Crypto-agility is working when algorithms can be changed without major re-engineering and the inventory shows which systems will be affected before the change is made. Signs of failure include unknown embedded libraries, orphaned certificates, and long manual remediation cycles. If the estate cannot absorb algorithm change predictably, the architecture is not agile enough.
👉 Read our full editorial: Post-quantum cryptography is becoming an identity governance problem