--- title: "Web requirements" slug: "web-requirements-1" tags: ["Install and Get Started", "DLPNP – SaaS"] updated: 2026-09-01T09:28:14Z published: 2026-09-01T09:28:14Z canonical: "docs.trellix.com/web-requirements-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Web requirements Trellix DLP Network Prevent – SaaS works with ICAP-compliant web proxies to protect web traffic. To fully integrate an ICAP client with a Trellix DLP Network Prevent appliance, the ICAP client must be able to: - Split requests from responses (REQMOD vs. RESPMOD). For example, in some environments it might be preferable for Trellix DLP Network Prevent – SaaS to process only web requests going to public sites, rather than processing every bit of HTTP traffic on the network. - Add an X-Authenticated-User ICAP request header to provide the Trellix DLP Network Prevent – SaaS appliance with the end user making the request for policy evaluation purposes. - Add X-Client-IP and X-Server-IP request header to provide the Trellix DLP Network Prevent – SaaS appliance with source and destination IP addresses for reporting purposes.