Topic starter
02/08/2026 11:23 am
TL;DR: Shadow agents are autonomous AI agents running locally or through MCP servers without IT or security approval, and Cyberhaven says they bypass browser proxies, SSO logs, and legacy DLP channels that were built for human-paced activity. The governance model fails when agents can read, call, write, and transmit data at machine speed without a human-in-the-loop checkpoint.
Editorial analysis by NHI Mgmt Group, based on content published by Cyberhaven: “What Are Shadow Agents and Why Are They a Security Risk?”.
By the numbers:
- endpoint-based AI agents grew 509% in 2025
Key questions
Q: What breaks when shadow agents are allowed to run outside approved controls?
A: Browser proxies, SSO logs and legacy DLP stop providing a reliable record of what the agent is doing.
Q: Why do shadow agents create a different risk profile from other shadow AI use?
A: Because the agent removes the human-in-the-loop checkpoint.
Q: What are the signs that endpoint governance is failing?
A: The warning signs are fragmented inventories, repeated portal switching, inconsistent policy enforcement, and devices reaching resources without clear posture validation.
Practitioner guidance
- Map endpoint-installed agents and MCP servers Create an inventory of locally installed agents, development assistants and MCP-connected services across user endpoints and developer machines.
- Move discovery to the operating system layer Use endpoint telemetry to identify which processes are reading files, calling external APIs or writing to repositories, because browser and proxy logs will miss that activity.
- Review delegated permissions as non-human identity scope Treat agent permissions as identity scope, not app settings, and evaluate whether file-system, clipboard, cloud and repository access matches the minimum task requirement.
Bottom line: Shadow agents are risky because they execute outside the browser and outside the human-paced oversight model that most AI governance programmes still rely on.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:40 pm
Browser-era AI governance is structurally mismatched to endpoint agents. Most organisations built their AI controls around web sessions, proxy inspection and SSO logging. Shadow agents operate below those layers, so the governance model is observing the wrong plane of activity. The practitioner takeaway is that discovery, authorization and monitoring must move to the endpoint and process level if the programme is meant to govern autonomous behaviour at all.
A few things that frame the scale:
- 28% of secrets incidents now originate outside code repositories, in Slack, Jira, and Confluence, and are 13% more likely to be categorised as critical than code-based leaks, according to the State of Secrets Sprawl 2026.
- 52% of respondents see AI security decision-making power shifting toward platform and infrastructure teams rather than the executive suite, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should organisations treat MCP connectors like ordinary integrations?
A: No. MCP connectors often carry delegated access into multiple tools and data stores, which makes them part of the identity control plane. They should be registered, scoped, monitored, and offboarded like any other privileged machine identity, otherwise a compromise in one connector can expand into broader system access.
👉 Read our full editorial: Shadow agents expose the limits of browser-era AI governance