You can create suppression rules from the Events Any traffic or data exchange detected by AT&T Cybersecurity products through a sensor or 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 table displays suppressed events along with all events. See To only display the suppressed events if you want to display just the suppressed events.

You can create your own rules from the Suppression Rules page or the Events details page, which is the easiest way to configure the matching conditions.

To create a Suppression Rule from the Events page

1. Go to Activity > Events.

2. Search the events which you want to include in the suppression rule.

   See Searching Events for more information.

3. Click the event to suppress.
4. Select Create Rule > Create Suppression Rule.

5. Select a Boolean operator.

   The options are AND, OR, AND NOT, and OR NOT.

6. Select a packet type in the Match drop-down list.

   

   • Logs: Use this packet type for event-based rules.
   • Configuration Issues: Use this packet type for configuration issues-based rules1 This packet type refers to configuration issues that are used to identify incorrect uses of certain features. For example, the app for AWS assesses your configuration of AWS to identify insecure use of the AWS security features..
   • Vulnerabilities: Use this packet type for vulnerabilities-based rules.
   • Alarms: Use this packet type for console user alarms-based rules.
7. You have already suggested property values to create a matching condition. If you want to add new property values, click Add Condition.

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.

8. (Optional.) Click Add Group to group your conditions.

   Note: See Operators in the Orchestration Rules 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.

9. Click Next.



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.

10. Enter a name for the rule.
11. (Optional.) Enter a description for identifying this rule.

12. 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.

13. Click Save.

    The created rule displays in the list of rules. You can see it from Settings > Rules. See Orchestration Rules for more information.

Important: It takes a few minutes for an orchestration rule to become active.

To only display the suppressed events

1. Go to Activity > Events.
2. In the Search & Filters area, click Not Suppressed to remove the Suppressed: False filter, and then click Suppressed to add the Suppressed: True filter.
3. In the upper-left corner of the page, click the Configure Filters link to see events suppressed by a certain rule.
4. In the Search filters field, enter Suppress.
5. Select the Suppress Rule Name filter.
6. Click the icon to pass the selected filter from the available filters to the selected ones.

7. Click Apply.

   The page reloads, and the Suppress Rule Name filter is added at the lower-left corner.

8. Search the Suppress Rule Name filter and click the rule.

If no rule name displays, it is because the rules are not suppressing the events or the Suppressed filter is not enabled

See Searching Events for more information about the icons below the filters.

To show triggered suppressed events

1. Go to Settings > Rules to open the All Orchestration Rules page.
2. In the Event Suppression row, click the icon.

The Events List View page opens. The page includes Rules Name as a filter so that you can see how many events match the selected rule.