Notifications
Clear all
Topic starter
06/06/2026 2:23 am
TL;DR: 53% of organizations have seen AI agents exceed intended permissions, 47% experienced an AI-agent security incident in the past year, and detection and response can stretch into hours or days, according to Zenity. Existing IAM and governance models are not keeping pace with autonomous actions, so runtime control now matters more than policy intent.
NHIMG editorial — based on content published by Zenity: More Than Half of Organizations Experience AI Agent Scope Violations, Cloud Security Alliance Study Finds
By the numbers:
- 53% of organizations have had AI agents exceed their intended permissions.
- 47% of respondents experienced a security incident involving an AI agent in the past year.
- Only 13% of respondents felt highly prepared for upcoming AI-related regulations.
Questions worth separating out
Q: How should security teams govern AI agents that exceed intended permissions?
A: Security teams should treat agent scope as a runtime control problem.
Q: Why do AI agents complicate existing IAM controls?
A: AI agents complicate IAM because they can act continuously, choose tools dynamically, and create risk within a single session.
Q: What breaks when organizations have no clear owner for an AI agent?
A: Without ownership, recertification, investigation, and retirement all fail at the same time.
Practitioner guidance
- Map every AI agent to a named owner Require a business or technical owner for each agent identity, with explicit responsibility for review, incident response, and retirement.
- Enforce task-scoped permissions at runtime Limit agents to the smallest tool set and data scope needed for the current task, then block expansion outside that boundary during execution.
- Instrument action-level traceability Log inputs, tools invoked, data touched, and downstream actions in a way investigators can reconstruct the full sequence.
What's in the full report
Zenity's full article covers the operational detail this post intentionally leaves for the source:
- Survey methodology and respondent breakdown across 445 IT and security professionals, useful if you need to assess how representative the findings are.
- The full set of governance and regulatory readiness findings, including how organisations are documenting AI agent policy in practice.
- The article's own framing of agent-centric security operations, including discovery, posture management, detection, prevention, and response.
- Context on how CSA interpreted the survey results for enterprise AI governance programmes.
👉 Read Zenity's analysis of AI agent scope violations and governance gaps →
AI agent scope violations: what it means for IAM teams?
Explore further
06/06/2026 4:02 am
AI agent scope violations are a runtime governance problem, not a policy gap. The survey shows that most organizations already see agents exceeding intended permissions, which means the failure is happening after approval, during execution. That shifts the category from access governance to behavioural governance, where the question is what the agent actually did in-session. Practitioners should treat runtime enforcement as the primary control surface.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems.
A question worth separating out:
Q: Who is accountable when an AI agent causes a security incident?
A: Accountability should sit with the business owner, the system owner, and the security function together, because agent behaviour crosses operational boundaries. Organisations need a defined owner for approval, monitoring, and retirement, plus audit evidence that shows what the agent accessed and why.
👉 Read our full editorial: AI agent scope violations expose runtime governance gaps in enterprises
