Agentic vaulting for AI agents: are secrets still governed like identities?

TL;DR: Secrets management is becoming an identity governance problem as agentic systems authenticate on their own, request scoped credentials, and expand exposure through loose vaulting, according to ConductorOne and GitGuardian research. The real shift is that credential lifecycle, approval, and audit now have to work at machine speed, or least privilege becomes a paper control.

NHIMG editorial — what this means for AI and NHI governance

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 5.7% of organisations have full visibility into their service accounts.
• 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.

Questions worth separating out

Q: What breaks when AI agent access relies on long-lived secrets?

A: Long-lived secrets let AI agents carry persistent access far beyond the task they were created for.

Q: Why do machine identities make secrets management harder than human access management?

A: Machine identities scale faster, change more often, and are frequently owned by applications rather than people.

Q: How do identity teams know whether secrets governance is actually working?

A: Identity teams know secrets governance is working when they can prove that every active secret has an owner, an approved scope, and a tested revocation path.

Practitioner guidance

• Separate secret custody from secret use Move exposed credentials into governed custody, then issue agents short-lived scoped credentials instead of passing raw keys into tools, pipelines, or prompts.
• Map every secret to an owning identity Tie each API key, token, certificate, and password to a named human, service account, workload, or agent so approval and revocation are not orphaned.
• Use decoys on exposed secret surfaces Plant decoy credentials in .env files, CI variables, and secrets stores that should never be used, then alert on any authentication attempt.

What's in the full announcement

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

• How Agentic Vault handles vault-and-replace for exposed secrets found in shadow AI discovery
• How workload federation is used to exchange signed workload identity for short-lived credentials
• How decoy credentials are fingerprinted and monitored for misuse across common secret storage surfaces
• How post-quantum hybrid key establishment is applied inside the vault rather than only at the transport layer

👉 Read ConductorOne's analysis of Agentic Vault and secret governance for AI agents →

Agentic vaulting for AI agents: are secrets still governed like identities?

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →