For "IP Address matching" enVision checks the circuits in the Correlation Rule Logic only when the IP address matching criteria is met. For "Threshold Definitions" Event thresholds can be defined in terms of the following:
A specific number of events are received within a specified time period.
The total number of events received is either greater than or less than either the selected event average or event baseline
The absence of events being received. If you normally receive a specific message and you do not receive one for a user-specified period of time, this constitutes an alert. (This threshold definition is only used for correlation statements.)
If you want to consider every event received for that message as an alert, then no threshold is set.
Each time a threshold is met within the time frame enVision issues 1 alert, and resets the event count for the threshold. For example, depending on how you set up the threshold criteria, if the threshold criteria is met 3 times during an hour, enVision issues 3 alerts.
Related Articles
Error: The system cannot locate the specified RDN 'DC=x, DC=y' in the external identity source 'example. Verify that the d… 9Number of Views Silvertail/RSA WTD: how to extract a single binary from an rpm package (for patching) 12Number of Views Integrate Citrix NetScaler with RSA Authentication Manager 8.x 197Number of Views Entitlement(app-role/group/ent) revocation request with multiple accounts in an application fails with error:"Expected 1 a… 49Number of Views RSA SecurID Authentication Agent 8.1 for PAM Installation and Configuration Guide for AIX (Portuguese) 11Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Artifacts to gather in RSA Identity Governance & Lifecycle RSA Authentication Manager Patch Updates How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle