Symantecâ¢ Security Gateways Reference Guide - Sawmill

More documents

Recommendations

Info

228 Log messagesWarning messages (300-399)390 - Intrusion Event detectedDescription: An intrusion event is detected and all suspicious packets from the rogue host are dropped. The log messageprovides information on the type of intrusion event and includes parameters that elaborate on the event.One of these parameters is a hyperlink that provides more information on the event. The parameters arelisted below:Policy TagVendorClassFamilyA string identifying the type of event.This is currently Symantec.Currently all trackable events are of one sensor class “sniffer.”The family to which the event belongs.The Legal Values are listed below:“integrity” Indicates a protocol anomaly event.“availability”“notice”Context dataContext descriptionFlow CookieIP ProtocolLevelReliabilityPayloadPayload offsetStart timeEnd timeSource IPSource PortDestination IPDestination PortPacketInterfaceSource MACDestination MACVLAN IDOutcomeIndicates a counter alert event.Indicates a trackable event.Context specific data about the connection event.Textual description of the data, a given state machine adds to the context data buffer.A string that pseudo uniquely identifies the network flow where the event occurs.This is a conglomerate of the protocol, IPs and ports on both ends of the connection.The transport layer protocol on which the event was detected.A number between 0 and 255, which represents how severe the event is.A number between 0 and 255, which represents how reliable the event is.The exact snippet of data that generated the event. This may be empty for somealerts.The number of bytes into the payload data when the alerting pattern starts. Thisvalue is zero-indexed and is left/right inclusive.The starting time of the event.The end time of the event.The source IP address of the attack. This is also used when blacklist notifications areconfigured.The level four network of the source of the attack traffic.The destination IP address of the attack.The level four network of the destination of the attack traffic.The whole or partial IP packet triggering the event.The string identifying the device, on which the packet was captured.The source Ethernet address of the offending packet.The destination Ethernet address of the offending packet.The virtual local area network (VLAN) ID from the Ethernet header of the offendingpacket.Currently set to unknown
Log messagesError messages (400-499)229392 - A infection has been foundDescription: A virus has been detected, and the details are logged by the antivirus engine. The parameters provideinformation on the virus and the preventive action.392 - Virus infected file was partially transferred and should be deletedDescription: A virus was found in a file during an FTP or HTTP session. Because comforting was turned on, a portion ofthe file was created before the virus was detected. It should be deleted.Error messages (400-499)Log messages in the range 400-499 are issued when normal security gateway operation cannot completesuccessfully. The security of your gateway is still ensured, but you should attempt to correct the error assoon as possible.400 - Invalid adapterDescription: This occurs only on the Symantec Client VPN client because of configuration issues.401 - Description: If this message is from gwcontrol, this indicates an error response from a daemon when gwcontrol sent akill command.401 - Accelerator does not support this AH algorithmDescription: The hardware accelerator does not support authentication header (AH) authentication.401 - Accelerator does not support this ESP algorithmDescription: The hardware accelerator does not support the IPsec algorithm. If this happens more than once, tryrunning the hardware accelerator diagnostic program.401 - Accept failed on portDescription: A socket API accept() call failed in nntpd. The system may have run out of resources.401 - ACK for wrong blacklist packetDescription: The Notify daemon received an invalid protocol while communicating with the blacklist daemon. If thecondition persists, restart the blacklist daemon.401 - Allocation failed (concurrent server)Description: Memory allocation failed. The connection cannot be handled.401 - Allocation failed (connection I/O)Description: Failed to connect to a content scanning server (CSS) or a news server. This is an internal resource allocationissue. Try decreasing the load.
Page 1 and 2:
Symantec Security GatewaysReference
Page 3:
Licensing and registrationContactin
Page 6 and 7:
6 ContentsMail server record ......
Page 8 and 9:
8 ContentsChapter 9Chapter 10Append
Page 10 and 11:
10 Contents
Page 12 and 13:
12 Introducing Symantec security ga
Page 14 and 15:
14 Introducing Symantec security ga
Page 16 and 17:
16 Network security overviewSecurit
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
24 Network security overviewManagem
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
32 Security gateway fundamentalsRou
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
38 Security gateway fundamentalsDom
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
44 Understanding accessNetwork prot
Page 46 and 47:
46 Understanding accessNetwork prot
Page 48 and 49:
48 Understanding accessProxiesProxi
Page 50 and 51:
50 Understanding accessProxiesExamp
Page 52 and 53:
52 Understanding accessProxiesThe D
Page 54 and 55:
54 Understanding accessProxiesThe H
Page 56 and 57:
56 Understanding accessProxiesThe N
Page 58 and 59:
58 Understanding accessProxiesThe S
Page 60 and 61:
60 Understanding accessProxiesTable
Page 62 and 63:
62 Understanding accessService grou
Page 64 and 65:
64 Understanding accessRulesTable 4
Page 66 and 67:
66 Understanding accessRulesWhen a
Page 68 and 69:
68 Controlling service accessFilter
Page 70 and 71:
70 Controlling service accessFilter
Page 72 and 73:
72 Controlling service accessConten
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
78 Controlling user accessAuthentic
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
86 Controlling user accessTime Peri
Page 88 and 89:
88 Understanding VPN tunnelsTunnels
Page 90 and 91:
90 Understanding VPN tunnelsTunnels
Page 92 and 93:
92 Understanding VPN tunnelsIPsec s
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
100 Understanding VPN tunnelsGlobal
Page 102 and 103:
102 Monitoring security gateway tra
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
114 Preventing attacksAntivirus (ap
Page 116 and 117:
116 Preventing attacksIntrusion det
Page 118 and 119:
118 Preventing attacksLogical netwo
Page 120 and 121:
120 Preventing attacksAddress trans
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
126 Preventing attacksAnti-spam mea
Page 128 and 129:
128 Ensuring availabilitySymantec
Page 130 and 131:
130 Ensuring availabilityStateful f
Page 132 and 133:
132 Ensuring availabilityCluster ad
Page 134 and 135:
134 Log messagesInformational messa
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
158 Log messagesNotice messages (20
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
176 Log messagesWarning messages (3
Page 178 and 179: 178 Log messagesWarning messages (3
Page 230 and 231: 230 Log messagesError messages (400
Page 256 and 257: 256 Log messagesAlert messages (500
Page 258 and 259: 258 Log messagesAlert messages (500
Page 260 and 261: 260 Log messagesCritical messages (
Page 270 and 271: 270 Log messagesEmergency messages
Page 272 and 273: 272 Log messagesEmergency messages
Page 274 and 275: 274 IDS eventsAbout IDS/IPS events
Page 276 and 277: 276 IDS eventsAbout IDS/IPS events
Page 278 and 279:
278 IDS eventsAbout IDS/IPS events
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
296 IDS eventsDenial-of-ServiceTabl
Page 298 and 299:
298 IDS eventsDenial-of-ServiceResp
Page 300 and 301:
300 IDS eventsDenial-of-ServiceMalf
Page 302 and 303:
302 IDS eventsIntrusion attemptsUnk
Page 304 and 305:
304 IDS eventsIntrusion attemptsCod
Page 306 and 307:
306 IDS eventsIntrusion attemptsDNS
Page 308 and 309:
308 IDS eventsIntrusion attemptsAff
Page 310 and 311:
Page 312 and 313:
312 IDS eventsIntrusion attemptsFTP
Page 314 and 315:
314 IDS eventsIntrusion attemptsHTT
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
320 IDS eventsIntrusion attemptsIMA
Page 322 and 323:
322 IDS eventsIntrusion attemptsIRC
Page 324 and 325:
324 IDS eventsIntrusion attemptsIRC
Page 326 and 327:
Page 328 and 329:
328 IDS eventsIntrusion attemptsNim
Page 330 and 331:
330 IDS eventsIntrusion attemptsNim
Page 332 and 333:
332 IDS eventsIntrusion attemptsOSP
Page 334 and 335:
334 IDS eventsIntrusion attemptsRlo
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
342 IDS eventsIntrusion attemptsSta
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
352 IDS eventsIntrusion attemptsWAR
Page 354 and 355:
354 IDS eventsProbesSensor Record F
Page 356 and 357:
356 IDS eventsProbesAffected:No spe
Page 358 and 359:
358 IDS eventsSignaturesSMTP Probin
Page 360 and 361:
360 IDS eventsSignaturesHTTP IIS IS
Page 362 and 363:
362 IDS eventsSignaturesAffected: A
Page 364 and 365:
364 IDS eventsSuspicious activitySu
Page 366 and 367:
366 IDS eventsSuspicious activityBG
Page 368 and 369:
368 IDS eventsSuspicious activityBG
Page 370 and 371:
370 IDS eventsSuspicious activityDN
Page 372 and 373:
372 IDS eventsSuspicious activityFT
Page 374 and 375:
374 IDS eventsSuspicious activityAf
Page 376 and 377:
Page 378 and 379:
378 IDS eventsSuspicious activityHT
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
392 IDS eventsSuspicious activityId
Page 394 and 395:
394 IDS eventsSuspicious activityIM
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
404 IDS eventsSuspicious activityMa
Page 406 and 407:
Page 408 and 409:
Page 410 and 411:
Page 412 and 413:
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 432 and 433:
Page 434 and 435:
Page 436 and 437:
Page 438 and 439:
Page 440 and 441:
Page 442 and 443:
442 IDS eventsSuspicious activityNN
Page 444 and 445:
444 IDS eventsSuspicious activityOS
Page 446 and 447:
446 IDS eventsSuspicious activityOS
Page 448 and 449:
448 IDS eventsSuspicious activityPO
Page 450 and 451:
450 IDS eventsSuspicious activityRl
Page 452 and 453:
452 IDS eventsSuspicious activityRP
Page 454 and 455:
454 IDS eventsSuspicious activityRe
Page 456 and 457:
Page 458 and 459:
458 IDS eventsSuspicious activitySM
Page 460 and 461:
460 IDS eventsSuspicious activitySN
Page 462 and 463:
462 IDS eventsSuspicious activitySO
Page 464 and 465:
Page 466 and 467:
Page 468 and 469:
Page 470 and 471:
Page 472 and 473:
Page 474 and 475:
Page 476 and 477:
Page 478 and 479:
Page 480 and 481:
Page 482 and 483:
Page 484 and 485:
Page 486 and 487:
Page 488 and 489:
Page 490 and 491:
Page 492 and 493:
Page 494 and 495:
Page 496 and 497:
Page 498 and 499:
Page 500 and 501:
Page 502 and 503:
Page 504 and 505:
Page 506 and 507:
Page 508 and 509:
508 IDS eventsSuspicious activity
Page 510 and 511:
510 IndexIP address spoofing 21Man-
Page 512 and 513:
512 IndexHH.323alias report 105prox
Page 514 and 515:
514 IndexRTSP 57service parameters
Page 516:
516 Index
show all

Symantecâ¢ Security Gateways Reference Guide - Sawmill

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?

Symantecâ¢ Security Gateways Reference Guide - Sawmill