Topic starter
06/11/2026 6:40 pm
TL;DR: AI agents can expose sensitive data without malware, stolen credentials or obvious network activity, according to Cyera’s analysis of DLP failure modes. For practitioners, the control problem shifts to discovery, classification and scoping access before an agent can reach unclassified data.
Editorial analysis by NHI Mgmt Group, based on content published by Cyera: “A Guide to Data Leak Prevention in 2026”.
By the numbers:
- Cyera says 344 of 7,246 public AI incident reports were verified cases of agent-inflicted damage at the enterprise level, including 188 with no external attacker involved.
- Only 25% of organisations have a fully mature insider risk program with defined metrics and executive oversight, according to Ponemon Institute research cited by Cyera.
- 56% of organisations do not have adequate visibility into who can access their sensitive data, according to Ponemon Institute research cited by Cyera.
Key questions
Q: Why do AI agents create new data privacy risks?
A: AI agents can move data across tools and systems without a fixed human checkpoint, so they widen the number of places where sensitive information can be copied, transformed, or retained.
Q: What is the difference between data at rest, data in motion, and data in use?
A: Data at rest is stored and not moving, such as files, databases, and backups.
Q: How do data leak prevention controls work with unclassified data?
A: DLP controls work poorly with unclassified data because enforcement depends on knowing what is sensitive before policy can be applied.
Practitioner guidance
- Implement continuous data discovery and classification Build an always-current inventory of sensitive data across SaaS, cloud storage, endpoints and shared drives, then tie labels to enforcement so DLP policies act on known assets, not guesses.
- Scope AI agent access to task-specific datasets Remove standing access to broad folders and datasets, and issue only the minimum permissions an agent needs for the current task or session.
- Extend DLP policy to unsanctioned AI usage Treat browser extensions, personal copilots and unapproved assistants as data egress channels and monitor them with the same governance expectations as approved tools.
Bottom line: DLP breaks down first when sensitive data is unclassified, because policy cannot govern what the programme has not discovered.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:42 pm
Discovery is now a security control, not a hygiene task. DLP fails early when teams do not know what data exists or where it lives, because every downstream policy assumes that map already exists. In a cloud and AI environment, unclassified data is functionally ungoverned data, even if the tooling is deployed. The practitioner conclusion is simple: classification quality determines whether DLP is operating as control or theatre.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should teams do first when DLP keeps missing sensitive data?
A: Teams should first verify what data they are trying to protect, then map where it is created, stored, moved and copied. Discovery and classification should identify the sensitive repositories, file types, labels and channels that DLP can inspect, because missed data usually comes from blind spots, unsupported formats or unmonitored exfiltration paths. From there, tune policies, test in alert mode and cover endpoints, email, cloud storage and web traffic.
👉 Read our full editorial: AI agents expose the limits of DLP when data is unclassified