Configuring a DLP Gateway for a Web Proxy

You can use a Web Proxy server or servers for HTTP and HTTPS traffic. If you want the DLP Gateway to scan this traffic, you must configure the DLP Gateway.

Note - You can enable HTTPS InspectionClosed Feature on a Security Gateway that inspects traffic encrypted by the Secure Sockets Layer (SSL) protocol for malware or suspicious patterns. Synonym: SSL Inspection. Acronyms: HTTPSI, HTTPSi. on the gateway to scan HTTPS connections.

To configure DLP for a Web Proxy, use these procedures if the proxy or proxies are between the DLP Gateway and the Internet, or in a DMZ.

Best Practice - If a proxy is in a DMZ, use the DLP Gateway to scan the HTTP traffic between the user network and the proxy in the DMZ.

Configuring DLP for an Internal Web Proxy

If the DLP Gateway is between the Web (HTTP) proxy server or servers and the Internet, use these procedures.

Configuring Proxy Settings after Management Upgrade

For a Security Management server that is upgraded from R70 and lower, traffic that passes through a DLP Gateway to a web proxy server contains the gateway's IP as the source address instead of the original client IP address. For new installations and for installations that were upgraded from R71, the original client IP address is used.

If the traffic that contains the gateway's IP as source address reaches another Security Gateway which either logs traffic or enforces access based on identity, the source IP address does not represent the user's IP address.