Topic starter
06/06/2026 2:23 am
TL;DR: AI agents are already embedded across enterprise workflows, unsanctioned agents are appearing before governance is in place, and scope violations are now routine rather than exceptional, according to a CSA and Zenity survey of 445 IT and security professionals. Existing compliance frameworks are helping define oversight, but they are not closing the operational gap.
Editorial analysis by NHI Mgmt Group, based on content published by Zenity: “AI Agents Are Already Running the Enterprise. Security Hasn't Caught Up.”.
Key questions
Q: What breaks when AI agents are allowed to contain incidents without governance?
A: The response chain becomes difficult to audit and reverse.
Q: What are the signs that AI agent permissions are too broad in enterprise environments?
A: Common warning signs include agents accessing tools they do not need, performing irreversible actions without confirmation, retrieving cross-tenant or unrelated data, and acting with long-lived credentials.
Q: How do security teams know whether an AI agent control stack is actually working?
A: Look for three things: every agent has a traceable identity, permissions are narrow enough to explain in operational terms, and actions can be audited end to end.
Practitioner guidance
- Establish a formal agent inventory Record every sanctioned and unsanctioned agent, its business owner, platform, data access, and approval state before allowing production use.
- Constrain agent permissions to task scope Map each agent to a narrow business purpose and deny broad standing access that lets it move from retrieval into modification or execution.
- Implement runtime logging for agent actions Capture tool calls, object changes, and delegated actions so overreach can be reconstructed after an incident and contained faster.
Bottom line: AI agents are already creating governance problems inside live business workflows, and the main failure is not future adoption but present-day scope drift.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/06/2026 4:02 am
AI agent governance now fails at the point of execution, not at the point of policy. The article shows that many organisations can describe oversight for AI agents, but far fewer can enforce scope in real time. That is a control-plane problem, not a documentation problem, and it means policy language is outrunning technical containment. Practitioners should treat runtime authorisation as the real control boundary.
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.
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 agents are already outpacing enterprise security controls