Two events generated for the same signature (one as Detected and other as Blocked) on IBM Security sensors
Why do you see two events generated for the same signature with one as Detected and other as Blocked on IBM Security sensors?
This is normal behavior and is due to the way the Protocol Analysis Module (PAM) event coalescer works.
When a signature fires, PAM will include the details of the traffic that caused it to fire in the event data. Certain events, such as scans and sweeps, may delay the collection of this data due to the nature of the traffic. If PAM is still in the process of collecting all of the event details, the event will show as having a "Detected" status. Once the collection of information is complete, the event will show as having a "Blocked" status.
In most cases, the two events are combined before being sent to SiteProtector. However, in situations where there was a delay or timeout while waiting for the rest of the information, users might see both the Detected and Blocked events in the SiteProtector Console. This is not indicative of a problem.
|Security||IBM Security Network Protection||Protocol Analysis Module (PAM)||Platform Independent||Version Independent|
|Security||IBM Security Network Intrusion Prevention System||Protocol Analysis Module (PAM)||Platform Independent||Version Independent|
More support for:
IBM QRadar Network Security
Protocol Analysis Module (PAM)
Software version: Version Independent
Operating system(s): Platform Independent
Reference #: 1515937
Modified date: 04 September 2017
Translate this page: