Notifications
Clear all
Topic starter
11/08/2026 3:15 pm
TL;DR: The central issue is not visibility alone but whether access, tool use, and remediation can be governed end to end before agent autonomy overwhelms existing IAM patterns, according to C1.ai’s four-part launch tying shadow AI discovery, agentic vaulting, runtime governance, and identity risk remediation into one control plane for AI agents and other non-human identities.
NHIMG editorial — what this means for AI and NHI governance
By the numbers:
- Only 5.7% of organisations have full visibility into their service accounts.
- 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage.
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%).
Questions worth separating out
Q: How should security teams implement AI agent credential management?
A: Security teams should issue short-lived, task-scoped credentials tied to the specific agent, tool, and resource involved, rather than sharing human sessions or static API keys.
Q: Why do AI agents create more governance risk than ordinary integrations?
A: AI agents can connect quickly, run continuously, and accumulate broad permissions across multiple services.
Q: What breaks when discovery does not lead to ownership for AI agents?
A: You get visibility without accountability.
Practitioner guidance
- Map AI agents to governance owners Inventory discovered agents, MCP servers, credentials, and cloud runtimes, then assign each item to a business owner and control owner before granting access.
- Replace persistent secrets with short-lived exchanges Use workload identity-backed credential exchange so agents receive scoped, time-bound access instead of underlying keys.
- Move authorisation to the tool-call boundary Enforce policy at runtime for every agent action that touches private data, untrusted input, or outbound transfer paths.
What's in the full announcement
C1.ai's full blog covers the operational detail this post intentionally leaves for the source:
- Step-by-step discovery coverage for AI tools, MCP servers, and exposed credentials across endpoints and cloud platforms.
- Product-specific examples of scoped credential exchange, proof of possession, and decoy credential handling.
- Runtime policy conditions used to block, hold, or redact agent tool calls when private data or exfiltration paths are present.
- Routing and remediation examples for ServiceNow, Jira, and PagerDuty integrations.
👉 Read C1.ai's roundup of agentic control plane launches →
Agentic control plane for AI agents: are your controls keeping up?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
11/08/2026 3:28 pm
Agentic identity governance is now a control-plane problem, not a point-product problem. The article is describing a model where discovery, secrets, runtime authorisation, and remediation all sit in one operational path. That matters because the failure mode in agentic environments is not a missing checkbox, but a broken handoff between inventory, access, and response. Practitioners should read this as a signal that AI agent governance will increasingly be judged by control continuity, not tool count.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface, according to Ultimate Guide to NHIs.
A question worth separating out:
Q: Who should be accountable when an AI agent causes a security incident?
A: Accountability should sit with the human owner, platform team, or business function that granted and operated the agent. The identity may act independently, but governance cannot detach responsibility from the delegation chain. Programs should define ownership, escalation, and remediation paths before deployment so responsibility is clear when the agent's behaviour changes.
👉 Read our full editorial: C1.ai's agentic control plane links discovery, vault, runtime, and response
