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.

Expanded Definition

Trust Now, Forge Later describes a long-horizon impersonation risk rather than an immediate exploit. An adversary may capture or preserve trust-related material today, then attempt to recreate certificates, roots of trust, or other cryptographically derived identity material once quantum capabilities mature. The concern is not stolen data alone, but the ability to counterfeit trust relationships and re-enter an environment as though the original identity were still valid.

In security terms, this concept sits at the intersection of cryptographic agility, identity assurance, and certificate lifecycle planning. It is closely related to quantum-risk discussions in NIST Cybersecurity Framework 2.0, but it is not a formal control term in most standards. Usage in the industry is still evolving, and organisations often apply it to migration planning for public key infrastructure, device identity, and machine trust chains. The strongest interpretation is preventive: if a trust anchor can be forged later, then its current exposure already matters.

The most common misapplication is treating it as a generic encryption concern, which occurs when teams focus only on data confidentiality and miss the future compromise of identity trust material.

Examples and Use Cases

Implementing defences against Trust Now, Forge Later often introduces migration and operational overhead, requiring organisations to weigh cryptographic resilience against compatibility with legacy systems.

• Inventorying certificates, root authorities, and signing keys that could become forgeable if quantum-safe algorithms are delayed, guided by the broader governance approach in NIST Cybersecurity Framework 2.0.
• Planning post-quantum migration for device identity in environments where certificates are used to authenticate servers, endpoints, or NHI workloads.
• Reviewing whether archived signing material, key backups, or escrow processes could later be abused to counterfeit trust relationships.
• Assessing long-lived systems such as industrial, government, or healthcare platforms where certificate rotation is slow and trust chains persist for years.
• Prioritising cryptographic agility so that future algorithm changes do not force a rushed rebuild of identity and trust infrastructure.

These use cases are less about hypothetical quantum attacks in isolation and more about reducing the value of any material that could later be used to impersonate a legitimate system or identity.

Why It Matters for Security Teams

Security teams need to understand Trust Now, Forge Later because the damage arrives in a different time window than the collection event. A compromise today may look harmless if the attacker cannot immediately break the cryptography, yet the same material may become decisive once quantum-safe assumptions no longer hold. That makes the term especially relevant for identity governance, certificate authority planning, and the protection of machine-to-machine trust.

This is particularly important for NHI environments, where service accounts, workload identities, and automated certificate-based authentication often persist far longer than human credentials. If trust material is not classified by lifespan and forgery impact, organisations can overprotect short-lived secrets while leaving long-lived roots, signing keys, and backup archives exposed to future misuse. Guidance from NIST Cybersecurity Framework 2.0 is useful here because it frames resilience as an ongoing governance problem rather than a one-time technical fix.

Organisations typically encounter the business impact only after migration deadlines, audit findings, or a trust-chain incident expose how much identity infrastructure still depends on non-quantum-safe assumptions, at which point the term becomes operationally unavoidable to address.

Related resources from NHI Mgmt Group

• Why does harvest-now, decrypt-later matter for NHI governance?
• Why does harvest-now, decrypt-later matter for IAM and NHI programmes?
• How do IAM teams prepare for harvest-now, decrypt-later risk?
• Why does digital trust now matter across IAM and NHI programmes?