Notifications
Clear all
Topic starter
15/05/2026 8:23 pm
TL;DR: AI agents inherit IAM roles when they go live, and reused templates often leave them over-privileged, with non-human identities now outnumbering human identities by more than 80 to 1 and over 90% of cloud identity permissions going unused, according to Sonrai Security. The practical issue is not visibility alone, but enforcing least privilege before agent deployment velocity turns drift into persistent blast-radius risk.
NHIMG editorial — based on content published by Sonrai Security: How AI Agents Accumulate Permissions Over Time and the Associated Security Risks
By the numbers:
- Non-human identities now outnumber human identities by more than 80 to 1 in enterprise environments.
- 90% of permissions assigned to cloud identities go, es go unused.
- 40% of enterprise applications will include integrated task-specific AI agents by the end of 2026.
Questions worth separating out
Q: How should teams govern AI agent permissions in cloud environments?
A: Start by treating each AI agent as a non-human identity with its own lifecycle, access review, and blast radius.
Q: When does AI agent over-privilege become a real security problem?
A: It becomes a real problem as soon as the agent can reach more systems, data, or actions than the workflow requires.
Q: What is the difference between JIT access and standing privilege for AI agents?
A: Standing privilege gives the agent persistent elevated access, while JIT access limits privilege to a specific task and then revokes it automatically.
Practitioner guidance
- Scope one IAM role per agent and workload Avoid shared roles across multiple agents.
- Replace standing privilege with JIT exceptions Keep baseline access minimal and use time-bound approvals for any elevated task.
- Enforce least privilege at the org level Use native cloud controls to block unused permissions centrally instead of relying on per-identity cleanup queues.
The governance question is shifting from whether agents are allowed to act to how far any one agent can reach before controls intervene?
👉 Read Sonrai Security's analysis of AI agent permission sprawl in cloud IAM →
Explore further
15/05/2026 8:23 pm
AI agent privilege drift is becoming the defining NHI governance problem in cloud environments. The issue is not simply that agents need access. It is that access frequently accumulates faster than lifecycle controls can remove it, which turns short-lived workflows into durable risk. That makes identity blast radius the central metric for agent governance, not raw agent count. Practitioners should measure whether each agent’s access still matches the current workload.
A few things that frame the scale:
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems, according to the 2026 Infrastructure Identity Survey.
- That same survey found that 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems.
A question worth separating out:
Q: Why do AI agents complicate traditional IAM reviews?
A: Traditional IAM review assumes identities have human lifecycle events such as hire, role change, or offboarding. AI agents do not follow that pattern, so access can drift silently unless teams build continuous entitlement governance. Without that shift, reviews become retrospective paperwork instead of active risk reduction.
👉 Read our full editorial: AI agent permission sprawl is widening cloud identity blast radius
