Topic starter
09/06/2026 11:11 pm
TL;DR: C1.ai argues that identity stacks built for human workflows are failing as AI agents call tools, chain tasks, spawn other agents, and outnumber human identities by more than 80 to 1, while 90% of organisations reported at least one identity-related incident. The governance gap is not login friction but agency control, where lifecycle, scope, attribution, and revocation all need to be rethought for autonomous execution.
Editorial analysis by NHI Mgmt Group, based on content published by C1.ai: “The Identity Stack Was Built for Humans. Agents Don't Care.”.
Key questions
Q: How should security teams govern AI agents that can invoke multiple tools in one session?
A: Security teams should govern AI agents as decision-making identities, not just tool users.
Q: Why do static access reviews fail for AI agent identities?
A: Static access reviews fail because they assume access remains stable long enough to be observed and certified.
Q: What breaks when an AI agent spawns another agent to finish a task?
A: What breaks is attribution and scope containment.
Practitioner guidance
- Instrument agent delegation chains Capture which tools each agent calls, which credentials it uses, who originated the chain, and when control passes from one agent to another.
- Redesign lifecycle governance for ephemeral identities Move from calendar-based recertification to issuance-time controls that can govern identities that create and destroy themselves within a single task.
- Separate agency scope from human role scope Define task-bounded, time-bounded, and blast-radius-bounded access for agents instead of inheriting coarse human roles.
Bottom line: The article argues that human-built IAM assumptions fail when agents can call tools, chain tasks, and delegate work without a person clicking through each step.
What's in the full article
C1.ai's full blog covers the operational detail this post intentionally leaves for the source:
- The article's four failure modes laid out as a practitioner checklist for identity, scope, attribution, and revocation.
- The agency model the author proposes for governing agents as identities that act on behalf of humans.
- The visibility-first approach recommended for instrumenting tool calls, credential use, and chain origin.
- The author's view of how a unified identity graph should represent humans and agents together.
👉 Read C1.ai's analysis of AI agent identity governance and the human-built stack →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 3 days ago by NHI Mgmt Group
10/06/2026 1:26 am
Human IAM assumes a person is in the loop, and that assumption is now failing. The article is right to frame the shift as a change in actor behaviour, not just a new tool category. Human identity stacks were tuned for clicks, prompts, and review cycles, while agents call tools and spawn follow-on work without waiting for a manager or a ticket queue. That means the governance model itself is out of sync with the runtime reality. Practitioners should treat this as a control-plane mismatch, not a usability problem.
A few things that frame the scale:
- 90% of organizations experienced at least one identity-related incident in the past year, according to the Ultimate Guide to NHIs.
- Our research also shows that only 5.7% of organizations have full visibility into their service accounts, which is a warning sign for any programme extending governance to AI agents.
A question worth separating out:
Q: What is the difference between agent identity and agency?
A: Agent identity tells you what the system is. Agency tells you what it can do, on whose behalf, with what scope, and for how long. Identity alone is not enough for AI systems that select tools and execute actions at runtime. Practitioners need to govern delegated action, not just authentication state.
👉 Read our full editorial: AI agent identity governance is breaking the human-built stack
11/06/2026 12:31 am
Human IAM assumes a person is in the loop, and that assumption is now failing. The article is right to frame the shift as a change in actor behaviour, not just a new tool category. Human identity stacks were tuned for clicks, prompts, and review cycles, while agents call tools and spawn follow-on work without waiting for a manager or a ticket queue. That means the governance model itself is out of sync with the runtime reality. Practitioners should treat this as a control-plane mismatch, not a usability problem.
A few things that frame the scale:
- 90% of organizations experienced at least one identity-related incident in the past year, according to the Ultimate Guide to NHIs.
- Our research also shows that only 5.7% of organizations have full visibility into their service accounts, which is a warning sign for any programme extending governance to AI agents.
A question worth separating out:
Q: What is the difference between agent identity and agency?
A: Agent identity tells you what the system is. Agency tells you what it can do, on whose behalf, with what scope, and for how long. Identity alone is not enough for AI systems that select tools and execute actions at runtime. Practitioners need to govern delegated action, not just authentication state.
👉 Read our full editorial: AI agent identity governance is breaking the human-built stack
12/06/2026 2:03 am
AI agent governance exposes an assumption collapse in human-first identity design: access review processes were designed for identities that persist long enough to be observed, certified, and removed later. That assumption fails when an agent acquires, uses, and discards access inside a single task chain. The implication is not simply to add more reviews, but to recognise that review-based governance no longer maps cleanly to agentic execution.
A question worth separating out:
A: They need a model where agents can investigate and propose actions, but humans still own the judgment calls and the verification standards. The practical guardrail is a system that shows what the agent did, what remains pending approval, and whether the action actually worked. That preserves accountability while reducing manual toil.
👉 Read our full editorial: AI agent identity governance is breaking the human-built stack
This post was modified 3 days ago by NHI Mgmt Group