There are cases where the alarms Alarms provide notification of an event or sequence of events that require attention or investigation. in USM Anywhere are false positives A condition that is flagged as a vulnerability or weakness that is not actually a concern. This may be caused by other mitigating conditions (such as additional security technology) or inefficient tuning of detection technology., and you may want to suppress this kind of alarm to prevent those false positives from flooding your system. To suppress an alarm, you need to create a suppression rule. USM Anywhere applies the suppression rule to similar alarms from the current day (up to 10 K alarms) and to future alarms. Therefore, existing alarms are suppressed but kept open, while future alarms are suppressed and closed.
Warning: Orchestration rules only apply to future events and alarms. There is no longer an exception for suppression rules.
Suppression rules using the
Match, case insensitive operators apply to future events and alarms, not to events and alarms received in the current day.
To create a suppression rule from the Alarms page
- Go to Activity > Alarms.
Locate the alarm that you want to include in the suppression rule.
See Searching Alarms for more information.
- Click the alarm that you want to suppress.
- Click Create Rule > Create Event Suppression Rule or Create Rule > Create Alarm Suppression Rule.
- You have already suggested property values to create a matching condition, but if you want to add new property values, click Add Condition.
(Optional.) Click Add Group to group your conditions.
Note: See Operators in the Orchestration Rules for more information.
- Click Next.
- Enter a name for the rule.
- (Optional.) Enter a description for identifying this rule.
Modify these two options:
- 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. You need to enter a number between 1 and 100.
Length: Specify the length of the timespan used to identify a match for multiple occurrences. Enter the number and choose a value of seconds, minutes, or hours.
This duration identifies the amount of time that transpires from the beginning to the end of the occurrence. If the number of occurrences is not met within this period, the rule is not a match.
In this example, the rule applies when the configured conditions happen five times every three hours.
These two 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 alarm Alarms provide notification of an event or sequence of events that require attention or investigation. for an unauthorized access An 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, execute commands in a remote machine, and move files from one machine to another through Secure Copy (SCP). login Log 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.
- Click Save.
Note: If the field is related to the name of a country, you should use the country code defined by the ISO 3166.
Note: The Sources or Destinations field needs to match the universally unique identifier (UUID) of the event or alarm. You can use the Source Name or Destination Name field instead.
Important: Instead of using the equals and equals, case insensitive operators for array fields, AT&T Cybersecurity recommends the use of the in or contains operators.
Note: If you need to add a property value that maps with a property key, you need to know the mapping of the field. See Determining the Mapping of a Field for more information.
Note: The current rule box shows you the syntax of your rule, and the rule verification box reviews that syntax before saving the rule.
Important: A dialog box opens if there are warning messages. Click Cancel to review the warning messages, or click Accept to continue creating the rule.
The created rule displays in the list of rules. You can see it from Settings > Rules > Orchestration Rules. See Orchestration Rules for more information.
Important: It takes a few minutes for an orchestration rule to become active.
Suppressed alarms remain in the system but are hidden in the web user interface (UI) by default. If you want to see these alarms, click Suppressed in the Search & Filters area. The table displays suppressed alarms along with the other alarms. Use the following instructions if you want to display just the suppressed alarms.
To only display the suppressed alarms
- Go to Activity >
- In the Search & Filters area, click Not Suppressed to remove the Suppressed: False filter, and then click Suppressed to add the Suppressed: True filter.
- Click Closed to include the closed alarms.
- In the upper-left corner of the page, click the Configure Filters link to see
alarmssuppressed by a certain rule.
- In the Search filters field, enter Suppress.
- Select the Suppress Rule Name filter.
- Click the icon to pass the selected filter from the available filters to the selected ones.
The page reloads, and the Suppress Rule Name filter is added at the lower-left corner.
- Search the Suppress Rule Name filter and click the rule.
If no rule name displays, it is because the rules are not suppressing the
See Searching Alarms for more information about the icons below the filters.
Note: You can save the view for later use. See Alarms Views for more information about how to create a configuration view.
To show triggered
- Go to Settings > Rules
> Orchestration Rulesto open the All Orchestration Rules page.
- In the
Create an Alarmrow, click the icon.