Q-day risk is accelerating, making PQC visibility the priority

At a glance

What this is: NHI Mgmt Group's analysis, drawing on Forescout's blog post: Accelerating quantum risk makes post-quantum cryptography migration depend on cryptographic visibility, asset inventory, and prioritisation rather than speed alone.

Why it matters: IAM and NHI teams need to understand how PQC migration affects trust anchors, certificates, signing, and long-lived credentials across human and machine identity systems.

By the numbers:

• Forescout says previous timelines predicting Q-day’s arrival in 2031 are now further compressed.
• The White House issued two landmark Executive Orders on June 22nd to accelerate the United States’ transition to post-quantum cryptography.
• Forescout says federal agencies are being directed to migrate high-value assets and high-impact systems toward quantum resilience by 2031.
• Forescout cites 90% of systems as unsafe in its PQC adoption data.

Context

Post-quantum cryptography is the shift from today’s public-key assumptions to algorithms designed to resist future quantum attacks. The hard problem is not only cryptographic replacement, but knowing where certificates, signing, tokens, and trust anchors exist across complex environments before they become the weak point.

That visibility challenge matters because quantum migration is not just a cryptography exercise. It touches identity assurance, machine trust, and the lifecycle of digital credentials, which means teams have to treat PKI inventory and workload trust paths as governance problems, not just engineering tasks.

Key questions

Q: How should teams prioritise data for post-quantum cryptography migration?

A: Prioritise data by confidentiality lifetime, replaceability, and exposure spread. The most urgent datasets are those that remain harmful if disclosed for years, cannot be reissued easily, and already exist in multiple copies across backups, analytics, email, and cloud services. That gives you a practical queue for migration and compensating controls.

Q: Why does quantum risk affect identity and trust systems as much as encrypted data?

A: Because quantum compromise is not only about reading old ciphertext. It can also undermine certificate authorities, code signing, and federation trust, which means attackers may be able to impersonate trusted entities or forge legitimate-looking signatures. Identity teams need to treat trust anchors as security assets with lifecycle risk, not just as background infrastructure.

Q: What breaks when organisations try to replace cryptographic algorithms without mapping dependencies first?

A: The migration often breaks at the operational layer. Applications may need vendor support, new libraries, hardware changes, or code updates. Dependencies can cascade across connected systems, so a seemingly simple change can trigger downtime, failed integrations, or stalled programmes. The cryptographic swap is usually easier than managing everything the swap affects.

Q: Should teams treat PQC as a one-time upgrade or a continuing governance programme?

A: They should treat it as a continuing governance programme. Standards, vendor support, and adversary capability will keep changing, so the control objective is ongoing cryptographic agility, not a single migration milestone. Organisations that lock in one architecture too early risk creating new constraints that are expensive to unwind later.

Technical breakdown

Why harvest now, decrypt later changes the risk model

Harvest now, decrypt later is the strategy of stealing encrypted data today and storing it until future quantum capability makes decryption feasible. The risk is highest for data with a long shelf life, such as personal information, classified records, financial data, private communications, and intellectual property. This is not a live break of confidentiality today, but a deferred compromise of data that organisations assumed was safely protected by current encryption. Practical implication: classify data by retention value, not just sensitivity, when prioritising PQC migration. See the Post-Quantum Cryptography Migration Guide.

Practical implication: Prioritise long-lived data and the systems that protect it before short-lived records that age out of risk.

How trust now, forge later attacks target identity and trust systems

Trust now, forge later is the more subtle quantum threat because it targets the mechanisms that prove authenticity rather than the payload itself. Certificate authorities, code signing chains, PKI roots, and other trust anchors can be attacked so that signatures, identities, or software provenance appear valid when they are not. In identity terms, this weakens the assurance layer that lets systems decide who or what can be trusted. If those trust anchors fail, a forged identity can move through systems as if it were legitimate. Practical implication: map every trust dependency, not just every encrypted data store, before migration planning begins. See the Machine Identity, PKI and Certificate Lifecycle Guide.

Practical implication: Inventory certificate, signing, and federation dependencies as identity trust assets, not as isolated technical components.

Why cryptographic inventory drives migration sequencing

PQC migration fails when organisations treat it as a universal upgrade rather than a prioritisation problem. Legacy systems, embedded firmware, industrial control environments, third-party products, and long-life hardware may not support rapid cryptographic change. That creates a visibility gap: if you cannot see where cryptography is used, you cannot rank which assets are most exposed or which dependencies create the largest operational risk. Practical implication: build a cryptographic inventory that links systems, certificates, protocols, and business criticality before choosing migration waves. Read Post-Quantum Readiness for Identity and PKI.

Practical implication: Use asset visibility to sequence migration by business criticality and exposure, not by technical convenience.

Threat narrative

Attacker objective: To preserve stolen encrypted material for future decryption and to undermine trust mechanisms so identities, signatures, or software provenance can be forged later.

