01.01.2013 Views

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Preventing data leaks<br />

Proxies and caching<br />

Preventing data leaks 3<br />

When you are running the appliance together with a DLP (Data Leakage Prevention) solution that uses<br />

an ICAP server for the filtering process, you can implement a rule set to ensure the smooth flow of data<br />

between the appliance and the ICAP server. This section describes the rule set and the settings that are<br />

implemented with it.<br />

The DLP solution that you can run together with the appliance is named nDLP. Its purpose is to filter<br />

data that users want to upload from your network to the web in order to prevent data leaks. An ICAP<br />

server is used by the solution for the filtering process. The data flow is as follows:<br />

• Data sent from the client systems of your users is forwarded to the appliance.<br />

• The appliance provides an ICAP client that sends REQMOD requests with the user data to the ICAP<br />

server that is part of the DLP solution.<br />

• The requests are filtered on the server by modifying them according to the ICAP protocol and passed<br />

on to the web servers that are the destinations of the requests.<br />

After importing the Data Leakage Prevention rule set from the rule set library, rules are executed on<br />

the appliance to handle the sending of requests to the ICAP server.<br />

According to these rules, a request is not forwarded if:<br />

• The body of the request contains no data and the request does not include URL parameters.<br />

• The body of the request exceeds a given size (default: 50 MB).<br />

Together with the rule set, settings are imported that you need to configure. These include a list of the<br />

ICAP servers that the appliance can forward requests to. You can also configure the ICAP client on the<br />

appliance not to open more connections for sending requests than a particular ICAP server can handle<br />

at the same time.<br />

For more information, see Import a rule set and Data Leakage Prevention.<br />

Data Leakage Prevention<br />

This section describes the rules in the Data Leakage Prevention library rule set.<br />

For general information on understanding and handling rules, see Rules and rule sets.<br />

Library rule set — Data Leakage Prevention<br />

Criteria — URL.Host does not equal “ ”<br />

Cycles — Requests (and IM) and embedded objects<br />

The rule set criteria specifies that the rule set applies when a host name can be found for a URL that is<br />

sent in a request to the appliance.<br />

The rule set contains the following rules:<br />

Skip requests that do not carry information<br />

Body.Size equals 0 AND ListOfString.IsEmpty(URL.Parameters) equals true –> Stop Rule Set<br />

The rule uses the Body.Size property to check whether a request has a body that is empty. It also<br />

uses the ListOfString.IsEmpty property to check whether a request has URL parameters. If one of<br />

the two parts of this criteria is matched, processing of the rule set stops and the request is not<br />

forwarded to the ICAP server.<br />

<strong>McAfee</strong> <strong>Web</strong> <strong>Gateway</strong> <strong>7.1.5</strong> <strong>Product</strong> <strong>Guide</strong> 73

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!