Skip to content

Commit

Permalink
DOCS-8405 clarifying suppresssions
Browse files Browse the repository at this point in the history
  • Loading branch information
michaelcretzman authored Oct 4, 2024
1 parent 947563c commit 44f8c6d
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions content/en/security/suppressions.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,8 @@ The [suppression list][3] provides a centralized and organized way for you to ma
1. Select the detection rules you want to apply this suppression to. You can select multiple detection rules.
1. In the **Add Suppression Query** section, you have the option to enter suppression queries so that a signal is not generated when the values are met. For example, if a user `john.doe` is triggering a signal, but their actions are benign and you no longer want signals triggered from this user, input the log query: `@user.username:john.doe`.
{{< img src="security/security_monitoring/suppressions/suppression_query.png" alt="The add suppression query with the query @user.username:john.doe" style="width:65%;" >}}
Suppression rule queries are based on **signal attributes**.
1. Additionally, you can add a log exclusion query to exclude logs from being analyzed. These queries are based on **log attributes**. **Note**: The legacy suppression was based on log exclusion queries, but it is now included in the suppression rule's **Add a suppression query** step.
In general, suppression rules are evaluated on signal outputs and not input logs/events. To add queries that only use inputs and CWS Agent and [NetFlow][6] events, you can suppress logs using the **Additionally, you can add a suppression query on log attribution to exclude logs from analysis** option.

Check notice on line 55 in content/en/security/suppressions.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.sentencelength

Suggestion: Try to keep your sentence length to 25 words or fewer.
1. In **Additionally, you can add a suppression query on log attribution to exclude logs from analysis**, add a log exclusion query to exclude logs from analysis. These queries are based on **log attributes**. **Note**: The legacy suppression was based on log exclusion queries, but it is now included in this suppression rule's **Add Suppression Query** step.

Check warning on line 56 in content/en/security/suppressions.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense

Avoid temporal words like 'now'.

## Further reading

Expand All @@ -64,3 +64,4 @@ The [suppression list][3] provides a centralized and organized way for you to ma
[3]: https://app.datadoghq.com/security/configuration/suppressions
[4]: https://app.datadoghq.com/security/rules
[5]: /logs/explorer/facets/#log-side-panel
[6]: /network_monitoring/netflow/

0 comments on commit 44f8c6d

Please sign in to comment.