Topic starter
02/08/2026 11:33 am
TL;DR: 39.7% of the data shared with AI tools is sensitive, Cyberhaven Labs reports, showing that legacy DLP still misses prompts, copilot use, and agentic workflows. Data governance now has to follow submissions into AI tools, where provenance and destination policy matter as much as content inspection.
Editorial analysis by NHI Mgmt Group, based on content published by Cyberhaven: “DLP for GenAI: How to Prevent Sensitive Data Leaks in AI Tools”.
Key questions
Q: Why do legacy DLP controls fail against AI prompts and copilots?
A: Legacy DLP fails because it assumes data moves through fixed channels such as email, files, or USB, while AI prompts often move as copied text through browser interfaces or embedded copilots.
Q: What are the signs that data governance is too weak for safe GenAI adoption?
A: Warning signs include widespread oversharing, unclear classification labels, inconsistent group membership, and access-control lists that are not kept current during onboarding and offboarding.
Q: How should organisations control sensitive data in GenAI tools?
A: Organisations should treat prompts, uploads, and model outputs as governed data flows, then apply classification, inspection, and logging at the point of use.
Practitioner guidance
- Map GenAI egress paths to data classes Identify where sensitive information can leave controlled repositories through prompts, browser assistants, copilots, and automated agent workflows, then bind those paths to data classification policy.
- Build an AI tool inventory with handling terms Maintain a live catalogue of approved AI tools, whether they train on submitted content, and where they store prompts or outputs so policy can distinguish acceptable from prohibited destinations.
- Enforce endpoint-level submission controls Monitor copy, paste, and browser submission events at the endpoint so controls can see data leaving the source document before it reaches an AI interface.
Bottom line: Legacy DLP misses GenAI risk because sensitive data now moves through prompts, copilots, and agentic workflows that do not resemble traditional file transfer.
Glossary terms: Data Lineage, Shadow AI, Agentic workflow, Prompt Submission Control
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 12:48 pm
Legacy DLP has become a channel-control problem in an AI workflow world: controls built for email, USB, and file transfer cannot reliably govern copy-paste submission into GenAI tools. The gap is not only technical detection but policy scope, because the same data can now enter sanctioned and unsanctioned AI services through browser interfaces and embedded copilots. Practitioners should treat GenAI as a new data egress class, not as another messaging channel.
A few things that frame the scale:
- 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.
- Internal repositories are 6x more likely to contain secrets than public ones (32.2% vs 5.6%), contradicting the assumption that private repos are safe, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How should organisations control AI agents that query sensitive business data?
A: Treat agents as governed identities with bounded purpose, not as open-ended query clients. Apply attribute and purpose checks, restrict raw field access, and default to aggregation or masking unless the request is explicitly justified. That keeps AI usage within policy and prevents agents from becoming a shortcut around human approval controls.
👉 Read our full editorial: DLP for GenAI exposes the limits of legacy data controls