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.

Logging<br />

Monitoring<br />

Logging 8<br />

Appliance behavior can be recorded in log files. This section describes the available log file types,<br />

explains their handling, and gives an example of configuring a log file to record found viruses.<br />

Log file types<br />

There are several types of log files on the appliance. They differ in the type of data that is recorded and<br />

in the way the recording is done.<br />

Log files that record the same kind of data are stored in a folder, which is called a log.<br />

System log files<br />

Some log files are maintained by the appliance system, which includes the operating system and<br />

several system-related services. For these log files, data is recorded by system functions. You can view<br />

these files on the user interface, but not edit or delete them.<br />

Note: When system log files are unreadable, they are not shown on the user interface.<br />

The files are also rotated in regular intervals by the system. There is no option for configuring this<br />

rotation.<br />

Module log files<br />

Another type of log file is maintained by particular modules of the appliance, such as the proxy or<br />

anti-malware module. Data for these log files is recorded by module functions. You can view these files<br />

on the user interface, but not edit or delete them.<br />

Rotation, deletion, and pushing of these files is handled by the Log File Manager, which you can<br />

configure settings for. The files are stored in subfolders that are located on the appliance under<br />

/opt/mwg/log.<br />

All files in these folders are handled by the Log File Manager, except those that have mwgResInfo as a<br />

part of their names. The folders with the following names are also not handled by the Log File Manager:<br />

cores, feedbacks, tcpdump, migration, system, ruleengine_tracing, connection_tracing,<br />

message_tracing.<br />

Logs for module log files include the following:<br />

• Audit log — Stores log files that record changes to the appliance configuration<br />

• Debug log — Stores log files that record debugging information<br />

• Migration log — Stores log files that record migration activities<br />

• MWG errors logs — Stores log files that record errors occurring in modules of the appliance<br />

There are separate errors logs for the core and coordinator subsystems, the Anti-Malware module,<br />

the user interface, and the system configuration daemon.<br />

• Update log — Stores log files that record updates of modules and files on the appliance<br />

Rule-based log files<br />

There are also log files that record data based on rules. The recording is executed by events that are<br />

triggered when these rules apply. For example, a rule triggers an event when an object that a user<br />

requested is infected by a virus. The triggered event writes an entry with information on the user, the<br />

infected object, date and time of the request, and so on, to the log file.<br />

You can edit the rules for this type of log files in the same way as any other rules.<br />

The following rule-based log files are provided on the appliance by default:<br />

• Access log — Stores log files that record requests and related information, including date and time,<br />

user name, requested object, infection of an object, blocking of an object<br />

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

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

Saved successfully!

Ooh no, something went wrong!