AWS guardduty documentation change
Summary
Changed 'AWS Security Hub' to 'AWS Security Hub CSPM' in suppression rules documentation
Security assessment
Updates security tool naming in suppression workflow documentation but does not change security behavior.
Diff
diff --git a/guardduty/latest/ug/findings_suppression-rule.md b/guardduty/latest/ug/findings_suppression-rule.md index 4886a91f1..a697f123a 100644 --- a//guardduty/latest/ug/findings_suppression-rule.md +++ b//guardduty/latest/ug/findings_suppression-rule.md @@ -13 +13 @@ After you create a suppression rule, new findings that match the criteria define -Suppressed findings are not sent to AWS Security Hub, Amazon Simple Storage Service, Amazon Detective, or Amazon EventBridge, reducing finding noise level if you consume GuardDuty findings via Security Hub, a third-party SIEM, or other alerting and ticketing applications. If you've enabled [Malware Protection for EC2](./malware-protection.html), the suppressed GuardDuty findings won't initiate a malware scan. +Suppressed findings are not sent to AWS Security Hub CSPM, Amazon Simple Storage Service, Amazon Detective, or Amazon EventBridge, reducing finding noise level if you consume GuardDuty findings via Security Hub CSPM, a third-party SIEM, or other alerting and ticketing applications. If you've enabled [Malware Protection for EC2](./malware-protection.html), the suppressed GuardDuty findings won't initiate a malware scan.