このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、
お気軽にご連絡ください。
利用可能な対象:
Cloud Security
|
Code Security
|
App and API Protection
|
Workload Protection
Configure mute rules to streamline security alerts by automatically filtering out non-urgent findings. This approach helps reduce noise from known false positives and accepted risks, allowing you to focus on addressing the most critical threats.
Create a mute rule
- In Datadog, go to Security > Settings > Findings Automation. Click Add a New Rule, then select Mute. The Create a New Rule page opens.
- Under Rule name, enter a descriptive name for the rule; for example, “Compensating control in place for account payment-prod”.
- Add your rule criteria into the following fields:
- Any of these types: The types of findings that the rule should check for. Available types include:
- Runtime Code Vulnerability
- Static Code Vulnerability
- Library Vulnerability
- Secret
- Infrastructure as Code
- Container Image Vulnerability
- Host Vulnerability
- Misconfiguration
- Attack Path
- Identity Risk
- API Security
- Workload Activity
- Any of these tags or attributes: The resource tags or attributes that must match for the rule to apply.
- To add severity criteria to the rule, click Add Severity.
- Specify the mute reason and duration:
- Reason for muting: The reason for muting the finding. Available reasons include:
- False Positive
- Risk Accepted
- Pending fix
- No Fix
- Duplicate
- Other
- Rule expiration: The date on which the rule expires.
- Further description for muting reason: Optional box for additional details.
- Click Save. The rule applies to new findings immediately and starts checking existing findings within the next hour.
You can also create mute rules with the API or the datadog_security_findings_mute_rule Terraform resource.
Rule matching order
When Datadog identifies a finding, it evaluates the finding against your sequence of mute rules. Starting with the first rule, if there’s a match, Datadog mutes the finding for the specified duration and stops evaluating further. If no match occurs, Datadog moves to the next rule. This process continues until a match is found or all rules are checked without a match.
Further reading
