Web Gateway 7.1.5 Product Guide - McAfee

More documents

Recommendations

Info

5 Authentication and access management Quota management • Media types — Users are allowed to download web objects belonging to particular media types only up to a limited volume. Note: These parameters are used by the rules in the library rule set for volume quotas. You can create rules of your own that use other parameters in relation to volume quotas. Information on the volume that users download from the web is stored on the appliance. When the configured volume quota has been exceeded for a user, a request that this user sends is blocked. A message is displayed to the user stating why the request was blocked. Users are identified by the user names they submitted for authentication. If no user name is sent with a request, web usage is recorded and blocked or allowed for the IP address of the client system that the request was sent from. Web downloads can be limited to volume downloaded per day, per week, or per month. Session time You can configure session time for users. This is the time allowed for a single session that a user spends on web usage. Session time is configured separately and handled differently for time quotas, volume quotas, and other quota management functions. • Session time for time quotas — When configuring time quotas, you also need to configure a session time. Whenever session time has elapsed for a user, the amount of time that is configured as session time is deducted from the user’s time quota. As long as the time quota has not been used up, the user can start a new session. When the time quota has elapsed, a request that the user sends is blocked and a block message is displayed. • Session time for volume quotas — When configuring volume quotas, the session time has no impact on the volume quota for a user. You can still configure a session time to inform the user about the amount of time that has been used up for web access. When time has elapsed for a session, the user can start a new session, as long as the configured volume has not been consumed. If you set the session time to zero, no session time is configured and communicated to the user. • Session time for other quota management functions — Session time can be configured for other quota management functions, which include Coaching, Authorized Override, and Blocking Sessions. Accordingly, there can be a coaching, an authorized override, or a blocking session. When session time has elapsed for coaching and authorized overriding, a request that a user sends is blocked. A message is displayed to the user stating why the request was blocked. The user can start a new session unless time quota has also been configured and is used up. The session time that is configured for the blocking session function is the time during which requests sent by a particular user are blocked. When this time has elapsed, requests from the user are again accepted unless time quota has also been configured and is used up. Coaching For coaching the web usage of your users, you configure a coaching session with a particular length of time. When this session time has elapsed for a user, a block message is displayed. The user can then start a new session. You can configure coaching in relation to the parameters used in the Coaching library rule set, such as URL categories, IP addresses, and user names. You can also create rules of your own using other parameters. 148 McAfee Web Gateway 7.1.5 Product Guide
Authentication and access management Quota management 5 Authorized Override You can configure session time for a session that allows authorized overriding. When this session time has elapsed, a user request is blocked and a block message is displayed. The message also asks for submission of a user name and password to start a new session. These credentials must be those of an authorized user. For example, in a classroom situation, a user who gets blocked after termination of an authorized override session could be a student, while the teacher is the authorized user. The block message also provides an option to specify the time length of the authorized override session for the user who was blocked. Note: The time length that is configured for this user should not exceed the time length configured for all other users as part of the module settings for authorized overriding. You can configure authorized overriding in relation to the parameters used in the Authorized Override library rule set, such as URL categories, IP addresses, and user names. You can also create rules of your own using other parameters. Blocking Sessions By configuring blocking sessions you can block requests sent by a user for a configured period of time after the user has sent a request that is blocked according to a configured rule, for example, a request for a URL that falls into a category on a list used by a blocking rule. This is a means of enforcing a web security policy that handles unwanted access to web objects with more strictness. You can configure blocking sessions in relation to the parameters that are used in the Blocking Sessions library rule set. You can also create rules of your own using other parameters. Combining quota management functions Using a particular quota management function to restrict web usage has no impact on the use of other quota management functions. For example, time quotas and volume quotas are configured and implemented separately on the appliance. You can, however, combine these functions in meaningful ways. For example, you can impose coaching on users’ access to some URL categories, while requesting authorized override credentials for other categories. For still another group of categories you could block users who attempt to access them over a configured period of time. Rules for quota management Rules for quota management are contained in several rule sets. Each rule set deals with a particular quota management function, such as time quota, volume quota, coaching, and others. This section describes the rules in these rule sets and explains how to configure them to implement quota management. Time Quota (rule set) This section describes the rules in a library rule set for implementing time quotas. For general information on understanding and handling rules, see Rules and rule sets. Library rule set — Time Quota Criteria — SSL.Client.Context.IsApplied equals true OR Command.Name does not equal “CONNECT” Cycle — Requests (and IM) The rule set criteria specify that the rule set applies to SSL-secured communication, as well as to other communication, where the CONNECT command is not used at the beginning. McAfee Web Gateway 7.1.5 Product Guide 149
Page 1 and 2:
Product Guide McAfee ® version 7.1
Page 3 and 4:
Contents Preface 9 About this guide
Page 5 and 6:
Contents Standard authentication .
Page 7 and 8:
Contents Create an error handler .
Page 9 and 10:
Preface About this guide This Produ
Page 11 and 12:
Table i-2 Acronyms (continued) Acro
Page 13 and 14:
1 Introduction Contents Comprehensi
Page 15 and 16:
Deployment of the McAfee Web Gatewa
Page 17 and 18:
Operating system Introduction Filte
Page 19 and 20:
Introduction Chapters of this guide
Page 21 and 22:
2 Setup and logon Contents Setting
Page 23 and 24:
Setup and logon Setting up the McAf
Page 25 and 26:
Installing the appliance software S
Page 27 and 28:
2 Review the summary that is displa
Page 29 and 30:
Import a license Setup and logon Lo
Page 31 and 32:
Main elements of the user interface
Page 33 and 34:
Setting up system management tools
Page 35 and 36:
Setup and logon Setting up system m
Page 37 and 38:
3 Proxies and caching Contents Inte
Page 39 and 40:
Explicit proxy mode Proxies and cac
Page 41 and 42:
Table 3-1 WCCP Services list (conti
Page 43 and 44:
Proxies and caching Network modes 3
Page 45 and 46:
Transparent bridge mode Proxies and
Page 47 and 48:
Page 49 and 50:
Transparent router mode Proxies and
Page 51 and 52:
Page 53 and 54:
Common proxy settings Proxies and c
Page 55 and 56:
Proxies and caching Common proxy se
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
8 Make sure the following is config
Page 63 and 64:
Proxies and caching Reverse HTTPS p
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Proxies and caching Providing proxy
Page 73 and 74:
Preventing data leaks Proxies and c
Page 75 and 76:
Web caching Proxies and caching Web
Page 77 and 78:
Bypass lists for web caching Proxie
Page 79 and 80:
Verify the enabling of the web cach
Page 81 and 82:
4 Rules and rule sets Contents Filt
Page 83 and 84:
Rules and rule sets Filtering contr
Page 85 and 86:
Modules for delivering filtering in
Page 87 and 88:
Rules on the user interface On the
Page 89 and 90:
Property of a URL Property — URL.
Page 91 and 92:
About rule sets Rules and rule sets
Page 93 and 94:
Rules and rule sets About rule sets
Page 95 and 96:
Table 4-4 Rule set library Rule set
Page 97 and 98: The Rule Sets toolbar provides the
Page 99 and 100: Add name, comment, and enabling Com
Page 101 and 102: Add as many parameters as needed. A
Page 103 and 104: 3 Select Event. The Add Event windo
Page 105 and 106: Adding the action 9 Select Action.
Page 107 and 108: Rules and rule sets Rule configurat
Page 109 and 110: Add a new rule set You can also cre
Page 111 and 112: List maintenance Rules and rule set
Page 113 and 114: Add a list Complete the following p
Page 115 and 116: Action and engine settings Rules an
Page 117 and 118: Access restrictions Rules and rule
Page 119 and 120: 5 Filtering users Authentication an
Page 121 and 122: Authentication and access managemen
Page 127 and 128: Module for authenticating users Aut
Page 131 and 132: LDAP Settings specifying the LDAP m
Page 133 and 134: Novell eDirectory Settings specifyi
Page 135 and 136: Kerberos Settings specifying the Ke
Page 137 and 138: Table 5-8 Certificate Authorities l
Page 147: Authentication and access managemen
Page 165 and 166: Administrator accounts Authenticati
Page 169 and 170: 6 Web filtering Contents Filtering
Page 171 and 172: Virus and malware filtering Web fil
Page 173 and 174: Web filtering Virus and malware fil
Page 177 and 178: Whitelists for virus and malware fi
Page 181 and 182: Module for virus and malware filter
Page 187 and 188: URL filtering Web filtering URL fil
Page 189 and 190: Web filtering URL filtering 6 The B
Page 191 and 192: Modify a filtering rule to block un
Page 193 and 194: Web filtering URL filtering 6 Add a
Page 195 and 196: Module for URL filtering Web filter
Page 197 and 198: Web filtering URL filtering 6 Advan
Page 199 and 200:
Different versions of URL category
Page 201 and 202:
Web filtering Media type filtering
Page 203 and 204:
Web filtering Media type filtering
Page 205 and 206:
Lists for media type filtering Web
Page 207 and 208:
HTML filtering Web filtering HTML f
Page 209 and 210:
Web filtering HTML filtering 6 Embe
Page 211 and 212:
Break; User-Defined.removeOneScript
Page 213 and 214:
Media Type String Blocklist List of
Page 215 and 216:
Global whitelists Web filtering Glo
Page 217 and 218:
Web filtering SSL scanning 6 Handle
Page 219 and 220:
Block untrusted certificate authori
Page 221 and 222:
Web filtering SSL scanning 6 Verify
Page 223 and 224:
Modules for SSL scanning Web filter
Page 225 and 226:
Web filtering SSL scanning 6 SSL Cl
Page 227 and 228:
8 Click OK. The window closes and t
Page 229 and 230:
The rule set contains the following
Page 231 and 232:
Bandwidth throttling Web filtering
Page 233 and 234:
Next-hop proxies Web filtering Supp
Page 235 and 236:
Web filtering Supporting functions
Page 237 and 238:
User messages Web filtering User me
Page 239 and 240:
The following table describes the o
Page 241 and 242:
Table 6-25 Template Editor (continu
Page 243 and 244:
Web filtering User messages 6 Redir
Page 245 and 246:
7 System configuration Contents Con
Page 247 and 248:
System settings System configuratio
Page 249 and 250:
Table 7-4 List of sections on syste
Page 251 and 252:
License system settings System conf
Page 253 and 254:
Network Protection system settings
Page 255 and 256:
System configuration System setting
Page 257 and 258:
Database updates Table 7-13 File Ed
Page 259 and 260:
System configuration Database updat
Page 261 and 262:
Configure central management settin
Page 263 and 264:
System configuration Central manage
Page 265 and 266:
Scheduled job settings This section
Page 267 and 268:
System configuration Central manage
Page 269 and 270:
8 Monitoring Contents Monitoring th
Page 271 and 272:
Monitoring Dashboard 8 Overview of
Page 273 and 274:
Charts and Tables tab Monitoring Da
Page 275 and 276:
Table 8-4 Overview of charts and ta
Page 277 and 278:
Logging Monitoring Logging 8 Applia
Page 279 and 280:
Sample logging rule Monitoring Logg
Page 281 and 282:
13 Configure the following for the
Page 283 and 284:
Monitoring Logging 8 4 Go to Policy
Page 285 and 286:
+ Number.ToString (Block.ID) + “
Page 287 and 288:
Create a rule for setting text as t
Page 289 and 290:
Monitoring Logging 8 • In the Con
Page 291 and 292:
Configuring log file settings Monit
Page 293 and 294:
Monitoring Logging 8 Auto Pushing S
Page 295 and 296:
Log handler rule sets Monitoring Lo
Page 297 and 298:
Performance measurement Monitoring
Page 299 and 300:
Monitoring Performance measurement
Page 301 and 302:
Transferring data to an ePO server
Page 303 and 304:
Event monitoring with SNMP Monitori
Page 305 and 306:
Error handling Table 8-7 Trap Sinks
Page 307 and 308:
Rule sets for error handling Monito
Page 309 and 310:
The rule set contains the following
Page 311 and 312:
Monitoring Error handling 8 Handle
Page 313 and 314:
Monitoring Error handling 8 Block o
Page 315 and 316:
9 Troubleshooting Contents Troubles
Page 317 and 318:
Enable the creation of connection t
Page 319 and 320:
List of actions Appendix: Configura
Page 321 and 322:
Table A-2 List of error IDs (contin
Page 323 and 324:
Table A-3 List of events (continued
Page 325 and 326:
Table A-3 List of events (continued
Page 327 and 328:
List of incident IDs Appendix: Conf
Page 329 and 330:
Table A-4 List of incident IDs (con
Page 331 and 332:
Table A-5 List of properties (conti
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Wildcard expressions Appendix: Conf
Page 369 and 370:
Table A-6 List of important special
Page 371 and 372:
Table A-7 List of important special
Page 373 and 374:
Index A access restrictions 117 act
Page 375 and 376:
I ICAP server, see proxies ICQ, see
Page 377 and 378:
SNMP monitoring 303 SSL scanning Ce
Page 380:
700-3299A00
show all

Web Gateway 7.1.5 Product Guide - McAfee

Create successful ePaper yourself

Delete template?

Save as template?