Topic starter
02/08/2026 11:52 am
TL;DR: 80% year over year in GenAI SaaS data movement shows employees are moving sensitive information through conversational tools faster than legacy controls catch, based on Cyberhaven telemetry. Data governance now has to track prompts, account context, and lineage where the work happens.
Editorial analysis by NHI Mgmt Group, based on content published by Cyberhaven: “Top Generative AI Security Risks in the Enterprise”.
By the numbers:
- There has been an 80% year-over-year increase in data movement events into and out of GenAI SaaS, according to Cyberhaven.
Key questions
Q: Why do personal AI accounts create governance risk in software teams?
A: Personal accounts break visibility, ownership, and policy enforcement.
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.
Q: What breaks when employees use generative AI tools outside DLP coverage?
A: Legacy DLP breaks because it is tuned for file movement, not conversational disclosure.
Practitioner guidance
- Define AI egress as a monitored data path Extend DLP policies to cover prompts, uploads, copy-paste actions, and browser-based AI sessions so conversational disclosure is treated like other egress channels.
- Separate corporate and personal AI usage Use endpoint controls to identify whether AI activity occurs in enterprise-managed sessions or personal accounts, then apply different policy and logging rules to each.
- Add data lineage to AI monitoring Track where sensitive content originated, which AI tools handled it, and where the resulting data went so incident response and compliance evidence remain defensible.
Bottom line: Generative AI is exposing a control gap where sensitive information moves through conversational interfaces that legacy DLP programmes do not reliably monitor.
Glossary terms: Generative AI, Shadow AI, Data Lineage, Conversational DLP
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
02/08/2026 1:01 pm
Generative AI has turned data egress into a conversational control problem. The most important shift is not that AI creates new categories of sensitive data, but that it changes where and how exfiltration-like behaviour happens. Security teams that still anchor policy to file movement are governing yesterday's workflow, not today's. Practitioners should treat prompt-level disclosure as a first-class governance event.
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.
A question worth separating out:
Q: What should teams do first when sensitive data is moving through AI tools?
A: First, identify which AI tools, browser flows, and MCP-connected systems can touch sensitive data. Next, define what content is allowed, what must be masked, and what must be blocked. Finally, tie those rules to enforcement so policy applies in real time across the same workflows users rely on.
👉 Read our full editorial: Generative AI security risks are exposing data governance gaps