Databricks Omnigent Contextual Policies Prevent AI Agent Data Exfiltration
Databricks details how Omnigent Contextual Policies prevent data exfiltration by AI agents, tackling the "lethal trifecta" vulnerability. This risk arises when agents combine access to private data, exposure to untrusted content, and outbound communication capabilities. Traditional per-action authorization checks fail to detect this sequence, but Omnigent's policies track session state, blocking exfiltration only when the first two conditions are met. The approach allows agents to perform normal tasks without hindrance while safeguarding sensitive information.
- →Addressing the AI Agent "Lethal Trifecta"
- →Why Traditional Authorization Fails Contextual Threats
- →Omnigent's Contextual Policy Mechanism
- →Preventing Data Exfiltration in Support Agents
- →No False Positives for Normal Agent Operations
Notes (6) ›
- Addressing the AI Agent "Lethal Trifecta"
This article details how Omnigent Contextual Policies prevent data exfiltration from AI agents by blocking the "lethal trifecta"—a vulnerability where agents combine access to private data, untrusted input, and outbound communication.
- Why Traditional Authorization Fails Contextual Threats
Standard per-action authorization checks are insufficient because they evaluate individual actions in isolation, failing to detect dangerous sequences of legitimate actions that lead to data exfiltration. The threat lies in the combination, not any single step.
- Omnigent's Contextual Policy Mechanism
Contextual policies track "legs" (private data access, untrusted content ingestion, exfiltration) as session state. When an agent attempts an outbound call after accessing both private data and untrusted content, the policy denies the exfiltration, preventing data leakage.
- Preventing Data Exfiltration in Support Agents
A demonstration shows a support agent, instructed by a prompt-injected customer ticket, attempting to exfiltrate internal revenue figures. The policy intervenes at the outbound email step, blocking the confidential data from leaving.
- No False Positives for Normal Agent Operations
The policy is designed to block only the dangerous combination of actions, not individual tools. It allows agents to perform routine tasks, such as responding to customer queries without sensitive data access, ensuring normal workflow is uninterrupted.
- Human-Defined Policy "Legs" for Security
The classifications for "private data," "untrusted content," and "exfiltration" are explicitly defined by a human in the agent's configuration, not by the agent itself at runtime, to prevent prompt injection from manipulating policy definitions.
https://www.databricks.com/blog/innocent-until-combined-blocking-lethal-trifecta-omnigent-contextual-policies
Related releases
- Databricks SDK for Go v0.172.0 Enhances IAMv2 and Job Cluster Management Databricks Go SDK Releases ·
- Databricks Java SDK v0.146.0 Adds IAM V2 API, Updates Job Cluster Field Databricks Java SDK Releases ·
- Databricks SDK for Python v0.128.0 Adds Account and Workspace IAM V2 API Methods Databricks Python SDK Releases ·
- Amtrak Builds Unified Data Backbone with Databricks for Rail Network Transformation Databricks Blog ·
- Databricks Re-architects Serverless Network Config Delivery for 97.5% Latency Cut Databricks Blog ·
- How a Major Freight Railroad Scaled Pipeline Creation with Databricks Genie Code Databricks Blog ·