Topic starter
30/09/2026 4:59 pm
TL;DR: Revocation gaps, not just secret storage, are now the operational failure mode for NHI governance, and credential vending and C1 Egress remove hardcoded secrets from apps and AI agents by issuing short-lived, scoped credentials on demand and injecting them only when policy allows a request, according to C1.ai.
NHIMG editorial: what this means for NHI practitioners
Questions worth separating out
Q: What breaks when apps and agents keep hardcoded secrets?
A: Hardcoded secrets create a spread problem, not just a storage problem.
Q: When does short-lived credential issuance reduce risk most effectively?
A: It reduces risk most when the workload only needs access for a single task, a bounded job, or a narrowly approved destination.
Q: What do security teams get wrong about secret rotation?
A: They often treat rotation as a substitute for removing the underlying credential model.
Practitioner guidance
- Inventory hardcoded secret paths Map where API keys, tokens, and certificates are currently copied into code, configuration, containers, logs, and support workflows so you can remove the highest-spread credentials first.
- Shift workload access to short-lived issuance Replace durable shared secrets with on-demand credentials for apps, agents, contractors, and CI/CD jobs where the access need is task-scoped and time-bounded.
- Enforce outbound destination policy Tie credential use to approved destinations and block internal addresses and cloud metadata endpoints by default so the workload cannot freely route around policy.
What's in the full announcement
C1.ai's full article covers the operational detail this post intentionally leaves for the source:
- How credential vending is wired into workload access workflows for apps and AI agents
- How C1 Egress enforces destination policy and blocks internal and metadata endpoints
- How revocation behaves on the next call rather than after a redeploy
- How the central credential inventory and audit trail are structured for operations
👉 Read C1.ai's article on credential vending and C1 Egress →
Credential vending for apps and agents: are your secrets still in workloads?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
30/09/2026 5:00 pm
Credential custody, not credential possession, is the real control boundary: the article shows why keeping a secret out of the workload matters more than simply storing it somewhere safer. When a credential can be pasted into config, copied into images, or inherited by an agent context window, the governance problem becomes propagation, not just storage. That is the right mental model for NHI programmes that have outgrown manual secret placement.
A question worth separating out:
Q: How should teams govern credentials for AI agents and CI/CD jobs?
A: They should govern them as task-scoped non-human identities, not as permanent application secrets. That means assigning short-lived credentials, limiting destinations, logging issuance and use, and ensuring the identity cannot keep access after the task ends or the pipeline completes.
👉 Read our full editorial: Credential vending changes how apps and agents handle secrets
