Notifications
Clear all
Topic starter
20/08/2026 5:56 pm
TL;DR: AI tools like Glean and Claude Cowork can expose sensitive enterprise data through natural-language queries and autonomous workflows, making traditional DLP blind to how data is synthesized, copied, and moved across SaaS and MCP-connected systems, according to Nightfall. The security gap is no longer hypothetical: agentic access now requires interaction-layer controls, audit trails, and policy enforcement tied to AI outputs, not just files and email.
NHIMG editorial — based on content published by Nightfall: 100 SaaS Apps. One Query. Zero Alerts: How Glean and Claude Cowork Expose the Agentic AI Data Risk
By the numbers:
- Glean connects to over 100 SaaS applications, which expands the number of systems a single AI query can traverse at once.
- While 71% of IT teams have been advised on AI agent data access, only 47% of compliance teams, 39% of legal teams, and 34% of executives have the same visibility.
Questions worth separating out
Q: What breaks when AI search tools are allowed broad access to SaaS data?
A: Broad AI search breaks when it can synthesize data across systems into a single response that users can copy out without triggering file-based controls.
Q: Why do AI agents complicate access governance more than ordinary automation?
A: AI agents complicate access governance because they can branch at runtime, wait on external services, and continue later with the same operational context.
Q: How can security teams tell whether AI lifecycle controls are working?
A: They should look for evidence that access requests, policy enforcement, and usage visibility are centrally recorded and current.
Practitioner guidance
- Map AI connector reach before enabling broad adoption Inventory every SaaS application, browser integration, and MCP-connected workflow that an AI tool can query or modify.
- Inspect AI outputs as policy enforcement points Apply detection and response logic to the answer the model returns, not only to the source file or database.
- Constrain delegated actions with least privilege Limit what an agent can read, write, and trigger across connected systems, and review those permissions separately from the user who launched the session.
What's in the full article
Nightfall's full article covers the operational detail this post intentionally leaves for the source:
- How Glean's browser-based query path can surface cross-system data without triggering traditional file or email DLP
- How Claude Cowork's multi-step workflows interact with local and SaaS environments through MCP-connected access
- How Nightfall recommends extending policy to the AI interaction layer and agentic workflows
- How incident teams can use AI activity logs to reconstruct what was queried, returned, and copied
👉 Read Nightfall's analysis of agentic AI data exfiltration risk →
Agentic AI data exfiltration: are legacy DLP controls keeping up?
Explore further
20/08/2026 6:36 pm
Agentic AI has created a data plane problem that legacy DLP cannot see. The issue is not simply that more data is accessible. It is that AI tools recombine data across SaaS boundaries into outputs that look like normal chat content, file summaries, or workflow results. That breaks the assumptions behind signature-based prevention and shifts governance toward runtime inspection. Security teams need to recognise that the control failure is visibility into synthesized output, not just source-system access.
A question worth separating out:
Q: Who is accountable when AI search exposes sensitive enterprise data?
A: Accountability sits with the teams that approved the data connections, retrieval scope, and response handling, not just the users who queried the system. Governance should cover access design, provenance controls, and operational monitoring across identity, search, and AI platform owners.
👉 Read our full editorial: Agentic AI data exfiltration is outpacing legacy DLP controls
