Network DLP was designed for a perimeter that most traffic no longer crosses, and endpoint DLP was designed for human users on managed laptops, so neither one sees an encrypted upload from a home network, a USB copy and an AI agent calling an API at the same time. This guide compares the two on coverage: what each can inspect, where encryption and protocol changes blind the network layer, which channels exist only on the device, what the agent costs to run, and how each copes with SaaS, generative AI tools and machine-to-machine traffic. It is written for data security, network and endpoint teams deciding whether network DLP still earns its place and how to layer the two. It does not repeat endpoint channel configuration (see the Endpoint DLP Guide), the proxy and API forms of cloud DLP (see Cloud DLP vs Endpoint DLP) or in-browser controls for unmanaged devices (see Browser DLP vs Endpoint DLP).
Key takeaways
- Short answer: endpoint DLP for the device, network DLP for egress points you still own. The agent sees local channels and content before encryption; the network sensor sees every device behind the egress point, including those that cannot run an agent, but only what it can decrypt.
- Encryption is the network layer's ceiling. Network DLP inspects content only where TLS is terminated; certificate pinning, QUIC over UDP 443 and Encrypted Client Hello (RFC 9849, March 2026) all shrink what it sees, and every inspection exemption is a blind spot.
- Off-network users bypass on-premises network DLP entirely. Unless traffic is steered through a cloud proxy, a remote worker's uploads never touch the sensor.
- USB, print, clipboard and RDP are endpoint-only channels. No network control sees a copy to removable media or a paste between applications.
- Machine traffic falls between both. Server workloads, pipelines and AI agents usually have no endpoint agent and often use pinned or mutually authenticated TLS; govern them with egress allow-lists, scoped credentials and API-level logging rather than content inspection alone.
The short comparison
| Dimension | Endpoint DLP | Network DLP |
|---|---|---|
| Where inspection runs | Agent on the operating system | Inline proxy or gateway, mail transfer agent, or passive sensor on a span port or tap |
| Sees content before encryption | Yes, at the file or application level | Only where TLS is decrypted at the inspection point |
| Off-network and remote users | Yes, policy keeps enforcing on the device | No, unless traffic is steered back through the sensor or a cloud proxy |
| Devices without an agent | No: servers, printers, IoT, contractor and personal devices are invisible | Yes, anything behind the egress point |
| Local channels (USB, print, clipboard, Bluetooth, RDP) | Yes | No |
| Non-web protocols (FTP, SMTP, custom TCP) | Partly, through restricted apps and network share rules | Yes where the protocol is parsed and not encrypted |
| User and process context | Strong: user, process, file path, label | Weak: source IP, unless joined to identity from proxy authentication |
| Operational cost | Agent packaging, compatibility testing, performance tuning on every device | Decryption capacity, certificate trust distribution, exemption management |
| Privacy footprint | Whole-device visibility | All decrypted traffic through the sensor, including personal use |
Option profiles: threat model, architecture, failure modes
Endpoint DLP
Threat model: a user, or malware running as that user, moving sensitive content off a managed device: copying to USB (ATT&CK T1052.001 Exfiltration over USB), pasting into another application or site (T1115 Clipboard Data), printing, or uploading through a browser or sync client (T1567.002 Exfiltration to Cloud Storage).
Architecture in words: a kernel or system extension intercepts file and application events, classifies content locally or against cloud policy, and allows, warns, blocks or audits. Microsoft Purview Endpoint DLP, as one documented example, lists auditable and restrictable activities including upload to a restricted cloud service domain or access from an unallowed browser, paste to supported browsers, copy to clipboard, copy to USB removable device, copy to a network share, print, copy or move using an unallowed Bluetooth app and copy or move using RDP (Windows only for RDP).
Failure modes: devices never onboarded; agents disabled or in audit mode forever; unsupported operating systems and Linux developer machines left out; desktop apps that upload over their own protocols not listed as restricted apps; and policy that is out of date on a device that has been offline. Microsoft documents that on Windows an offline device keeps enforcing the policy it already has, but changes are not pushed and events do not appear centrally until it reconnects.
Controls it delivers: data-in-use protection (CSF 2.0 PR.DS-10), media use (NIST SP 800-53 MP-7) and information flow enforcement at the device (AC-4).
Network DLP
Threat model: bulk or automated exfiltration through the egress point: uploads over web protocols (T1071.001 Web Protocols traffic carrying T1567 Exfiltration Over Web Service), transfers over FTP, SMTP or custom protocols (T1048 Exfiltration Over Alternative Protocol), and scheduled transfers from compromised hosts (T1029 Scheduled Transfer). It covers every host behind the egress point, including servers and devices that cannot run an agent.
Architecture in words: three deployment patterns.
- Inline proxy or gateway: a forward proxy or secure web gateway terminates TLS with an organisation-trusted certificate, hands content to a DLP engine, and can block. Many products connect proxy and DLP engine through ICAP (RFC 3507, Informational, April 2003), which defines REQMOD for request modification and RESPMOD for response modification, on default port 1344.
- Mail gateway: the mail transfer agent passes outbound messages and attachments to the DLP engine, which can quarantine, encrypt or reroute. Email remains one of the most effective network DLP channels because the gateway is already in the path.
- Passive sensor: a span port or network tap copies traffic for inspection. It can only alert, and only on traffic it can parse, which in practice means unencrypted protocols.
Failure modes: decryption exemptions that cover the riskiest destinations; remote users who never route through the gateway; QUIC traffic allowed out on UDP 443 and so never seen by a TCP proxy; pinned applications exempted wholesale; and alerts that show an IP address but no user.
Controls it delivers: boundary protection (SP 800-53 SC-7), system monitoring at the network (SI-4), information flow enforcement (AC-4) and network monitoring (CSF 2.0 DE.CM-01). ATT&CK lists M1057 Data Loss Prevention and M1020 SSL/TLS Inspection as related mitigations.
TLS inspection limits: what the network layer cannot see
Network DLP is only as good as its decryption. Each of the following removes content from view, and each grows every year.
| Limit | What happens | Effect on network DLP | Compensating control |
|---|---|---|---|
| Certificate pinning | The application accepts only specific certificates, so the proxy certificate breaks the connection | Pinned apps must be exempted or they fail; exempted traffic is uninspected | Endpoint restricted-app rules; allow-list destinations for pinned apps |
| Mutual TLS | Client presents its own certificate, common for APIs and workloads | Interception breaks client authentication, so traffic is usually bypassed | Egress allow-list by destination and identity; API-side logging |
| QUIC and HTTP/3 | Transport over UDP 443 with encryption built into the protocol | A TCP-only proxy never sees it if UDP 443 is allowed out | Block outbound UDP 443 from managed networks so clients fall back to TCP, or use a proxy that handles it |
| Encrypted Client Hello (RFC 9849) | Server name and other ClientHello fields are encrypted inside an outer ClientHello | Passive sensors and SNI-based policy lose the destination name | Explicit or transparent proxy that terminates TLS; DNS-layer control; endpoint controls |
| Privacy and legal exemptions | Banking, health and personal categories excluded from decryption | Uploads to services in those categories, or miscategorised sites, are not inspected | Narrow category exemptions; review miscategorisation; endpoint coverage |
| Payload encoding and application encryption | Content compressed, encrypted or encoded before upload | Content inspection cannot classify it | Endpoint inspection before the upload; block unknown encrypted archives to unsanctioned destinations |
TLS interception also carries its own risk: the interception point holds a trusted certificate authority key and re-encrypts traffic, so a weak implementation can lower security for every connection through it. CISA has published an alert on the NSA advisory "Managing Risk from Transport Layer Security Inspection", which covers the risks and mitigations of decrypt-and-inspect deployments. Treat the inspection platform as a privileged system and see M1020 SSL/TLS Inspection for the control itself and the HTTP/2, HTTP/3 and QUIC Security Guide for protocol detail.
Channel coverage map
| Channel | ATT&CK | Endpoint DLP | Network DLP |
|---|---|---|---|
| USB and removable media | T1052.001 | Yes | No |
| Clipboard between applications | T1115 | Yes | No |
| Local and network print | None | Yes | Partly, if print traffic is unencrypted and parsed |
| RDP session copy | None | Yes on Windows | No, the session is encrypted |
| Web upload on the corporate network | T1567, T1567.002 | Yes for supported browsers and apps | Yes where decrypted |
| Web upload from home or travel | T1567 | Yes | Only if steered through a cloud proxy |
| Outbound email | T1048 | Partly, through mail client rules | Yes, at the mail gateway |
| FTP, SFTP, custom TCP from servers | T1048, T1029 | No agent on most servers | Plaintext protocols yes; SFTP and TLS no |
| Exfiltration over an existing command channel | T1041 | Indirectly, through process and file monitoring | Metadata only: volume, destination, timing |
For the full endpoint channel list and policy design see the Endpoint DLP Guide; for removable media specifically see the Removable Media and USB Control Guide.
Off-network users and agent overhead
Remote work changed the arithmetic. When most users worked on the corporate network, one gateway covered them all. With users at home, network DLP covers them only if every connection is steered back: full-tunnel VPN (costly and slow for SaaS), or a cloud proxy that the endpoint client or PAC file forces traffic through. At that point the "network" DLP is a cloud service, and its deployment problem looks like the endpoint one: a client on every device. See CASB vs SWG for that architecture.
Agent overhead is real but bounded. Endpoint DLP costs CPU during content scanning, adds file-operation latency, and conflicts with other security agents and developer tooling. Plan for:
- Compatibility rings: pilot with IT, then a cross-section of business roles, then broad rollout, with an exclusion list for build directories and virtual machine images reviewed quarterly.
- Platform gaps: check which activities each operating system supports before promising coverage. Microsoft's documentation, for example, marks some activities as preview or not supported on macOS.
- Tamper protection: alert on agent removal and stale check-ins; a device that stops reporting is a coverage gap.
Where each wins: small organisations with a fully remote workforce and no owned network get little from on-premises network DLP; endpoint plus cloud controls cover them. Large organisations with data centres, plants, labs or regulated networks still need network DLP at those egress points for servers and unmanaged devices.
SaaS and generative AI channels
Most sensitive uploads now go to SaaS and AI tools over TLS. Network DLP can see them only where it decrypts, and even then it sees an HTTP body, often JSON from a web app or a streaming chat request, without the page context the browser has. Endpoint DLP sees pastes and file uploads in supported browsers and can block unallowed browsers, but desktop AI clients need restricted-app rules. The practical split:
- Prompts and pastes on managed devices: endpoint DLP, or browser DLP where the browser is controlled.
- Uploads from any device on owned networks: network or cloud proxy DLP with decryption for the AI category.
- Data already in a SaaS tenant: API-based cloud DLP and posture tooling, not either of these.
See GenAI DLP vs Traditional DLP for prompt-level inspection.
Agent and API traffic: where both fail
AI agents, automation and integrations move data without a person at a keyboard, and both DLP models were built around one.
- Local tool servers: the Model Context Protocol defines two standard transports, stdio and Streamable HTTP. With stdio the client launches the server as a subprocess and exchanges JSON-RPC messages over standard input and output, so a local tool can read files and send them on through its own outbound connection. Network DLP sees only that outbound connection; endpoint DLP sees it only if the process is a restricted app.
- Remote tool servers and model APIs: Streamable HTTP uses HTTP POST and GET to a single MCP endpoint, usually over TLS, from wherever the agent runs, often a cloud workload with no endpoint agent and outside the corporate gateway.
- Service-to-service APIs: pipelines and integrations use API keys, OAuth client credentials or mutual TLS; interception often breaks them, so they are exempted.
Content inspection is the wrong primary control here. Use identity and egress instead: scope each agent and service identity to the data it needs, restrict outbound destinations per workload, log API calls at the data source, and alert on volume and destination anomalies. See the Agent Egress Control and Network Isolation Guide and GenAI DLP vs MCP DLP.
Where identity fits
Network DLP alerts are only actionable when an IP address resolves to a user or workload identity, which requires authenticated proxy sessions or a client that tags traffic. Endpoint DLP inherits the signed-in user, but service accounts and scheduled tasks on the device act under their own identities, so include them in policy scope. For non-human traffic, the owner and permitted destinations of each workload identity are the policy: an agent with read access to a customer database and unrestricted egress is a DLP problem no sensor will fully solve.
Decision guidance and layering
| Situation | Primary control | Add |
|---|---|---|
| Managed laptops, mostly remote | Endpoint DLP | Cloud proxy DLP for web uploads; API cloud DLP for SaaS |
| Office or plant network with unmanaged devices and servers | Network DLP at egress | Endpoint DLP on managed devices; block outbound UDP 443 |
| Regulated email flows | Mail gateway DLP | Endpoint label-based rules |
| Contractors on personal devices | Browser DLP or virtual desktop | Network DLP only if they use your network |
| AI agents and automation in cloud workloads | Scoped identities and egress allow-lists | API-level logging and anomaly detection |
| Developer workstations | Endpoint DLP with tuned exclusions | Secret scanning and egress control for build systems |
Is network DLP obsolete? Not where you own the egress point and it carries traffic from devices you cannot instrument. It is close to obsolete for a fully remote, SaaS-first workforce, where its job moves into cloud proxy DLP. Decide per network segment, not organisation-wide.
Worked scenario
A manufacturer runs on-premises network DLP on its head office proxy. An audit asks whether engineering drawings can leave.
- Map paths: engineers work hybrid; drawings live on a file server and in a SaaS product data system; plant PCs have no agent; an integration service syncs drawings to a supplier portal.
- Find gaps: home uploads bypass the proxy; the supplier sync uses mutual TLS and is exempted; QUIC is allowed out; USB is uncontrolled on engineering laptops.
- Layer: endpoint DLP on engineering laptops for USB, clipboard and uploads, with drawing fingerprints; outbound UDP 443 blocked at sites; network DLP kept for plant networks; the supplier integration's service identity restricted to one destination with transfer volume alerts.
- Measure: coverage per channel and per device class reported monthly, with exemptions listed and owned.
Phased rollout
- Inventory channels and device classes: list every egress path, decryption exemption and device type, and which control covers each.
- Close the cheapest gaps first: block outbound UDP 443 where a TCP proxy is used, review exemption categories, and resolve proxy traffic to identities.
- Endpoint in audit mode: deploy to a pilot ring, collect a full business cycle of events, tune classifiers and exclusions.
- Enforce in steps: warn, then block with override, then block, ring by ring. Keep a documented rollback that returns a policy to audit within minutes.
- Machine traffic: inventory workloads and agents with data access, set egress allow-lists, and enable API logging at the data sources.
- Retire or re-scope network DLP: where segments no longer carry meaningful traffic, move the policy to the cloud proxy and keep network sensors only where devices cannot be instrumented.
Detection and measurement
- Decrypted share: percentage of outbound web bytes inspected after exemptions, per site.
- Agent health: percentage of managed devices with an active, current DLP agent in enforce mode.
- Off-network coverage: share of remote web traffic passing through a DLP-capable proxy or covered by the endpoint agent.
- Exemption count and age: number of decryption and DLP exemptions, each with an owner and review date.
- Machine egress coverage: share of workloads and agents with data access that have an egress allow-list.
- True positive rate: confirmed incidents as a share of DLP alerts, per channel.
Common failure patterns
- Counting network DLP as remote coverage: the head office gateway is reported as protecting users who have not been on site in months.
- Exempting everything that breaks: pinned apps, mutual TLS APIs and whole categories exempted with no owner or review date.
- Leaving QUIC open: browsers use UDP 443 and the TCP proxy sees nothing.
- Endpoint in audit forever: events are collected but nothing is blocked, so USB and clipboard remain open.
- Forgetting servers and agents: no endpoint agent, exempted from inspection, broad data access and open egress.
- Alerts without identity: network alerts show an IP address and cannot be acted on.
Framework mapping
| Framework | Reference | Endpoint DLP | Network DLP |
|---|---|---|---|
| NIST CSF 2.0 | PR.DS-02 Data in transit protected | Supports | Primary |
| NIST CSF 2.0 | PR.DS-10 Data in use protected | Primary | Supports |
| NIST CSF 2.0 | DE.CM-01 Networks monitored | Supports | Primary |
| NIST SP 800-53 Rev. 5 | AC-4 Information Flow Enforcement | Yes | Yes |
| NIST SP 800-53 Rev. 5 | SC-7 Boundary Protection, SI-4 System Monitoring | SI-4 | Both |
| NIST SP 800-53 Rev. 5 | MP-7 Media Use | Primary | No |
| CIS Controls v8.1 | Safeguard 3.13 Deploy a Data Loss Prevention Solution | Yes | Yes |
| ISO/IEC 27001:2022 | A.8.12 Data leakage prevention | Yes | Yes |
| MITRE ATT&CK v20 | M1057 Data Loss Prevention, M1020 SSL/TLS Inspection | M1057 | Both |
Practitioner checklist
- Map every egress channel and device class to the control that covers it, and list the gaps.
- Measure the share of outbound traffic your network DLP actually decrypts.
- Block outbound UDP 443 where your proxy cannot inspect QUIC.
- Give every decryption and DLP exemption an owner and a review date.
- Steer remote web traffic through a DLP-capable proxy or rely on the endpoint agent, and report which.
- Deploy endpoint DLP in rings, audit first, with a tested rollback to audit mode.
- Govern agent and API traffic with scoped identities, egress allow-lists and data-source logging.
- Resolve every network DLP alert to a user or workload identity.
Standards and references
- IETF: RFC 3507 Internet Content Adaptation Protocol (ICAP)
- IETF: TLS Encrypted Client Hello (RFC 9849)
- CISA: NSA Releases Cyber Advisory: Managing Risk from Transport Layer Security Inspection
- NIST: SP 800-53 Rev. 5 Security and Privacy Controls
- NIST: Cybersecurity Framework 2.0
- MITRE ATT&CK: M1057 Data Loss Prevention
- Microsoft Learn: Learn about Endpoint data loss prevention
- Model Context Protocol: Transports specification
Related NHI Mgmt Group resources: Data Loss Prevention (DLP) Guide · Endpoint DLP Guide · Cloud DLP vs Endpoint DLP · Browser DLP vs Endpoint DLP · Insider Data Theft Guide