Topic starter
11/08/2026 3:16 pm
TL;DR: AI agents now operate inside enterprise systems faster than governance can adapt, with 53% of AI interactions already autonomous actions and 93% of prompts approved by human reviewers, according to Island and McKinsey. The real issue is not model quality but identity, policy, and audit gaps around non-human actions.
Editorial analysis by NHI Mgmt Group, based on content published by Island: “The control plane for the agentic enterprise”.
By the numbers:
- 92% of MCP server owners have no verifiable organizational affiliation.
Key questions
Q: What breaks when agentic control planes are governed like normal applications?
A: What breaks is the assumption that access can be reviewed after it has already been exercised.
Q: Why do autonomous agent workflows create more identity risk than human-in-the-loop prompts?
A: Because the review step often validates a prompt after the machine has already shaped the action path.
Q: How do security teams know if agent governance is actually working?
A: It is working only if the team can answer three questions quickly for any agent: what it can reach, what it did recently, and whether that behaviour matches intent.
Practitioner guidance
- Inventory every agent and its execution surface Build a complete inventory of agents, associated MCP servers, skills, packages, extensions, and the browser or endpoint surfaces they can touch.
- Move policy enforcement to runtime Apply controls at the point where an agent calls a tool, opens a file, or attempts a sub-agent action, rather than relying on upstream approval alone.
- Issue just-in-time credentials for agents Replace standing keys with ephemeral access that is bound to a specific task and revoked when the task ends.
Bottom line: Agentic enterprise control planes create governance risk because non-human actors can execute inside business systems without the onboarding and review assumptions built for people.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/08/2026 3:28 pm
Agentic enterprise governance is collapsing into an identity problem because the actor is no longer predictable at provisioning time. Traditional IAM assumes access can be defined before use and then reviewed after use. That assumption weakens when an agent can select tools, sequence actions, and continue execution inside a single task. The implication is that identity governance must shift from static entitlement views to runtime action governance.
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.
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between IAM and PAM in identity governance?
A: IAM governs authentication and ordinary access across the estate, while PAM constrains elevated privileges and high-risk sessions. In practice, IAM answers who should get in, and PAM answers who can perform sensitive actions once inside. Strong programmes use both, with governance ensuring that access remains current and justified.
👉 Read our full editorial: Agentic enterprise control planes are becoming an identity problem