TL;DR: AI agents need separate identities and named policies because shared credentials erase attribution and make revocation imprecise, according to KeyRunner. Authorization has to stay tied to the runtime decision, or security teams lose sight of who acted, why it was allowed, and what changed.
Editorial analysis by NHI Mgmt Group, based on content published by KeyRunner: “How Should Enterprises Identify and Authorize AI Agents?”.
Key questions
Q: Why is authentication alone not enough for agentic AI access control?
A: Authentication answers whether the agent can prove its identity, but agentic AI can still take actions that exceed the original intent of that identity.
Q: What breaks when an AI agent shares one credential across tools and model calls?
A: The boundary between inference and action breaks down.
Q: How should organizations approach the governance of AI agents?
A: Organizations should adopt a governance framework that incorporates continuous visibility, adaptive IAM practices, and stringent policy-based controls.
Practitioner guidance
- Define a unique identity for each agent Register every agent as a separate principal with its own owner, purpose, lifecycle state, and access scope so revocation does not depend on a shared account.
- Preserve the initiating identity Carry the verified human or workload that requested the action through the full execution chain so audit, approval, and accountability stay tied to the original requester.
- Enforce policy before execution Check the agent, initiator, tool, parameters, target, environment, time, and approval state before any downstream API call is allowed.
Bottom line: AI agents need separate identities and named policies because shared credentials erase attribution and make revocation imprecise.
Glossary terms: AI Agent Identity, Runtime Authorisation, Attribution Chain, Tool-Set Authority Leakage
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Unique agent identity is the governance primitive that makes delegation legible. If one agent can stand in for many users, tasks, or workloads, then identity becomes ambiguous and accountability degrades with every shared credential. The article correctly separates the agent from the initiator, which is the only way to preserve ownership, scope, and revocation as distinct governance events. The practitioner takeaway is to treat each agent as an independently managed principal, not as a convenience wrapper around human access.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should enterprises use the same identity for an AI agent and its human user?
A: No. The agent and the user should remain distinct identities linked in the same execution context. That separation preserves who initiated the task while allowing the agent to carry narrower permissions, independent policy, and a lifecycle that can be revoked without changing the human account.
👉 Read our full editorial: Unique identities and external policy close the AI agent gap