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.

4<br />

Rules and rule sets<br />

Rule configuration<br />

Property and Criteria<br />

The property used in the criteria of the rule is URL. Its meaning can be paraphrased as “being a URL”.<br />

If a requested web object is a URL, then the rule is processed to see if it is on a particular whitelist.<br />

The whitelist is specified in the rule criteria as Global Whitelist. For looking up whether a given URL is<br />

on it, no special module is needed. Therefore the criteria includes no settings for a module.<br />

Action<br />

If the criteria of the rule matches, the rule applies and the Stop Cycle action is executed, with the<br />

impact that is the purpose of the rule. All measures that might prevent users from accessing the URL<br />

are avoided.<br />

The Stop Cycle action stops the request cycle when a request for access to the URL has been received.<br />

Since the rule set of the rule is processed in all three cycles of the filtering process, the Stop Cycle<br />

action can also stop the response or the embedded object cycle if a whitelisted URL is involved in these.<br />

The Stop Cycle action does not affect a user in the way that a blocking action would do. If the action<br />

and its rule work as intended, the user is allowed to access the requested URL. No message to the user<br />

is therefore needed, so the action of this rule has no settings to specify such a message.<br />

Process flow<br />

If processing the rule leads to the result that a URL is on the specified whitelist, the current cycle of the<br />

filtering process stops, according to what the rule says. Other cycles of the process can go on. For<br />

example, if an embedded object was sent with the request, the embedded object cycle could be started<br />

to filter this object.<br />

If the request cycle is stopped after the whitelisted URL has been sent, the request is passed on the<br />

appropriate web server. The appliance then waits for a response from this server, and if this is<br />

received, the response cycle of the filtering process is started to process this reponse.<br />

Block URLs whose category is in Category BlockList (Sample rule)<br />

This rule can be included in a rule set for URL filtering.<br />

Rule<br />

Name<br />

Block URLs whose category is in Category BlockList<br />

Criteria Action<br />

URL.Categories at least on in list Category Blacklist –> Block<br />

In plain text, the rule could be rendered as follows:<br />

If the category of a URL is on a particular blocking list, block access to this URL.<br />

Purpose of the rule<br />

This rule is for blocking URLs not individually, but per category. All URLs that are related to, for<br />

example, drugs or online shopping are blocked. To achieve this, URL categories are entered on a<br />

blocking list.<br />

If a requested URL falls under a category that is on the list, the rule stops processing completely. The<br />

request is not passed on to the appropriate web server and the user who requested the URL cannot<br />

access it. In this sense, the URL is blocked.<br />

Property and criteria<br />

The property used in this rule is URL.Categories. Its meaning could be paraphrased as “belonging to a<br />

URL category”. If a requested web object is a URL, it is checked whether its categories are on the<br />

specified blocking list. If the URL belongs to more than one category, only one of them on the list is<br />

sufficient to trigger the blocking, as the rule says it: at least one in list.<br />

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

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

Saved successfully!

Ooh no, something went wrong!