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.

5<br />

Filtering users<br />

Authentication and access management<br />

Contents<br />

Filtering users<br />

Standard authentication<br />

Instant messaging authentication<br />

Cookie authentication<br />

Quota management<br />

Administrator accounts<br />

Users can be “filtered” on the appliance, which means you can allow web access only for those who are<br />

able to authenticate. Administrators need to have accounts with roles and privileges. This gives you<br />

control over who is active in your network.<br />

The sections of this chapter explain the authentication process and how to configure it, for example, by<br />

joining the appliance to a Windows domain to retrieve user information, or by using a database on an<br />

LDAP or RADIUS server, or on another server.<br />

They also explain how to guide users by configuring quotas for their web usage. Furthermore, they tell<br />

you how to set up accounts and roles for administrators and grant them privileges.<br />

Authentication process<br />

This section explains what happens on the appliance during the authentication process. Understanding<br />

this process should help you when you begin to configure authentication according to your own<br />

requirements.<br />

Authentication usually takes place in the request cycle of the filtering process. When users send<br />

requests to the web, for example, to view a web page or download a file, the appliance intercepts these<br />

requests and “considers” whether to block or allow them.<br />

There can be many reasons for not allowing a request, for example, the URL of a requested website<br />

could be on a blocking list. However, authentication usually does not look at the requested object, it<br />

looks at the user. Can information be found in a directory or database to prove that the user can be<br />

trusted? If yes, the user is authenticated.<br />

This is what the authentication rules of the appliance check. A special authentication module retrieves<br />

user information and passes it on to these rules to let them trigger actions, like asking an<br />

unauthenticated user to authenticate or forwarding a request of an authenticated user to further<br />

filtering. The methods the authentication module uses to retrieve the user information can be<br />

configured under its settings.<br />

Looking at the user need not be the only thing that happens in the authentication process. The rules for<br />

this process can also include the checking of web objects. Then authentication can also happen in the<br />

response cycle. For example, a rule might specify that when a web object is sent from the web in<br />

response to a request, a user must authenticate to be allowed access to the object.<br />

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

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

Saved successfully!

Ooh no, something went wrong!