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.

Authentication and access management<br />

Quota management 5<br />

Authorized Override<br />

You can configure session time for a session that allows authorized overriding. When this session time<br />

has elapsed, a user request is blocked and a block message is displayed. The message also asks for<br />

submission of a user name and password to start a new session.<br />

These credentials must be those of an authorized user. For example, in a classroom situation, a user<br />

who gets blocked after termination of an authorized override session could be a student, while the<br />

teacher is the authorized user.<br />

The block message also provides an option to specify the time length of the authorized override session<br />

for the user who was blocked.<br />

Note: The time length that is configured for this user should not exceed the time length configured for all<br />

other users as part of the module settings for authorized overriding.<br />

You can configure authorized overriding in relation to the parameters used in the Authorized Override<br />

library rule set, such as URL categories, IP addresses, and user names. You can also create rules of<br />

your own using other parameters.<br />

Blocking Sessions<br />

By configuring blocking sessions you can block requests sent by a user for a configured period of time<br />

after the user has sent a request that is blocked according to a configured rule, for example, a request<br />

for a URL that falls into a category on a list used by a blocking rule.<br />

This is a means of enforcing a web security policy that handles unwanted access to web objects with<br />

more strictness.<br />

You can configure blocking sessions in relation to the parameters that are used in the Blocking Sessions<br />

library rule set. You can also create rules of your own using other parameters.<br />

Combining quota management functions<br />

Using a particular quota management function to restrict web usage has no impact on the use of other<br />

quota management functions. For example, time quotas and volume quotas are configured and<br />

implemented separately on the appliance.<br />

You can, however, combine these functions in meaningful ways. For example, you can impose coaching<br />

on users’ access to some URL categories, while requesting authorized override credentials for other<br />

categories. For still another group of categories you could block users who attempt to access them over<br />

a configured period of time.<br />

Rules for quota management<br />

Rules for quota management are contained in several rule sets. Each rule set deals with a particular<br />

quota management function, such as time quota, volume quota, coaching, and others. This section<br />

describes the rules in these rule sets and explains how to configure them to implement quota<br />

management.<br />

Time Quota (rule set)<br />

This section describes the rules in a library rule set for implementing time quotas.<br />

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

Library rule set — Time Quota<br />

Criteria — SSL.Client.Context.IsApplied equals true OR<br />

Command.Name does not equal “CONNECT”<br />

Cycle — Requests (and IM)<br />

The rule set criteria specify that the rule set applies to SSL-secured communication, as well as to other<br />

communication, where the CONNECT command is not used at the beginning.<br />

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

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

Saved successfully!

Ooh no, something went wrong!