Topic starter
06/06/2026 11:12 am
TL;DR: C1.ai says enterprise AI agent adoption is outrunning governance, with 85% of organisations experimenting, only 5% in production, and 59% admitting shadow AI outside the perimeter. The central problem is that identity programmes built for human review cycles cannot control autonomous agents or MCP-mediated tool access fast enough.
Editorial analysis by NHI Mgmt Group, based on content published by C1.ai: “A CISO's Top 3 Takeaways from RSA Conference 2026”.
By the numbers:
- 85% of enterprises are experimenting with AI agents, while only 5% have moved them to production.
- 59% admit shadow AI operates entirely outside their governance perimeter.
- 60% of organizations cannot terminate a misbehaving agent once it's running.
Key questions
Q: How should teams govern AI agents that use MCP?
A: Treat each connected agent as a non-human identity with an owner, a scope, and a review cycle.
Q: Why do autonomous agents make traditional access reviews less effective?
A: Access reviews assume permissions persist long enough to be observed, challenged, and recertified.
Q: What breaks when AI agents are not inventoried or classified?
A: When AI agents are not inventoried or classified, organisations lose the ability to assign risk, apply the right obligations, and prove control to auditors.
Practitioner guidance
- Inventory every agent identity Build a living register of AI agents, owners, permitted tools, and business purpose so governance starts with discovery rather than assumption.
- Govern MCP as a control plane Require authentication, authorisation, audit logging, and policy enforcement for each MCP endpoint and each connected tool.
- Replace periodic reviews with runtime controls Move agent governance from quarterly certification to issuance-time and action-time controls that can stop or constrain execution before the task completes.
Bottom line: AI agent adoption is outpacing the governance models most identity teams still use, which leaves ownership, scope, and accountability unresolved.
What's in the full article
C1.ai's full blog covers the operational detail this post intentionally leaves for the source:
- The specific RSA conference keynote themes and vendor examples that shaped the three takeaways.
- The discussion of MCP gateways, agent identity products, and how each vendor is positioning protocol-layer governance.
- The cited industry statistics and conference observations behind the 85% adoption, 5% production, and 22-second response claims.
- The blog's full breakdown of why autonomous defence and agent governance are being treated as one problem.
👉 Read C1.ai's analysis of AI agent identity governance and MCP →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/06/2026 11:52 am
AI agent governance is now an identity governance problem, not an AI side topic. The article describes a market where adoption is ahead of policy, ownership, and audit. That means the centre of gravity has moved from human access administration to machine decision authority, and identity programmes that do not treat agents as governed subjects are already incomplete. The practitioner conclusion is straightforward: if an agent can act, it must be governable as an identity.
A few things that frame the scale:
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between AI agent governance and traditional IAM?
A: Traditional IAM focuses on human users and static entitlements, while AI agent governance must handle autonomous execution, tool access, and rapidly changing context. The difference is operational as much as technical. AI agents can keep acting after the original task ends, so teams need continuous controls, not just periodic access reviews.
👉 Read our full editorial: AI agent identity governance is colliding with MCP and autonomy