Web Gateway 7.1.5 Product Guide - McAfee

More documents

Recommendations

Info

4 Rules and rule sets Filtering controlled by rules A rule applies and specifies that processing must stop completely. A rule applies and specifies that processing must stop for the current rule set. A rule applies and specifies that processing must stop for the current cycle. A rule applies and specifies that processing continues with the next rule. 84 McAfee Web Gateway 7.1.5 Product Guide –> Processing stops. An example of a rule that stops processing completely is a rule with a blocking action. If, for example, a request is blocked because the requested URL is on a blocking list, it is no use to process anything else. No response is going to be received because the request was blocked and not passed on to the appropriate web server. Filtering an embedded object that might have been sent with the request is also not needed because the request is blocked anyway. A message is sent to the user who is affected by the action, for example, to inform this user that the request was blocked and why. Processing begins again when the next request is received. –> Processing stops for this rule set. The rules that follow the stopping rule in the rule set are skipped. An example of a rule that stops the processing of a rule set is a whitelisting rule followed by a blocking rule in the same rule set. When a requested object is found on a whitelist, the request is allowed to pass through without further filtering. Therefore the rule set is not processed any further and the rule that eventually blocks the object is skipped. Processing continues with the next rule set. The next rule set can contain rules that, for example, block a request, although it was allowed to pass through the preceding rule set. –> Processing stops for this cycle. The rules and rule sets that follow the stopping rule in the cycle are skipped. An example of a rule that stops the processing of a cycle is a global whitelisting rule. When a requested object is found on a global whitelist, the request is allowed to pass through to the appropriate web server. To ensure the request is not blocked eventually by any of the following rules and rule sets, the request cycle is not processed any further. Processing continues with the next cycle. –> Processing continues with the next rule. This can be the next rule in the current rule set or the first rule in the next rule set or cycle. An example of a rule that lets the filtering process continue unimpeded is a statistics rule. This rule just counts requests by increasing a counter and does otherwise nothing.
Modules for delivering filtering information Rules and rule sets About rule elements 4 This section explains what special modules do for rules in the filtering process. Before a rule can trigger a particular action, it needs to know what the value of a particular property is. Consider, for example, a rule that blocks virus-infected objects: If “being virus-infected” has the value “true” (for a given object), block this object. The rule needs to know what the value for “being virus-infected” is for a given object. Only then can it block access to the object. How does the rule get this information? It gets the information by calling a special module. This module scans the object and tells the rule what value the property has for the object, for example, if “being virus-infected” is true for it or not. For a virus and malware filtering rule, the special module is the Anti-Malware module (also known as Anti-Malware engine). It can run with different settings and accordingly use different methods for completing its scanning job. For example, it can evaluate only virus signatures or use also proactive methods that are suitable for detecting viruses and other malware for which no signatures are known yet. Although the scanning module is used in the filtering process, it is not a filtering module in a strict sense. The filtering is not done by the module, but by the corresponding rule, based on the delivered information. About rule elements This section explains the elements of a web security rule. The general structure of a rule can be rendered very simply as follows: If a is the case, then do b. For web security rules on the appliance, this simple structure can be filled with a little more detail: If property p has the value x, do y. The property mentioned in the rule is the property of a web object or a user. It is checked, for example, when a user requests access to an object. An example of a rule like this is (in normal language): If “being virus-infected” has the value “true” (for a given object), block this object. or paraphrased even more simply: If an object is virus-infected, block it. Other examples are: If “category that a URL belongs to” has the value “on list x”, block the URL. If “user groups that user is member of” has the value “not on allowed groups list x”, block requests from this user. paraphrased more simply as: If the category of a URL is on a particular list, block the URL. If a user is not a member of an allowed user group, block requests from this user. McAfee Web Gateway 7.1.5 Product Guide 85
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 49 and 50: Transparent router mode Proxies and
Page 53 and 54: Common proxy settings Proxies and c
Page 55 and 56: Proxies and caching Common proxy se
Page 61 and 62: 8 Make sure the following is config
Page 63 and 64: Proxies and caching Reverse HTTPS p
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: Rules and rule sets Filtering contr
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 139 and 140:
Authentication and access managemen
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Administrator accounts Authenticati
Page 167 and 168:
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 175 and 176:
Page 177 and 178:
Whitelists for virus and malware fi
Page 179 and 180:
Page 181 and 182:
Module for virus and malware filter
Page 183 and 184:
Page 185 and 186:
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?