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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Monitoring<br />

Logging 8<br />

4 Go to Policy | Rule Sets and insert a logging rule that triggers events when its criteria is matched<br />

into the rule set you created in step 2. The logging rule should triggers the following events if its<br />

criteria is matched:<br />

• A set event that sets parameter values for a log file entry<br />

• A write event that writes the entry into a log file of the log you created<br />

Note: The criteria of the logging rule relates to what you want to log, for example, Antimalware.Infected<br />

equals true as the criteria if you want to log requests for infected objects. Then the set and write events<br />

are triggered if an object is found to be infected.<br />

5 Click Save Changes.<br />

The new log and the log files are stored in a folder of the program files for <strong>McAfee</strong> <strong>Web</strong> <strong>Gateway</strong>. To<br />

view them, navigate with your file manager to the location where these program files are stored and go<br />

to:<br />

/opt/mwg/log/user-defined-logs//<br />

For more information, see Create a log handler, Add a new rule set, Create a sample logging rule,<br />

Configuring log file settings, and Access restrictions.<br />

Use of a property in a logging rule to record blocking key words<br />

When user access to web objects is blocked on the appliance, you can in some situations use the<br />

List.LastMatches property to find out why it was done. This section explains what you need to configure<br />

to use the property in this way.<br />

The implemented rules on your appliance could, for example, include a rule for blocking access to web<br />

objects containing unwanted text, which is identified by the occurrence of “bad” key words. Then you<br />

might be interested in knowing not only that access to an object has been blocked, but also what the<br />

key words were that led to the blocking.<br />

To find out about the key words, you need to configure the following:<br />

• A list of the key words<br />

• A rule that blocks access to web objects with text containing the key words<br />

• An addition to a default logging rule to let it record the key words<br />

List of key words<br />

You can create a list of key words on the Lists tab and fill it with suitable entries.<br />

For more information on how to create this list, see Create a list of key words.<br />

Rule for blocking text with key words<br />

You can create a rule for blocking text with key words, which must be contained in a rule set. You can<br />

create both items on the Rule Sets tab.<br />

The following is an example of what the blocking rule could look like:<br />

Block text with bad words<br />

User-Defined.listOfWords at least one in list BadWords –> Block<br />

The rule uses the User-Defined.ListOfWords property to compare the text contained in the body of<br />

a web object with the words in the BadWords list. The value of the property is a string list of all the<br />

words that are in this text. If one of these words matches a word from the list, access to the web<br />

object with this text is blocked for the user who requested it.<br />

Processing then stops and continues with the next request that is received on the appliance.<br />

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

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

Saved successfully!

Ooh no, something went wrong!