Notifications
Clear all
Topic starter
09/07/2026 3:19 pm
TL;DR: AI access control governs what AI agents can access and do inside enterprise systems, and the gap is widening as 40% of enterprise applications are expected to embed task-specific agents by the end of 2026, according to Linx Security. The practical conclusion is that existing IAM must extend into inline, tool-level enforcement for agent identities, not sit beside it.
NHIMG editorial — based on content published by Linx Security: AI Access Control Jul 6, 2026 What Is AI Access Control? A Guide for Identity and Security Teams
By the numbers:
- 40% of enterprise applications are expected to embed task-specific AI agents by the end of 2026, up from less than 5% in 2025.
- 97% of organizations that suffered an AI-related breach lacked proper AI access controls.
- 82% of enterprises already have unknown AI agents operating in their environments.
Questions worth separating out
Q: How should security teams govern AI agents that use borrowed credentials?
A: Security teams should treat borrowed credentials as a high-risk delegation pattern, not a convenience.
Q: Why do AI agents complicate existing IAM and IGA programmes?
A: AI agents complicate IAM and IGA because they can be created programmatically, act continuously, and change access footprints faster than periodic review cycles can track.
Q: What breaks when AI access control is limited to logs and reviews?
A: Logs and reviews tell you what happened after the fact, but they do not stop an agent from making the wrong call in the moment.
Practitioner guidance
- Inventory every AI agent and delegated credential Build a complete register of agents, the service accounts or tokens they use, and the systems they can reach.
- Apply task-scoped least privilege to each agent Replace broad standing access with permissions tied to one task, one workflow, or one approval boundary.
- Enforce policy inline before tool execution Place decision logic at the MCP gateway or equivalent enforcement point so every tool call is checked before it reaches the target system.
What's in the full article
Linx Security's full blog post covers the operational detail this post intentionally leaves for the source:
- A step-by-step framework for discovery and inventory of AI agents across enterprise environments
- Detailed examples of tool- and parameter-level policy enforcement at the MCP gateway
- Implementation guidance for just-in-time access, continuous monitoring, and audit logging
- Practical examples of how to extend existing identity governance into the agentic layer
👉 Read Linx Security's guide to AI access control for identity and security teams →
AI access control and agent identities: what IAM teams need now?
Explore further
09/07/2026 3:37 pm
AI access control is now an IAM design problem, not an AI feature problem. The article correctly frames agents as identities with credentials, entitlements, and consequences. That means the control model belongs alongside IGA, PAM, and NHI governance, not in a separate AI operations silo. The practitioner conclusion is that identity programmes must treat agent actions as first-class governance events.
A few things that frame the scale:
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to the Ultimate Guide to NHIs.
- 91.6% of secrets remain valid five days after notification, showing how slowly remediation can follow exposure. That lag is why governance cannot depend on review cycles alone.
A question worth separating out:
Q: Who is accountable when an AI agent acts outside its intended scope?
A: Accountability should sit with the team that approved the agent's access model and operating boundaries, not with the downstream system that merely executed the request. If the agent used borrowed credentials or shared permissions, accountability also extends to the governance process that allowed ambiguous delegation. Clear ownership and traceable policy decisions are essential.
👉 Read our full editorial: AI access control is becoming the missing layer in IAM governance
