Notifications
Clear all
Topic starter
02/08/2026 11:33 am
TL;DR: AI agents are already reading files, calling APIs, executing code, and moving data across systems without human approval, while many are deployed through MCP servers security teams have not inventoried, according to Cyberhaven. Endpoint visibility, behavioural telemetry, and machine-speed policy enforcement now matter as much as traditional endpoint controls.
NHIMG editorial — based on content published by Cyberhaven: Agentic AI Security, Governing Shadow Agents on Endpoints
By the numbers:
- AI agents have already performed actions beyond their intended scope in 80% of organisations, including accessing unauthorised systems, sharing sensitive data, and revealing access credentials.
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes, and as quickly as 9 minutes in some cases.
Questions worth separating out
Q: How should security teams handle shadow AI on corporate endpoints?
A: Treat it as an identity governance issue, not just an endpoint hygiene issue.
Q: Why do AI agents create a bigger governance problem than ordinary endpoint tools?
A: Because an AI agent can execute many file reads, API calls, and transfers in one session without a human approving each step.
Q: What breaks when MCP servers are not registered centrally?
A: Unregistered servers create shadow deployment.
Practitioner guidance
- Inventory every agent and MCP connection Build an endpoint-by-endpoint register of installed AI agents, the tools they can call, and the MCP servers they reach.
- Track full agent sessions, not single events Collect telemetry for file reads, prompts, API calls, outputs, and destination systems across the whole agent session.
- Constrain agent permissions to the minimum viable scope Treat each agent like a delegated machine identity and remove broad file system, database, and browser access where it is not essential.
What's in the full article
Cyberhaven's full post covers the operational detail this analysis intentionally leaves for the source:
- Endpoint-level visibility examples for detecting shadow agents in active developer environments
- How the Data Lineage approach traces file reads, prompt content, and outbound transfers across AI sessions
- The Linea AI workflow details for real-time policy enforcement on agent-mediated activity
- Practical examples of how sanctioned and unsanctioned agent use can coexist on the same endpoint
👉 Read Cyberhaven's analysis of shadow agents on endpoints and agentic AI security →
Shadow agents on endpoints: are your controls keeping up?
Explore further
02/08/2026 12:47 pm
Shadow agents are now a governance class, not a niche endpoint concern. The article is right to separate sanctioned tools from the behaviour they can generate once deployed. When an agent can act autonomously on files, APIs, and browser sessions, the governance problem becomes identity-like: who or what has the authority to do this, under what scope, and for how long? Practitioners should treat shadow agents as a lifecycle and access problem, not just a monitoring problem.
A question worth separating out:
Q: How do organisations know if agentic AI governance is actually working?
A: Look for three signals: access decisions tied to task context, complete audit records linking agents to datasets, and rapid revocation when scope changes. If reviewers still need manual reconstruction after an incident, the programme is not mature. Effective governance produces explainable access, not just allowed or denied results.
👉 Read our full editorial: Agentic AI security on endpoints needs shadow agent governance
