Cisco Umbrella DLP: What DNS Filtering Misses and the Endpoint SWG That Replaces It

What "Cisco Umbrella DLP" actually means in 2026

When a Cisco rep talks about Umbrella DLP, three different things get bundled into one term. It is worth pulling them apart before any renewal conversation.

The first is DNS-layer category control. Umbrella can block or warn on the resolution of a domain that has been categorized as risky. If a user tries to reach a known data-exfil domain or a flagged consumer file-sharing site, the resolver returns nothing or a block page. That is not DLP. That is reputation-based domain blocking.

The second is the intelligent proxy. For a small subset of risky-but-not-banned domains, Umbrella can backhaul the session to its cloud for SSL inspection. This is the slice of traffic that gets actual content inspection in the Umbrella architecture, and it is intentionally narrow because backhauling everything would punish performance.

The third is Cisco Secure Internet Gateway (SIG), which is a separately licensed cloud proxy bolted onto Umbrella. SIG can do URL filtering, malware scanning, and some level of DLP on the traffic it inspects. The catch is the architecture: SIG is a cloud proxy. Every inspected request hairpins through Cisco's data centers, adds latency, and pays the same tax every legacy cloud SWG charges.

None of these are endpoint DLP. None of them inspect a file at the moment a user clicks upload in a browser. None of them can read what an employee actually typed into ChatGPT.

The four blind spots DNS-based DLP cannot close

1. The URL path inside an allowed domain

DNS sees docs.google.com and stops. It does not see whether the path is a public help article, a corporate Workspace document, or a personal account's confidential design doc. The category check is at the domain level. The risk is at the path level. An endpoint SWG decrypts the session locally, reads the full URL, and can apply policy by path (corporate tenant allowed, personal Drive blocked).

2. TLS-encrypted content

Over 95% of web traffic is HTTPS. DNS sees none of the payload. Umbrella's SIG cloud proxy can inspect a slice of that traffic, but only by backhauling it to Cisco. dope.security's on-device proxy does the break and inspect locally, so every TLS session is visible to policy without leaving the laptop.

3. File uploads and in-app actions

The risky moment is not "user visited Dropbox." It is "user uploaded a 50 MB customer manifest to a personal Dropbox." DNS has no view of that event. Dopamine DLP, our endpoint DLP, intercepts file uploads on the device at the moment of egress. It classifies the file with a zero-retention OpenAI API, returns a human-readable Dopamine Summary of what was detected, and applies one of three modes: Block, Monitor, or Off. The approach is covered by US Patent 12,464,023.

4. AI prompts

This is the gap that closes fastest in real-world buyer conversations. An employee opens ChatGPT and pastes 400 lines of an unreleased financial model into the prompt. The session is HTTPS to an allowed domain. No file moved, because the data was a copy and paste. DNS sees the resolution and steps off. Dopamine DLP inspects the prompt itself, classifies the content, and can block, warn, or log per policy. Cloud Application Control sits on top and restricts logins to your enterprise ChatGPT and Claude tenants only, so employees cannot route around the policy on a personal account. The full three-layer AI governance pattern is covered in what Cisco Umbrella can't see.

"But Cisco SIG has DLP"

It has some. Worth being precise about what it costs and what it gets you.

SIG is a separately licensed cloud proxy. The license is on top of the Umbrella DNS license. The deployment posture is the legacy SWG model: backhaul every inspected request through Cisco's data centers, take the latency hit, take the cost hit, and accept that the inspection is happening somewhere other than where the data is.

For mobile users, the math gets worse. A salesperson on hotel Wi-Fi in Berlin has every inspected request routed to Cisco before reaching the destination. For a real Cisco Umbrella customer that is a venture firm with a distributed partner base, this was the breaking point. Greylock Partners ditched Cisco Umbrella for dope.security and went from first proposal to signed contract in 27 days. The Umbrella SWG component still backhauled. DNS-only could not see HTTPS. The architecture was the wrong shape for the workforce.

If the answer to "DNS isn't enough" is "add a cloud proxy," you are paying twice to recreate the legacy SWG model the industry has spent the last five years moving away from.

What endpoint DLP actually looks like

dope.security puts a lightweight agent on the device, under 100 MB of RAM, on macOS and Windows. The agent does SSL inspection on the device. URL filtering happens on the device. Application control happens on the device. DLP happens on the device. Traffic flies direct to the destination. No Cisco data center in the path. No tunnel. No detour.

What that means for DLP specifically: the inspection happens in the moment a user takes the risky action, on the same device the data is leaving. A file upload to a personal Google Drive triggers the same policy whether the user is in headquarters, in a coffee shop, or on a customer site. The classification is done by a zero-retention OpenAI API, which means the content being inspected is never retained or used for training. The Dopamine Summary explains what was detected in human language, so an admin reviewing a block does not have to puzzle out a regex match.

Three modes: Block, Monitor, Off. Monitor is the right starting position for most teams, because it lets you see the policy fire on real traffic before you decide which patterns to block. Block is the enforcement posture for confirmed-sensitive categories like customer PII, source code with secrets, PHI, and unreleased earnings figures.

The single-console part is not a marketing line

A Cisco Umbrella shop trying to assemble a DLP story today usually ends up with three or four panes of glass. Umbrella for DNS. SIG for cloud proxy DLP, if licensed. A separate endpoint DLP product for file uploads. A CASB layer for data at rest in M365 and Google Workspace. Each one has its own policy model, its own log format, and its own renewal line.

dope.security puts all of that into one console. dope.SWG handles SSL inspection, URL filtering, and Cloud Application Control on the endpoint. Dopamine DLP covers data in motion (uploads and AI prompts). CASB Neural scans the Microsoft 365 and Google Workspace tenants for sensitive content shared externally and inventories third-party OAuth-connected apps with risk scoring. One agent. One console. One renewal line.

Outreach Health did the migration off a legacy SWG to this stack, secured 99% of devices in a week, and cut web-access-related IT tickets by 70% in the first 90 days. A separate Cisco Umbrella replacement hit 2,000 machines in two days once the team made the call. The deployment story is short because the architecture is simple.

What replacing Cisco Umbrella's DLP gap looks like in practice

The migration is not a forklift. dope.security runs alongside Umbrella for as long as you want. Push the agent through your MDM (Intune, Jamf, Kandji, JumpCloud). Put Dopamine DLP in Monitor mode for the first week so you can see the prompts and uploads users are actually generating. Tune the policy to your real data. Switch to Block on the categories that matter to your compliance regime. Decommission the SIG add-on at the next renewal cycle.

The reason this works is that DLP enforcement does not require the SWG to backhaul. The agent already sees every request on the device. Turning DLP on is a policy change, not a redeployment.

The bottom line

There is no real Cisco Umbrella DLP product because DNS filtering cannot inspect content. The closest Cisco gets is the SIG cloud proxy, which solves the visibility problem by paying the backhaul tax and adding a separate license. An agent-based endpoint SWG with on-device DLP fixes the architecture: inspection happens where the data is, policy fires before the data leaves, and the single console covers the SWG, DLP, CASB, and CAC layers that Cisco Umbrella forces you to license separately.

dope.security is the named replacement. Dopamine DLP, US Patent 12,464,023, ships under the same console as dope.SWG, CASB Neural, and Cloud Application Control. One agent. One renewal line.

Run it on your worst case first. Pick the team most exposed to AI prompts and personal cloud uploads, deploy the agent through your MDM, and put Dopamine DLP in Monitor for a week. The data tells the story before any vendor deck has to. Start a free trial or book a 20-minute demo.