Topic starter
02/08/2026 11:38 am
TL;DR: AI agents in IDEs, endpoints, SaaS, and MCP-connected systems inherit user permissions and can read files, query databases, call APIs, and chain actions without continuous human oversight, according to Cyberhaven. The governance problem is no longer prompt safety alone: security teams need inventory, observability, and runtime controls that can track agent behaviour across the full execution lifecycle.
Editorial analysis by NHI Mgmt Group, based on content published by Cyberhaven: “Agentic AI Security: Visibility and Control for AI Agents at Work”.
Key questions
Q: What breaks when AI agents are given broad inherited permissions?
A: Broad inherited permissions break the assumption that access is tied to a narrow business need.
Q: Why do agentic AI workflows create more risk than browser-based chat prompts?
A: Browser prompts are discrete interactions, but agentic workflows can chain tool calls, access data sources, and trigger follow-on actions.
Q: How do security teams know if agent observability is actually working?
A: Observability is working only when teams can tie together token activity, tool calls, and latency for a specific agent session.
Practitioner guidance
- Define agent-specific identity scope Separate AI agent permissions from the human user’s full access wherever possible, and document which data sources, APIs, and SaaS systems each agent may touch.
- Inventory unmanaged agents and connectors Continuously discover local agents, IDE assistants, MCP servers, and unsanctioned connectors so authorisation decisions are based on current inventory, not assumed approvals.
- Correlate agent actions into a single execution record Track prompt context, tool calls, data access, and downstream writes as one chain so security teams can judge whether an agent’s behaviour crossed a boundary.
Bottom line: AI agents inherit user permissions and can act across multiple enterprise systems without the continuous oversight that existing IAM controls assume.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:51 pm
Agentic AI exposes an inherited-access model that enterprise IAM was never designed to govern: the article makes clear that agents often act with the permissions of the deploying user, not with a purpose-built identity and scope. That sounds convenient until the delegated software actor starts reading, writing, and combining data across tools at machine speed. The governance problem is not merely broader access, but access exercised by a non-human actor that does not behave like the person it represents. Practitioners need to treat delegated agent authority as a first-class identity domain.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
- 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: How should organisations govern shadow agents and unsanctioned MCP connections?
A: Treat them as identity and authorisation problems, not just software sprawl. Organisations need continuous discovery, ownership, and approval boundaries for any agent or connector that can reach corporate data or invoke enterprise actions.
👉 Read our full editorial: Agentic AI security exposes the visibility gap in enterprise IAM