On-premises gateways support integration with third-party Internet Content Adaptation
Protocol (ICAP) servers. The ZTSA on-premises gateway acts as an ICAP client, forwarding
outbound traffic to ICAP servers via REQMOD for DLP scanning and taking action based
on your Internet Access Rules.
NotePredefined DLP rules are available with built-in DLP engines for all gateway types.
Third-Party ICAP servers can only be used for on-premises getaways that are not configured
in ICAP mode.
|
Each ICAP server profile can have up to 20 servers.
Procedure
- On the TrendAI Vision One™ console, go to .
- On the Global Settings tab, click 3rd Party DLP Integration via ICAP protocol.
- Click Add.
- Enter the Profile name.
- You can enter a description of the ICAP profile if you want.
- Enter your ICAP servers:
- Click Add server.
- Enter the Server FQDN/IP address.
- You can enable ICAP over SSL if you want.
- Enter the Port number.
- Enter the Weight of the server.
- Enter the REQMOD path.
- Enter the maximum number of concurrent connections.
- Enter the Timeout.
- Select the Failure Action:
-
Allow (Default)
-
Block
-
- Select the X-Headers to stamp in the ICAP request:
- X-Authenticated-User
- X-Server-IP
- X-Client-IP
- In the Parse the result from the given X-Header in ICAP response field enter response header that the ICAP server returns after scanning content.
