Example: Creating a Suppression Rule for VPC Flow Logs

Role Availability Read-Only Investigator Analyst Manager

In this example, we are going to create a suppression rule to suppress VPC Flow Logs events Any traffic or data exchange detected by LevelBlue products through a sensor or external devices such as a firewall.. This way you will avoid noise in your list of events.

To create a VPC Flow Logs Suppression Rule

  1. Go to Activity > Events.
  2. Enter VPC in the search field.
  3. Click the icon.
  4. Select one of the events.
  5. Select Create Rule > Create Suppression Rule.
  6. These property values are selected:

    Create a VPC Flow Logs Suppression Rule

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

    Note: See Operators in the Orchestration Rules for more information.

  8. In the Occurrences text box, enter the number of event occurrences that you want to produce a match on the conditional expression to trigger the rule.

    You can enter the number of occurrences or use the arrows to scroll the value up or down. You can enter a number between 1 and 100.

  9. Click Next.

    Rules Verifications Dialog Box

    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, for example Suppress VPC Flow Logs.
  11. (Optional.) Enter a description for identifying this rule.
  12. In the Length text box, specify the timespan that you want to use to identify a match for multiple occurrences. Enter the number in the text box, and then use the drop-down menu to select 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.

  13. Click Save.
  14. The suppression rule has been created. You can see it from Settings > Rules. See Suppression Rules from the Orchestration Rules Page for more information.

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