Topic starter
02/08/2026 11:23 am
TL;DR: Agentic AI breaks core security assumptions about known assets, deterministic behavior, and identity-based authorisation, and practitioners are converging on scoped identity, action-level approval, observability, and containment, according to OXSecurity. Static IAM models fail when agents make runtime decisions across tool chains and shadow AI expands faster than governance can track; the control problem is dynamic, not merely access-based.
Editorial analysis by NHI Mgmt Group, based on content published by OXSecurity: ““Be Violent With Your Agents”: The Hard Truths of Governing Agentic AI”.
Key questions
Q: What breaks when agentic AI relies on static IAM assumptions?
A: Static IAM breaks when the system can decide new steps at runtime.
Q: Why do AI agents require contextual authorisation instead of static entitlements?
A: Because the agent’s next action is not fully knowable at provisioning time.
Q: How do security teams know whether containment is actually working?
A: They should test whether the identity can still execute privileged actions after revocation, not just whether the API call succeeded.
Practitioner guidance
- Define scoped identities for every agent Give each agent its own narrowly bounded identity, eliminate shared credentials, and remove standing access wherever the task can be completed with task-scoped privilege.
- Require approval for high-impact actions Place explicit human or policy approval gates on destructive, external, or irreversible operations so the agent cannot self-authorize consequential steps.
- Build full agent observability Record prompts, tool calls, MCP interactions, and command context so security teams can reconstruct intent, not just events, after unexpected behaviour.
Bottom line: Agentic AI breaks the assumption that identity can be governed only through static entitlements, because runtime decisions and tool chaining change the actual control surface.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:40 pm
Static IAM is the wrong control model for agentic behaviour: The article shows that agentic systems invalidate the assumption that identity can be authorised once and then left alone. Once an actor can choose tools and sequence actions at runtime, the control problem shifts from access assignment to decision control. Practitioners need to recognise that static entitlements describe only the starting condition, not the security state.
A few things that frame the scale:
- Half of companies using generative AI will deploy agentic AI by 2027, according to Deloitte's 2025 Technology Predictions.
A question worth separating out:
Q: What should organisations do first when shadow AI appears in the environment?
A: Organisations should treat the tool as an unmanaged identity, then decide whether it is allowed to handle business data at all. The first 24 to 72 hours should focus on discovery, containment, and policy enforcement at the access boundary. If the tool cannot be governed inline, it should be denied by default.
👉 Read our full editorial: Agentic AI governance needs dynamic controls, not static IAM