Topic starter
06/11/2026 6:40 pm
TL;DR: One agent simultaneously touches devices, applications, networks, data and user identity, which turns cell-based coverage into a false sense of control, according to Aizome. The practical issue is that identity, scope and behavioural baselines have to come before any meaningful detection or response.
Editorial analysis by NHI Mgmt Group, based on content published by Aizome: “The Framework That Defined Cybersecurity Doesn’t Work for AI. Here’s What Does.”.
Key questions
Q: How should teams govern AI agents that act across multiple security control planes?
A: Teams should govern AI agents as delegated actors with explicit scope, approved tools, and named human accountability.
Q: Why do AI agents create higher access risk than human users in identity models?
A: AI agents create higher access risk because they act at machine speed, operate continuously, and can invoke multiple tools or APIs without the pauses, judgment, or fatigue limits of humans.
Q: What is the difference between human identity governance and AI agent governance?
A: Human identity governance focuses on people, sessions, approvals, and access reviews.
Practitioner guidance
- Define governed AI agent identity boundaries Assign each agent a named owner, declared purpose and explicit scope so the security programme can treat it as an accountable actor rather than an anonymous workflow.
- Baseline agent behaviour before expanding controls Record normal tool use, data access patterns and system reach for each agent so deviations can be identified against a real operating baseline.
- Map controls by actor behaviour, not by asset class Reconcile your existing stack against what the agent actually does across identity, application, network and data planes, then close the gaps that remain unassigned.
Bottom line: AI agents can defeat row-and-column security models by crossing identity, application, network and data boundaries in one session.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:41 pm
AI agent security is a coverage problem, not a single-control problem. The article is right to reject the idea that one product or one control cell can govern an agent that behaves across identity, application, network and data planes at once. That is why point solutions tend to overstate coverage and understate residual risk. Practitioners should treat AI agent security as a stack design problem, not a product-selection exercise.
A question worth separating out:
Q: What are the signs that an AI agent has gone out of scope?
A: Common signs include attempts to use unapproved tools, unexpected access to production data, spawning additional agents without a clear mandate, and repeated requests that expand beyond the original task. The key indicator is deviation from the declared lane, especially when the action is technically possible but operationally out of policy.
👉 Read our full editorial: AI agents break the Cyber Defense Matrix's identity assumptions