Topic starter
14/08/2026 6:35 pm
TL;DR: AI agents can move data at machine speed, through API calls and model requests that legacy DLP was never built to see, according to Orion. The governance challenge is shifting from reviewing human behaviour to enforcing action-level controls on software that can act hundreds of times per session.
Editorial analysis by NHI Mgmt Group, based on content published by Orion: “DLP for AI Agents: Securing Autonomous Workflows”.
Key questions
Q: How should security teams govern personal data used by AI agents?
A: Security teams should govern agent access as a runtime control problem, not as a one-time permission decision.
Q: Why do AI agents create a bigger data-loss risk than human users alone?
A: AI agents can move data, invoke tools, and act under delegated credentials at machine speed, so the exposure is no longer limited to what a person types.
Q: Where does legacy DLP fail when AI agents move sensitive data?
A: Legacy DLP fails when it assumes a person will move data in a slow, visible way.
Practitioner guidance
- Inventory all sanctioned and unsanctioned AI agents Map coding assistants, workflow bots, browser automations and employee-built scripts on personal API keys before setting policy, because controls cannot protect what the organisation has not found.
- Scope agent permissions to the minimum task set Reduce drive, repository, ticketing and model-access privileges so each agent can only touch the data needed for its current instruction, not the full enterprise surface.
- Enforce per-action runtime policy at the egress point Classify each agent movement by content, context and destination, and block or coach before the data leaves, rather than relying on post-event alert queues.
Bottom line: AI agents change DLP because the protected event is no longer a person copying or emailing data, but software moving information through prompts, APIs and connectors.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/08/2026 6:42 pm
Agentic DLP is becoming a control-plane problem, not a content-filtering problem. Once the actor is software, the question changes from whether a person should send the data to whether the agent should move it at that moment. That shifts governance toward runtime authorization, task scoping and destination awareness. Practitioners should treat AI agent egress as a live policy decision, not a retrospective review.
A few things that frame the scale:
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
- Gartner predicts that more than 40% of agentic AI projects will be cancelled by the end of 2027, citing rising costs, unclear value and insufficient risk controls.
A question worth separating out:
Q: How do organisations keep AI agent adoption under control without blocking it?
A: Use sanctioned agent routes, narrow permissions, and per-action enforcement so the workflow can continue while unsafe movements are stopped or coached. The goal is visibility and bounded autonomy, not blanket prohibition. That balance prevents teams from shifting to personal accounts and shadow automations outside governance.
👉 Read our full editorial: DLP for AI agents changes how enterprises govern data movement