Post-quantum agentic vaulting pushes credential governance closer to identity

At a glance

What this is: This is a product announcement about an agentic secrets vault that applies identity policy, just-in-time access, and auditability to credentials used by humans, agents, and service accounts.

Why it matters: It matters because IAM and NHI teams need to govern credentials as runtime identity power, especially where AI agents and machine workloads can consume secrets faster than legacy vault processes can control them.

By the numbers:

• 28.65 million new secrets leaked on public GitHub in 2025, up 34% year over year, with leaked AI-service credentials up 81%.
• Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
• 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.

👉 Read ConductorOne's post on post-quantum agentic vault governance for credentials

Context

Credential governance has become a core identity security issue because secrets now power people, workloads, bots, and AI agents. When credentials are treated as static artifacts instead of runtime identity assets, organisations create exposure windows that traditional vault models were never designed to manage.

The primary governance gap is not storage alone. It is the mismatch between legacy checkout workflows and modern machine-speed consumption, where policy needs to follow the secret at request time and maintain traceability across identity, privilege, and rotation.

For IAM, PAM, and NHI programmes, the important question is no longer whether a vault exists. It is whether the vault can enforce least privilege, time-bound use, revocation, and auditability across all actor types without creating parallel governance paths.

Key questions

Q: How should security teams handle exposed secrets in AI-driven environments?

A: Security teams should treat exposed secrets as active access paths and respond as though misuse can begin immediately. The right sequence is to identify the owning NHI, revoke the credential everywhere it is trusted, check downstream dependencies, and then validate whether the secret was copied into collaboration or CI systems.

Q: Why do traditional vaults struggle with AI-driven workloads?

A: Traditional vaults assume infrequent human checkout and manual oversight. AI-driven workloads can request credentials repeatedly and at machine speed, which makes approval loops, broad vault access, and per-secret sprawl hard to sustain. The result is either excessive privilege or operational bottlenecks, both of which undermine identity governance.

Q: What is the biggest risk of storing credentials without strong lifecycle controls?

A: The biggest risk is that the secret outlives the access need. When offboarding, revocation, and rotation are weak, credentials remain valid after the actor, project, or vendor relationship has changed. That creates a standing exposure window that attackers can exploit long after the original business purpose has ended.

Q: How do post-quantum concerns change secrets management decisions?

A: They extend the useful life of stolen credentials far beyond the moment of theft. If an attacker can harvest a secret now and decrypt it later, organisations need to prioritise the lifetime and sensitivity of stored credentials, not just whether they are currently protected. That pushes high-value secrets toward stronger cryptography and shorter validity periods.

How it works in practice

Why legacy secrets vaults break at agent scale

Traditional vaults were built around a human user retrieving a credential occasionally, then returning to a browser or terminal. Agentic environments change the access pattern entirely: secrets may be requested repeatedly, at machine speed, by systems that do not wait for a person to approve each use. That makes manual approval flows, periodic checkout models, and per-credential vault sprawl operationally brittle. If the vault cannot bind access to identity policy at request time, it becomes a storage layer instead of a governance control.

Practical implication: Treat vault design as an access-control problem, not only a storage problem.

How policy-governed credential access changes the control model

Policy-governed access means the right to reveal a secret is evaluated at the moment of use, against identity, context, and policy. That matters because the secret itself is the power to act, whether the actor is a person, a service account, or an AI agent. In practical terms, the vault becomes an enforcement point for just-in-time access, least privilege, and audit logging, rather than a passive repository. The architectural shift is from static possession to conditional revelation.

Practical implication: Make secret disclosure conditional on policy, not on prior possession.

Why post-quantum protection matters for credentials

Post-quantum vaulting addresses a long-tail risk: credentials encrypted today may be harvested now and decrypted later when quantum systems are sufficiently capable. That means the threat is not only immediate compromise but also delayed exploitation of long-lived secrets. A vault that uses zero-knowledge design and quantum-resistant cryptographic choices reduces the value of stored secrets both now and in future decryption scenarios. For identity teams, this reinforces that credential lifespan and cryptographic durability are linked governance concerns.

Practical implication: Prioritise high-value secrets whose exposure would still matter years from now.

NHI Mgmt Group analysis

Credential governance is now the control plane for agentic environments. When secrets power users, workloads, and AI systems alike, the old distinction between secret storage and access governance stops holding. A vault that does not evaluate identity, context, and privilege at request time is not governing the credential lifecycle. Practitioners should treat every secret as an executable permission boundary.

