Notifications
Clear all
Topic starter
26/08/2026 11:51 am
TL;DR: AI agents are spreading across enterprise stacks with broad permissions, long-lived tokens, and weak ownership, and Cakewalk’s analysis argues that incidents like OpenClaw and Moltbook exposed a governance gap rather than a model failure. The real issue is that traditional IAM assumes human-paced approval and review cycles, while agent access behaves like a privileged identity that can act continuously at machine speed.
NHIMG editorial — based on content published by Cakewalk: Talk the Walk OpenClaw & Moltbook: Why AI Agent Access Is The Next Identity Crisis
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%).
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job.
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do AI agents create new risk in non-human identity management?
A: AI agents create risk because they operate as software identities with delegated authority, but many organisations do not track them with the same discipline applied to users or service accounts.
Q: What breaks when AI agents are given broad standing access?
A: Broad standing access breaks governance because the agent can move from one task to another without a fresh authorization check.
Practitioner guidance
- Inventory every AI agent and its connected systems Create a complete register of agentic identities, linked applications, permission scopes, and business owners.
- Replace broad tokens with task-scoped access Reduce each agent to the smallest feasible permission set, then time-box access so the credential cannot outlive the task.
- Add an approval path for new AI agent connections Require documented review before any agent is connected to production systems, especially MCP-backed tools, cloud infrastructure, or shared repositories.
What's in the full article
Cakewalk's full article covers the operational detail this post intentionally leaves for the source:
- A step-by-step framework for discovering AI agents across developer tools, automation platforms, and third-party services
- Practical guidance on assigning ownership, approval paths, and review cadence for agent access
- The article's discussion points on applying least privilege and short-lived credentials to agent permissions
- Examples of how to think about agent access management when multiple humans influence one identity
👉 Read Cakewalk's analysis of AI agent access governance and identity risk →
AI agent access governance: what IAM teams need to fix now?
Explore further
26/08/2026 11:51 am
AI agent access is becoming a privileged identity problem, not an AI model problem. The article’s core lesson is that the dangerous behaviour sits in the access layer, not in the model itself. When an agent can act across systems with a single broad token, identity governance has already failed before the model produces an output. Practitioners should treat agent access as a privileged identity class with explicit ownership and scope.
A few things that frame the scale:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems (39%), inappropriately sharing sensitive data (31%), and revealing access credentials (23%), according to AI Agents: The New Attack Surface report.
- Another 52% of companies cannot track and audit the data their AI agents access, which leaves a compliance and investigation blind spot that is already operational, not theoretical.
A question worth separating out:
Q: Who should own review and offboarding for service accounts and AI agents?
A: Ownership should sit with the team that relies on the identity to run production work, with identity governance defining the policy and evidence requirements. If ownership is left ambiguous, offboarding slows down, rotation stalls, and stale credentials stay active long after their original purpose has ended.
👉 Read our full editorial: AI agent access governance is the next identity crisis