1. Entry occurs through passive collection of encrypted communications, archived records, or long-lived protected data that can be stored for future decryption.
2. Credentialed trust is then targeted through certificate authorities, code signing chains, or other roots of trust that make forged identities and signatures appear valid.
3. The impact is delayed compromise, where stolen data becomes readable later and trust systems may be subverted without obvious immediate detection.

NHI Mgmt Group analysis

PQC migration is now an identity governance problem, not just a cryptography project. The article’s core point is that quantum risk touches certificates, signing, and authentication as much as it touches encryption at rest. That means governance has to extend to trust inventory, lifecycle ownership, and dependency mapping across human and machine identity systems. The organisations that treat PQC as an infrastructure refresh will miss the trust layer entirely. Practitioners should manage PQC as a governed identity change programme, not a one-time cryptographic swap.

Trust now, forge later is the more dangerous long-tail risk because it attacks legitimacy itself. If an attacker can compromise certificate authorities or signing chains, the problem is not data confidentiality alone but the ability to impersonate trusted entities and ship forged software or assertions. That makes the integrity of certificate lifecycle controls central to quantum readiness. Practitioners should treat roots of trust as critical assets whose compromise would invalidate downstream authentication decisions.

Cryptographic visibility is the named concept that determines whether PQC becomes manageable or chaotic. Organisations cannot prioritise what they cannot see, and the article is explicit that many environments include legacy systems, embedded hardware, and third-party dependencies that are difficult to inventory. This creates governance debt because migration plans depend on incomplete knowledge of where cryptography is used. Practitioners should demand an inventory that links asset criticality to cryptographic exposure before approving any migration timeline.

Speed is the wrong optimisation target when cryptographic transition spans decades of infrastructure. The article shows that policy urgency, vendor pressure, and technical change will not produce safe migration by force alone. The real differentiator is whether a programme can adapt as standards, procurement expectations, and quantum capability change. That argues for flexible control design, staged migration, and continuous reassessment rather than fixed deadlines treated as the end state. Practitioners should plan for evolving assurance, not just initial compliance.

What this signals

Cryptographic agility is now a governance requirement, not an optional architecture preference. Teams need to assume that algorithms, standards, and procurement expectations will keep changing, which makes one-time migration projects insufficient. The practical lesson is to build changeable trust infrastructure and to anchor decisions in inventory, not vendor roadmaps.

Quantum readiness will expose weak asset visibility long before it exposes weak encryption. The organisations most at risk are often the ones that cannot answer where their certificates, signing chains, embedded devices, and long-life systems are located. That is why the first operational priority is usually discovery, not algorithm selection.

Post-quantum planning should be linked to identity assurance and certificate lifecycle management. The same inventory that supports PQC migration also supports control over roots of trust, federation dependencies, and certificate renewal. Programs that align these disciplines will reduce both future decryption risk and present-day trust compromise.

For practitioners

• Build a cryptographic asset inventory Catalogue certificates, keys, signing systems, tokens, protocol dependencies, and the business services they protect so migration can be prioritised by exposure and criticality. Read Post-Quantum Readiness for Identity and PKI.
• Prioritise long-lived and high-impact data first Rank records and communications by retention value, regulatory exposure, and likely adversary interest so harvest now, decrypt later risk is reduced where it matters most.
• Map roots of trust across identity systems Trace certificate authorities, code signing chains, federation dependencies, and other trust anchors to identify where forged trust would undermine authentication decisions.
• Segment migration by platform readiness Separate modern platforms from legacy and embedded systems, then build phased migration waves that account for hardware refresh cycles and vendor support constraints.

Key takeaways

• Quantum risk now affects both data confidentiality and the trust systems that prove identity and software provenance.
• The hardest part of PQC migration is usually not the algorithm change but discovering where cryptography exists and which assets matter most.
• Organisations that build cryptographic visibility and agility now will be better positioned to absorb future standards and threat changes.

Related NHI Mgmt Group resources: Machine Identity, PKI and Certificate Lifecycle Guide · Post-Quantum Readiness for Identity and PKI · Post-Quantum Cryptography Migration Guide · Cryptography Basics Guide

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.
• Trust Now, Forge Later: A quantum-era impersonation threat in which an attacker may eventually recreate cryptographically derived identity material such as certificates or roots of trust. Unlike data harvesting, this attack aims to counterfeit trust relationships and act inside an environment. It depends on future quantum capability, but it can inform current identity and certificate planning.
• Cryptographic visibility: Cryptographic visibility is the ability to see where keys, certificates, and algorithms exist, who owns them, and which services depend on them. It turns hidden trust dependencies into governed assets. Without it, teams cannot reliably assess exposure, prioritise remediation, or prove control effectiveness across identity and workload systems.

Deepen your knowledge

NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security, workload identity, and secrets management. It helps practitioners connect identity controls to the broader security decisions their programmes depend on.