TL;DR: Quantum computing will eventually weaken much of today’s public-key cryptography, while AES-256 remains robust, according to Yoti’s analysis. The practical issue is not only algorithm choice but cryptographic agility across identity, TLS, and long-lived personal data, where harvest-now-decrypt-later risks are already shaping transition plans.
At a glance
What this is: NHI Mgmt Group's analysis, drawing on Yoti's blog post: Post-quantum cryptography changes identity and data security planning because asymmetric schemes will be weakened first, while symmetric protection such as AES-256 remains resilient for now.
Why it matters: Identity, biometrics and sensitive data programmes need cryptographic agility now because long-lived records, TLS traffic and signing dependencies can outlast current algorithms.
Context
Post-quantum cryptography is the shift from today’s public-key algorithms to new methods designed to resist quantum attacks. The governance gap is that many identity and data flows still assume current asymmetric cryptography will remain dependable for the lifetime of the data, which is not a safe assumption for biometrics, identity records or long-retention personal data.
The article’s practical concern is not abstract quantum theory but dependency management across encryption, signing and transport layers. For identity and verification programmes, that means the crypto boundary can become a lifecycle risk: data captured now may still be valuable when quantum capability matures, so transition planning has to start before the break point arrives.
Key questions
Q: How should security teams prepare identity systems for post-quantum cryptography?
A: They should start with a complete inventory of where cryptography underpins authentication, federation, signing, and encrypted transport. Then they should rank systems by business lifetime and migration complexity, because the most dangerous dependencies are the ones that must remain trusted for years. Crypto-agility matters when replacement can happen without re-architecting the whole identity stack.
Q: Why is harvest-now-decrypt-later such a concern for identity data?
A: Because intercepted ciphertext can remain valuable long after it is captured if the data has a long shelf life. Identity records, biometric templates and signed transactions may still be sensitive years later, which means today’s encryption choice determines tomorrow’s exposure. That is why retention policy and cryptographic planning now need to be managed together.
Q: What happens when one partner is not ready for post-quantum cryptography?
A: The whole trust chain can stay exposed if a dependency, library or relying party continues to rely on vulnerable algorithms. Cryptography sits at the boundary between systems, so the slowest participant can define the real security level. Practitioners should treat external readiness as part of their own assurance model, not as a separate problem.
Q: How do teams decide whether to move to post-quantum signatures or wait?
A: Do not wait for a perfect ecosystem, because the main risk is deferred exposure of data that is already being collected. Teams should migrate the most sensitive and longest-lived identity assets first, while using hybrid approaches where they reduce immediate risk. The decision is about prioritising future impact, not proving theoretical readiness.
Technical breakdown
Why asymmetric cryptography is exposed first
Asymmetric cryptography uses a public key and private key pair to support encryption, signing and key exchange. Its security depends on mathematical problems such as factoring or discrete logarithms, which are hard for classical computers but become far more tractable for sufficiently powerful quantum machines. RSA and elliptic-curve schemes are therefore the first major concern. Symmetric cryptography works differently because the same key encrypts and decrypts data, so quantum speed-ups reduce, but do not collapse, its effective strength. That is why AES-256 remains a much stronger near-term foundation than legacy public-key methods.
Practical implication: Prioritise asymmetric dependencies first, because those are the earliest quantum failure points in identity and transport controls.
What post-quantum cryptography changes in identity architecture
Post-quantum cryptography is not one control but a set of replacement algorithms and migration patterns. The article points to NIST-standardised ML-KEM, ML-DSA and SLH-DSA, which are meant to preserve confidentiality and trust when quantum-capable adversaries emerge. In practice, identity systems must inventory where keys, certificates, TLS endpoints and signing workflows depend on classical algorithms. The hard part is not selecting a stronger algorithm in isolation. It is ensuring every dependency that validates identity, secures sessions, or signs trusted artifacts can move together without breaking the service chain.
Practical implication: Inventory identity, TLS and signing dependencies now so algorithm migration can happen without hidden service outages.
Why harvest-now-decrypt-later is the near-term risk
Harvest-now-decrypt-later means attackers collect encrypted traffic today and store it until quantum decryption becomes feasible. That threat matters most where the data has a long shelf life, such as identity evidence, biometric templates, regulated records and signed transactions. The risk is not limited to stored data, because intercepted session traffic can also reveal information later if the protection layer is still based on vulnerable public-key methods. This creates a timing mismatch: the breach event occurs now, but the disclosure event may happen years later when the ciphertext is no longer safe.
Practical implication: Treat long-retention identity data as future-exposure material and protect it with migration paths that remove quantum-future decryptability.
Threat narrative
Attacker objective: The attacker’s objective is to turn today’s encrypted identity and transport data into future readable material once quantum capability matures.
- Entry occurs when attackers intercept encrypted traffic or store identity-related ciphertext for later analysis.
- Credential or session protection becomes vulnerable once legacy public-key schemes are no longer sufficient against quantum-capable decryption.
- Impact arrives when previously captured identity, biometric or transport data can be decrypted and reused long after collection.
Breaches seen in the wild
- Zacks breach claim 2025: A hacker leaked 12 million Zacks accounts in 2025, claiming domain admin access in 2024; HIBP verified the data, Zacks has not confirmed.
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 agility is now an identity governance requirement, not a future engineering preference. Identity and verification systems hold data whose value can outlast current algorithms, which means crypto decisions have lifecycle consequences. The governance failure is assuming today’s public-key choices can safely protect tomorrow’s records. Practitioners should treat algorithm transition planning as part of data and identity control ownership, not as an isolated infrastructure upgrade.
Harvest-now-decrypt-later turns long-retention identity data into deferred exposure. A biometric template, identity assertion or signed transaction intercepted today can remain exploitable when quantum capability becomes practical. That shifts the security question from whether current controls work to whether they still work at the point of future decryption. The practical conclusion is that data retention policy and cryptographic choice are now linked.
PQC boundary drift: the real risk is not only broken algorithms, but inconsistent readiness across TLS, signing and dependency ecosystems. If one partner, library or hardware component lags behind, the whole trust chain remains exposed. For identity programmes, that means the weakest crypto dependency sets the effective security horizon for the entire service.
Hybrid transition patterns are a sensible bridge, but they do not remove the need for inventory and coordination. Standards bodies are aligning on post-quantum migration, but the article correctly shows that no single organisation can complete the shift alone. Identity teams should assume transition work will be asynchronous across customers, regulators, libraries and infrastructure providers, which makes governance over dependencies the decisive capability.
Long-lived identity data changes the quantum risk calculus for regulated organisations. The same ciphertext can be low risk for one dataset and highly material for another if retention and sensitivity differ. That makes post-quantum planning a prioritisation exercise, not a blanket crypto refresh. The practitioner conclusion is to rank identity assets by shelf life and future consequence, then migrate accordingly.
What this signals
PQC transition planning is now part of identity risk management. Teams that handle biometric, identity and regulated personal data should assume that retention length directly affects cryptographic exposure. The strongest programmes will maintain a dependency inventory that links each trust path to a migration owner and a retirement date.
Quantum readiness will be won or lost at the integration boundary. Even if core systems are modernised, weak partner links, libraries or certificate workflows can preserve legacy exposure. For identity leaders, that makes supplier coordination and crypto inventory as important as algorithm selection.
Post-quantum migration should be sequenced by consequence, not by convenience. Protect the longest-lived identity records and the externally visible TLS and signing paths first, because those are the assets most likely to survive into the quantum era.
For practitioners
- Map cryptographic dependencies across identity flows Build a complete inventory of where RSA, elliptic-curve and TLS-based protections appear in identity, signing and data transfer paths, including third-party dependencies.
- Prioritise long-retention identity data for migration Rank biometric records, identity evidence, regulated personal data and signed artifacts by shelf life, then move the highest-value assets first.
- Consolidate signing into fewer control points Reduce the number of signing services and certificate paths so the eventual switch to post-quantum signatures can be executed consistently.
- Test hybrid key exchange on exposed endpoints Validate post-quantum hybrid key exchange on internet-facing TLS endpoints and confirm partner systems can still negotiate sessions without fallback risk.
Key takeaways
- Post-quantum risk is now a governance problem for identity and data holders because legacy public-key cryptography will not age gracefully across long retention periods.
- The most credible near-term threat is harvest-now-decrypt-later, where encrypted identity data is captured now and exposed later when quantum capability matures.
- Practitioners should inventory asymmetric dependencies, prioritise long-lived identity assets and coordinate migration across partners before the trust chain becomes the weak point.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | SC-13 — Cryptographic Protection | The article centres on protecting identity data as cryptography ages into quantum risk. |
| SC-12 — Cryptographic Key Establishment and Management | Migration planning depends on managing key establishment and replacement across systems. | |
| Recommendation — Use SC-13 to govern where classical cryptography still protects identity and transport data. Apply SC-12 to track cryptographic transitions and replacement dependencies across the trust chain. | ||
| NIST CSF 2.0 | PR.DS-02 — Data-in-Transit is Protected | The article discusses TLS traffic protection and future exposure of intercepted data. |
| ID.AM-01 — Physical Devices and Systems Inventoried | A cryptographic inventory is central to planning post-quantum transition. | |
| GV.RM-01 — Risk Management Strategy Established and Managed | The article frames PQC as a long-horizon governance and prioritisation issue. | |
| Recommendation — Map transport protection to PR.DS-02 and verify which sessions still rely on vulnerable algorithms. Extend inventory discipline to cryptographic dependencies so migration scope is visible. Embed post-quantum migration into the organisation’s risk strategy and prioritisation model. | ||
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.
- 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.
- Hybrid Key Exchange: A transitional cryptographic setup that supports both classical and post-quantum key exchange during session negotiation. It reduces compatibility risk while improving resilience, but it is not a final endpoint because the surrounding certificate and identity estate may still rely on quantum-vulnerable components.
Deepen your knowledge
NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, identity lifecycle and secrets management. It helps practitioners connect identity control decisions to the wider security programme they are responsible for.
Published by the NHIMG editorial team on August 1, 2026.
Updated on October 13, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org