Topic starter
02/08/2026 11:36 am
TL;DR: Data exfiltration now moves through AI tools, browser sessions, cloud sync, email, and removable media, and Cyberhaven says 39.7% of AI interactions involve sensitive data while about 44% happen through personal accounts. Legacy DLP cannot reliably track transformed data or prompt-level movement, so detection has to shift toward lineage and behavior-aware controls.
Editorial analysis by NHI Mgmt Group, based on content published by Cyberhaven: “Most Common Forms of Data Exfiltration”.
By the numbers:
- 39.7% of all AI interactions involve sensitive data, according to Cyberhaven research cited by Cyberhaven.
- Approximately 44% of AI use occurs through personal accounts where enterprise visibility is absent, according to Cyberhaven research cited by Cyberhaven.
Key questions
Q: What fails in traditional DLP when employees use AI tools with enterprise data?
A: Traditional DLP fails when data is no longer moving only through files, email, and endpoints.
Q: Why do personal AI accounts and browser sessions increase exfiltration risk?
A: They increase risk because the enterprise loses visibility into both the session and the destination.
Q: What are the signs that browser-based exfiltration is happening?
A: Common indicators include unusual webmail forwarding, external form submissions, spikes in cloud sync activity, repeated uploads to unsanctioned SaaS tools, and copy-paste behaviour that does not match a user’s normal role.
Practitioner guidance
- Deploy transfer-time controls for AI and browser sessions Intercept copy, paste, upload, and submission actions in browser-mediated workflows so sensitive data can be governed before it reaches third-party AI tools or unsanctioned SaaS destinations.
- Map and monitor data lineage for high-value information Track sensitive data from source systems through downstream copies, summaries, and reformats so security teams can see where information actually leaves control.
- Separate sanctioned AI use from personal-account use Identify where employees are using public or personal AI accounts and apply policy controls that differentiate approved enterprise sessions from unmanaged ones.
Bottom line: AI tools and browser-based workflows have become common exfiltration paths because they move sensitive data in ways legacy DLP was not designed to inspect.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:50 pm
AI-based exfiltration is a data governance problem that legacy DLP was never built to solve. The core failure is not simply that users share data, but that they do so through prompts, browser sessions, and transformed outputs that break file-centric inspection. That means confidentiality controls now have to follow data through identity and session context, not just through content signatures. Practitioners should treat this as a control-plane shift, not a tuning exercise.
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.
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.
A question worth separating out:
Q: How should security teams govern data lineage for AI systems?
A: Security teams should govern data lineage by tracing every AI input class to an owner, a source system and a freshness rule. Training data, RAG sources, embeddings, prompts and agent inputs need different controls because they shape behaviour in different ways. The goal is to prove provenance, not just collect logs.
👉 Read our full editorial: AI-based data exfiltration is outpacing legacy DLP controls