You can create suppression rules from the EventsAny traffic or data exchange detected by AlienVault products through a Sensor, or through external devices such as a firewall. page to prevent some events from flooding your system.
USM Anywhere saves the events that match a suppression rule, but does not correlate these suppressed events. By default, USM Anywhere hides these suppressed events. If you want to see these events, click Suppressed in the Search & Filters area. The suppressed events will be displayed in the table along with all events. If you want to display just the suppressed events, see To only display the suppressed events.
You can create your own rules from the Suppression Rules page or from the Events details page, which is the easiest way to configure the matching conditions.
To create a Suppression Rule from the Events page
- Navigate to ACTIVITY > EVENTS.
- Search the events which you want to include in the suppression rule. See Searching Events for further information.
- Click on the event to suppress.
- Click Create Rule > Create Suppression Rule.
- Type a name for the rule.
- You have already suggested property values to create a matching condition. If you want to add new property values, click Add Condition.
- You can click Add Group to group your conditions.
(Optional) To include a multiple occurrence parameter, click the More... link.
These options function together to specify the number of occurrences within a time period that will produce a match for the rule. For example, you can define a rule to trigger an alarmAlarms provide notification of an event or sequence of events that require attention or investigation. for an unauthorized accessAn incident-type categorization that may be a precursor to other actions or stages of an attack. attempt when a failed SSH Program to securely log into another computer over a network, to execute commands in a remote machine, and to move files from one machine to another through SCP.loginLog in (verb): Process in which an individual gains access to a computer system after providing sufficient credentials to authenticate their unique identity. Login (noun): User credentials, typically a username and matching password. occurs three times within a five minute window.
- Occurrences — Specify the number of event occurrences that produce a match on the conditional expression to trigger the rule. You can enter the number of occurrences or use the arrow to scroll the value up or down.
Length — Specify the length of the window used to identify a match for multiple occurrences. Enter the number and choose a time unit value of seconds, minutes, or hours.
This duration identifies the amount of time that transpires from the first occurrence to the last occurrence. If the number of occurrences is not met within this period, the rule is not a match.
In this example, the rule will apply when the configured conditions happen three times every five minutes.
- Click Save Rule.
Note: If the field is related to the name of a country, you should use the country code defined by the ISO 3166.
Note: Keep in mind that the Sources or Destinations field needs to match the UUID (Universally Unique Identifier) of the event or alarm. You can use Source Name(s) or Destination Name(s) instead.
Note: See Operators in the Orchestration Rules for further information.
The suppression rule has been created. You can see it from SETTINGS > RULES, see Suppression Rules from the Orchestration Rules page for further information.
- Navigate to ACTIVITY > EVENTS.
- Click the Configure Filters link, which is positioned at the lower-right area of the filters.
- Write in the Search filters field 'Suppress'.
- Select the Suppress Rule Name filter.
- Click the Right Arrow icon ().
- Click Apply.
- Click Suppressed in the Search & Filters area.
- Search the Suppress Rule Name filter and click on the rule.
The selected filter will pass from the available filters to the selected filters.
The dashboard view will reset and the Suppress Rule Name filter will be available.
If there are no rule names displayed it is because
- there are no events suppressed by the rule
- the Suppressed filter is not enabled
See Searching Events for further information about the icons below the filters.
Note: You can save the view for later use. See Views for further information about how to create a configuration view.