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.
Editorial analysis by NHI Mgmt Group, based on content published by Sonrai Security: “How AI Agents Accumulate Permissions Over Time and the Associated Security Risks”.
By the numbers:
- Gartner projects that 40% of enterprise applications will include integrated task-specific AI agents by the end of 2026.
- Non-human identities now outnumber human identities by more than 80 to 1 in enterprise environments, according to the 2025 Identity Threat Landscape Report cited by Sonrai Security.
- Over 90% of permissions assigned to cloud identities go unused, according to Sonrai Security.
Key questions
Q: What breaks when AI agents share the same cloud IAM role?
A: Shared roles break attribution and expand blast radius.
Q: Why do AI agent permissions keep growing even when teams know they are excessive?
A: Because deployment speed outpaces IAM governance.
Q: How should security teams enforce least privilege for AI agent identities?
A: Start by treating every agent as an NHI with a dedicated identity, a tight permission boundary, and a named owner.
Practitioner guidance
- Scope one role per agent and workload Eliminate shared IAM roles for AI agents wherever attribution or blast-radius control matters.
- Enforce org-level least privilege Move privilege reduction out of manual queues and into cloud-wide policy enforcement so unused permissions cannot linger until the next review cycle.
- Replace standing access with JIT exceptions Treat elevated permissions as time-bound exceptions and revoke them automatically when the task finishes.
Bottom line: AI agent permission sprawl turns cloud identity design into a blast-radius problem when roles are reused across workloads.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
15/05/2026 8:23 pm
AI agent permission sprawl is a governed identity problem, not a visibility problem. Sonrai Security's article shows that cloud teams often know permissions are excessive but still struggle to remove them at scale. That matters because reporting does not reduce blast radius unless the organisation can enforce least privilege across the fleet. The practitioner conclusion is that agent roles must be treated as governed identities from deployment onward.
A few things that frame the scale:
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: When should organisations prioritise just-in-time access for AI agents over standing credentials?
A: Organisations should prioritise just-in-time access when AI agents need elevated permissions only for specific tasks, environments, or short windows of time. It is especially important for production systems, sensitive data paths, and cross-domain actions. JIT reduces standing exposure, limits reuse of stolen credentials, and makes approval and audit trails clearer.
👉 Read our full editorial: AI agent permission sprawl is widening cloud identity blast radius
This post was modified 4 days ago by NHI Mgmt Group