Topic starter
06/09/2026 5:18 pm
TL;DR: AI agents are moving into production fast, but LEVO argues that nearly 9 out of 10 enterprises expect deployment by 2025 while half of pilot projects stall because security and compliance concerns remain unresolved. The core issue is that static IAM and perimeter controls cannot govern machine-speed, context-driven agent behaviour, so Zero Trust becomes the required model for verification, auditability, and blast-radius control.
Editorial analysis by NHI Mgmt Group, based on content published by LEVO: “Zero Trust Architecture for AI-Driven Market Leadership”.
By the numbers:
- Nearly 9 out of 10 enterprises expect AI agent deployment by 2025.
- Zero Trust Architecture is already embraced by 63% of organizations.
- The article says 73% of enterprises report experiencing at least one AI related security issue.
Key questions
Q: Why do static IAM roles break down for AI agents?
A: Static IAM roles break down because agent intent is not fully known when access is granted.
Q: Why do AI agents need Zero Trust instead of perimeter security?
A: AI agents operate inside the environment while still behaving like active decision-makers, so perimeter controls no longer define trust.
Q: What are the signs that AI governance is failing in the enterprise?
A: Common warning signs include rapid growth in AI use without matching policy coverage, sensitive files being copied into personal accounts, and a large share of AI apps carrying high or critical risk.
Practitioner guidance
- Assign unique identities to every AI agent instance Do not let agents inherit a human account, shared token, or generic service identity.
- Enforce per-request authorisation for prompts and API calls Evaluate every agent action against current context, data sensitivity, and intended purpose instead of granting broad session-wide access.
- Constrain blast radius with microsegmentation Separate agents by trust zone, workload, and data class so a compromised or misdirected agent cannot traverse the environment freely.
Bottom line: AI agents expose a structural mismatch between dynamic runtime behaviour and the static assumptions embedded in legacy IAM.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/09/2026 5:19 pm
Static IAM assumptions collapse when the identity itself is making runtime decisions. IAM was designed for subjects whose access could be provisioned, reviewed, and recertified on a stable schedule. That assumption fails when an AI agent changes tool use, timing, and scope inside the session. The implication is that identity governance has to move from entitlement administration to continuous runtime control.
A few things that frame the scale:
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
- 62% of organisations are at least experimenting with AI agents, but only 23% have scaled one into a single business function, according to McKinsey's 2025 State of AI survey.
A question worth separating out:
Q: How should security teams implement microsegmentation for AI-driven workloads?
A: Start by segmenting around business functions and workload identity, not just subnets. Define which service accounts, APIs, and automation components are allowed to talk to each other, then enforce that policy continuously. The goal is to stop a compromise from spreading across tiers even when the attacker is using AI to move quickly.
👉 Read our full editorial: Zero Trust for AI agents: why traditional IAM falls short