Topic starter
23/06/2026 9:11 pm
TL;DR: AI agents share core identity needs with people, but their ephemeral lifecycles, 80-to-1 scale, and multi-hop delegation chains break static IAM models, according to Strata Identity. Access review processes assume identities persist long enough to be reviewed; agents can appear and disappear within a task.
Editorial analysis by NHI Mgmt Group, based on content published by Strata Identity: “Exploring IAM for AI Agents”.
By the numbers:
- AI agents may outnumber human identities 80 to 1 in some enterprises.
Key questions
Q: How should security teams govern AI agents that browse and transact on behalf of users?
A: Security teams should govern AI agents as delegated actors with narrow, task-scoped permissions, not as enhanced browsers.
Q: Why do static service accounts break down for AI agent workflows?
A: Static service accounts assume a durable principal, stable permissions, and enough lifespan for periodic review.
Q: What are the signs that an agent governance programme is failing?
A: Common signals include unknown agents in staging or production, unvetted MCP connections, broad or long-lived credentials, and logs that show service-account activity without clear ownership.
Practitioner guidance
- Define task-scoped agent identities Issue an identity only for the specific workflow or delegation it will perform, and retire it immediately when that task ends.
- Bind delegation into the token path Use On-Behalf-Of, token exchange, and proof-of-possession controls so every agent action remains tied to the delegator and cannot be replayed outside the intended context.
- Enforce continuous access evaluation Apply runtime policy re-evaluation so agent authority can be revoked when context changes, rather than waiting for a periodic certification cycle.
Bottom line: AI agents expose the limits of static account-based IAM because their authority is often delegated, task-scoped, and short-lived.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 2:20 am
AI agents are first-class identities, not expanded service accounts: The article is right to separate agent identity from static machine accounts because the governance problem is different. Service accounts presume a persistent principal with a fixed owner and a long enough lifespan to be reviewed. AI agents can be instantiated per task, delegated on the fly, and destroyed before any periodic governance cycle sees them, so identity management must move to runtime issuance and retirement.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
- 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.
A question worth separating out:
Q: What is the difference between governing AI agents as users and governing them as workloads?
A: Governing AI agents as users assumes stable human-like access patterns, which breaks down when the agent acts programmatically across systems. Governing them as workloads aligns control design with machine-to-machine behavior, so teams can apply scoped credentials, policy enforcement, monitoring, and revocation discipline. That distinction matters for auditability, containment, and safe scaling.
👉 Read our full editorial: AI agent identity needs first-class IAM, not static service accounts