Symantec™ Security Gateways Reference Guide - Sawmill

IDS eventsSuspicious activity367BGP Invalid ORIGINATOR_ID LengthBase Event:Details:ReferencesBGP_UPDATE_ORIGINATOR_ID_BAD_LENGTHThe BGP UPDATE message contained an invalid ORIGINATOR_ID length. This violation of thestandard could indicate an attempt to compromise the protocol.BGP SpecificationsBGP Invalid Path Attribute LengthBase Event:Details:ReferencesBGP_PATH_ATTRIBUTE_BAD_LENGTHThe BGP UPDATE message contained an invalid path attribute length. This violation of thestandard could indicate an attempt to compromise the protocol.BGP SpecificationsBGP Invalid PATHSEG LengthBase Event:Details:ReferencesBGP_UPDATE_ASPATH_BAD_PATHSEGLENThe BGP UPDATE message contained an invalid PATHSEG length in the ASPATH path attribute.This violation of the standard could indicate an attempt to compromise the protocol.BGP SpecificationsBGP Invalid PATHSEGTYPEBase Event:Details:ReferencesBGP_UPDATE_ASPATH_BAD_PATHSEGTYPEThe BGP UPDATE message contained an invalid PATHSEGTYPE in the ASPATH path attribute.This violation of the standard could indicate an attempt to compromise the protocol.BGP SpecificationsBGP Invalid ROUTE REFRESH Message LengthBase Event:Details:ReferencesBGP_BAD_ROUTE_REFRESH_LENGTHThe BGP message length was outside the limitations specified in the RFC. This violation of thestandard could indicate an attempt to compromise the protocol.BGP SpecificationsBGP Invalid Unknown Message TypeBase Event:Details:ReferencesBGP_UNKNOWN_MSG_TYPEThe BGP message type falls outside the possible range of values specified by the RFC. Thisviolation of the standard could indicate an attempt to compromise the protocol.BGP SpecificationsBGP Invalid UPDATE Message LengthBase Event:Details:ReferencesBGP_BAD_UPDATE_MSG_LENGTHThe BGP UPDATE message length was outside the limitations specified in the RFC. This violationof the standard could indicate an attempt to compromise the protocol.BGP Specifications