Configuring a DLP Gateway in Bridge Mode

Best Practice and Limitations

Best Practice - When you set up a dedicated DLP Gateway, Check Point recommends that you configure the DLP Gateway as a bridge, so that the DLP Gateway is transparent to network routing.

You can configure DLP in bridge modeClosed Security Gateway or Virtual System that works as a Layer 2 bridge device for easy deployment in an existing topology., with the requirements described in this section for routing, IP address, and VLAN trunks.

Note the current limitations:

  • In an environment with more than one bridge interface, the DLP Gateway must not see the same traffic twice on the different interfaces. The traffic must not run from one bridged segment to another.

  • Inter-bridge routing is not supported. This includes inter-VLAN routing.

  • If the bridge interface is connected to a VLAN trunk, all VLANs are scanned by DLP. You cannot keep out specific VLANs.

  • Routing from the bridge interface to a Layer3 interface, and from Layer3 interface to the bridge, is not supported. Traffic on the bridge interface must run through the bridge or be designated to the DLP Gateway.

  • From R76, the DLP Gateway in bridge mode can be in a clusterClosed Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing., in High Availability mode. But the Ask User action and the UserCheck Agent are not supported.

  • If the DLP Gateway in bridge mode is behind a cluster, the cluster must be in High Availability mode.

  • Bond High Availability (HA) or Bond Load Sharing (LS) (including Link Aggregation) are not supported in combination with bridge interfaces.