Legacy vault assumptions were designed for human-paced checkout, not machine-paced consumption. Human operators can tolerate approval loops, manual rotation, and intermittent use. AI agents and service workloads can exhaust those assumptions in minutes, which means the model of static possession followed by periodic review no longer describes how access actually behaves. The implication is that IAM and PAM teams must rethink whether their current governance cadence matches runtime reality.

Post-quantum credential protection should be evaluated as a data-retention issue as much as a cryptography issue. If a credential remains valid long enough to matter later, then harvested secrets become future liabilities even when they are not immediately abused. That changes how teams assess vault design, because cryptographic durability and secret lifetime now sit in the same risk conversation. Practitioners should stop treating quantum resilience as a distant niche topic.

Decoy credentials and full audit trails are useful only when they are tied to identity context. An alert that fires on secret use is most valuable when the organisation can immediately tell which actor, policy path, and workload context were involved. Otherwise the signal becomes noise and the response window stretches. The practical lesson is that detection, governance, and attribution need to operate together, not separately.

Named concept: credential blast-radius control. The real problem is not only whether a secret is stored securely, but how far that secret can carry an identity when it is used. As AI adoption expands the number of identities that can consume credentials, the blast radius of any single secret grows unless access is tightly scoped and time bound. Practitioners should judge vault architecture by how much identity reach each secret creates.

From our research:

• 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures, according to Ultimate Guide to NHIs.
• 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage.
• For a broader lifecycle view, the Ultimate Guide to NHIs also shows that only 20% have formal processes for offboarding and revoking API keys.

What this signals

With 91.6% of secrets still valid five days after notification, the operational problem is not discovery but revocation latency. That leaves modern identity programmes exposed to a window where AI agents, service accounts, and human-held credentials can still be abused even after the risk is known, which is why lifecycle control now matters as much as vault design.

Credential blast-radius control: identity teams should measure how far a single secret can reach across users, workloads, and agentic systems. If a credential can unlock multiple systems or survive owner changes, the programme is carrying hidden privilege debt that normal access review cycles will not surface.

For teams mapping this to standards, the practical lens is Zero Trust and identity lifecycle governance, not vaulting alone. The question is whether the organisation can prove that secret use is least-privileged, time bound, and attributable, with NHI lifecycle controls supporting revocation and audit at the speed modern systems now demand.

For practitioners

• Map every secret to a specific identity and use case Inventory API keys, tokens, passwords, certificates, and signing secrets by the identity that can consume them, the workload they unlock, and the policy that should govern disclosure. This exposes overbroad credentials and makes it easier to align rotation and revocation with actual business ownership.
• Enforce request-time policy checks for secret revelation Require the vault to evaluate identity, context, and approval state before a secret is disclosed. This closes the gap between possession and use, especially for service accounts and AI agents that can request access far faster than a human review cycle can react.
• Separate long-lived secrets from short-lived operational access Reserve durable credentials for cases that truly require them and move routine access to just-in-time patterns wherever possible. The goal is to reduce the number of secrets that can be harvested now and abused later, including in post-quantum scenarios.
• Instrument secret use with identity-context logging Log who or what requested the secret, which policy allowed it, when it was used, and what system consumed it. Tie that telemetry into detection workflows so unusual secret use can be correlated with the workload or agent that triggered it.

Key takeaways

• Secrets are no longer passive storage objects. In agentic environments, they function as runtime permissions that must be governed at the moment of use.
• Exposure and revocation lag remain the main risk multipliers, with leaked credentials often staying valid long enough to be abused after defenders are notified.
• Identity teams should measure vaults by blast radius, policy enforcement, and revocation speed, not by how many secrets they can store.

Key terms

• Credential Blast Radius: Credential blast radius is the amount of access, data, and system reach that a single compromised secret can unlock. The wider the blast radius, the more damage one leaked token or certificate can cause. Reducing it requires tighter scope, faster revocation, and better segmentation.
• Request-Time Policy Check: An access decision made at the moment a secret is requested, rather than when it is stored or provisioned. For workloads and AI agents, this is a key control because it ties disclosure to identity, context, and policy instead of static possession.
• 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.

What's in the full announcement

ConductorOne's full product post covers the operational detail this post intentionally leaves for the source:

• How Agentic Vault handles request-time policy checks for humans, agents, and service accounts
• The full audit-trail model down to the individual secret, including read and rotation events
• The vendor's description of end-to-end rotation flow, including provisioning, cycling, and destruction
• How decoy credentials are intended to trigger alerts on use

👉 ConductorOne's full post covers the credential policy model, audit trail details, and decoy secret behaviour.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity security are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing identity security across humans, workloads, and AI-driven systems, it is worth exploring.