AWS guardduty documentation change
Summary
Clarified that GuardDuty scans the content (not just existence) of uploaded S3 objects matching specified prefixes
Security assessment
Change improves accuracy of malware scanning description but doesn't address a specific vulnerability or weakness. No evidence of security incident remediation.
Diff
diff --git a/guardduty/latest/ug/how-malware-protection-for-s3-gdu-works.md b/guardduty/latest/ug/how-malware-protection-for-s3-gdu-works.md index 363d5bce8..1718e9633 100644 --- a//guardduty/latest/ug/how-malware-protection-for-s3-gdu-works.md +++ b//guardduty/latest/ug/how-malware-protection-for-s3-gdu-works.md @@ -15 +15 @@ This section describes components of Malware Protection for S3, how it works aft -You can enable Malware Protection for S3 for an Amazon S3 bucket that belongs to your own AWS account. GuardDuty provides you flexibility to enable this feature for your entire bucket, or limit the scope of the malware scan to specific [object prefixes](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-prefixes.html) where GuardDuty scans each uploaded object that starts with one of the selected prefixes. You can add up to 5 prefixes. When you enable the feature for an S3 bucket, then that bucket is called a **protected bucket**. +You can enable Malware Protection for S3 for an Amazon S3 bucket that belongs to your own AWS account. GuardDuty provides you flexibility to enable this feature for your entire bucket, or limit the scope of the malware scan to specific [object prefixes](https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-prefixes.html) where GuardDuty scans the content of each uploaded object that starts with one of the selected prefixes. You can add up to 5 prefixes. When you enable the feature for an S3 bucket, then that bucket is called a **protected bucket**.