Topic starter
15/08/2026 6:06 pm
TL;DR: Enterprise AI guardrails are becoming necessary because AI agents move 16x more data than human users while 90% hold excessive privileges, according to Obsidian Security's analysis of AI guardrails. The core issue is that traditional IAM assumes stable, reviewable authority, but AI systems act at runtime with access patterns that outpace static controls.
Editorial analysis by NHI Mgmt Group, based on content published by Obsidian Security: “AI Guardrails: Enforcing Safety Without Slowing Innovation”.
By the numbers:
- AI agents move 16x more data than human users.
- 90% of those agents hold excessive privileges.
Key questions
Q: How should security teams authorize AI agents that need changing access over time?
A: Security teams should model AI agents as first-class identities with explicit relationships to resources, teams, and shared data.
Q: Why do AI agents complicate privilege governance?
A: AI agents complicate privilege governance because they can request access, use tools, and execute actions faster than human review cycles.
Q: What are the signs that AI guardrails are not keeping up with runtime demands?
A: Common signs include selective deployment, inconsistent moderation outcomes across environments, growing exception lists, and teams routing around controls to protect latency.
Practitioner guidance
- Map effective authority, not just assigned roles Inventory what each AI agent can actually reach across SaaS, cloud, and internal systems, then compare that reach with the workflow it is supposed to perform.
- Separate agent access by workflow and data scope Avoid shared high-privilege agent roles.
- Add runtime behavioural monitoring for AI actions Track prompts, tool calls, data accessed, and unusual cross-application movement so that deviations can be detected while the agent is still active.
Bottom line: AI agents create a governance problem because their runtime authority can exceed what traditional IAM and review cycles were designed to observe.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
15/08/2026 6:15 pm
Effective authority, not configured authority, is the control variable that now matters. Obsidian Security's analysis shows that AI agents can hold access that looks acceptable on paper while behaving in ways that expand real reach at runtime. That makes policy-as-config insufficient on its own, because what matters is the scope the agent can actually exercise across systems. The practitioner conclusion is simple: governance must measure the authority an agent can use, not the permissions a dashboard says it has.
A few things that frame the scale:
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should organisations do when an AI agent has more privilege than its workflow needs?
A: They should reduce the agent's reachable systems, narrow the tools it can invoke, and separate the agent's runtime permissions from the human user's broader rights. The goal is to limit blast radius so a single compromised workflow cannot expand into unrelated data or services.
👉 Read our full editorial: AI guardrails expose the limits of traditional IAM for agents