Suppression rules - Amazon GuardDuty

Suppression rules

A suppression rule is a set of criteria used to filter findings by automatically archiving new findings that match the specified criteria. Suppression rules can be used to filter low-value findings, false positive findings, or threats you do not intend to act on, to make it easier to recognize the security threats with the most impact to your environment.

After you create a suppression rule, new findings that match the criteria defined in the rule are automatically archived as long as the suppression rule is in place. You can use an existing filter to create a suppression rule, or define a new filter for the suppression rule as you create it. You can configure suppression rules to suppress entire finding types, or define more granular filter criteria to suppress only specific instances of a particular finding type. Your suppression rules can be edited at any time.

Suppressed findings are not sent to AWS Security Hub, Amazon S3 or CloudWatch Events, reducing finding noise level if you consume GuardDuty findings via Security Hub or a third-party SIEM, alerting and ticketing applications.

GuardDuty continues to generate findings even when they match your suppression rules, however, those findings are automatically marked as "archived". The archived finding is stored in GuardDuty for 90-days and can be viewed at any time during that period. You can view suppressed findings in the GuardDuty console by selecting Archived from the findings table, or through the GuardDuty API using the ListFindings API with a findingCriteria criterion of service.archived equal to true.

Common use cases for suppression rules

The following are finding types with common use cases for applying suppression rules, select the finding name to learn more about how to apply a suppression rules for that use case.

To create a suppression rule using the console:

The GuardDuty console allows you to easily visualize, create and manage suppression rules.

  1. On the GuardDuty Findings page, choose Suppress findings.

  2. Do one of the following:

    • To use an existing filter for the rule, choose the filter from the Saved rules drop-down list.

    • To create a new rule add filter criteria to create a filter for the suppression rule. To save the filter for use later, choose Save at the end of the filter criteria field.

  3. Enter a name and a description for the suppression rule.

  4. Choose Save.

Your suppression rules can be viewed, edited, or deleted at any time by selecting the rule from the Saved rules drop down in the console.

To create a suppression rule using API:

  1. You can also create suppression rules through the CreateFilter API. You can specify the filter criteria in a JSON file following the format of the example detailed below, which would select any unarchived findings where a DNS request to was made.

    { "Criterion": { "service.archived": { "Eq": [ "false" ] }, "service.action.dnsRequestAction.domain": { "Eq": [ "" ] } } }

    For a list of JSON field names and their console equivalent see Filter criteria.

    You can test your filter criteria first by using the same JSON criterion in the ListFindings API and confirming that the correct findings have been selected or you can do this through the AWS CLI by following the example below using your own detector ID, and .json file.

    aws guardduty list-findings --detector-id 12abc34d567e8fa901bc2d34e56789f0 --finding-criteria file://criteria.json
  2. Upload your filter to be used as suppression rule with the CreateFilter API or by using the AWS CLI following the example below with your own detector ID, a name for the suppression rule, and .json file.

    aws guardduty create-filter --action ARCHIVE --detector-id 12abc34d567e8fa901bc2d34e56789f0 --name yourfiltername --finding-criteria file://criteria.json

You can view a list of your filters programmatically with the ListFilter API, you can see details of an individual filter by supplying the filter name to the GetFilter API. Update filters using UpdateFilter or delete them with the DeleteFilter API.