AWS guardduty: GuardDuty adds S3 bucket owner verification for findings export
Summary
Adds a documentation history entry announcing that when exporting GuardDuty findings to an Amazon S3 bucket, you can optionally specify the AWS account ID of the expected bucket owner so findings are exported only to a bucket owned by that account.
Security assessment
The entry documents a new security control (expected bucket owner verification) that prevents GuardDuty findings from being exported to a bucket not owned by the intended account, reducing risk of misdirected data exposure. It announces a feature rather than fixing a specific vulnerability or incident, so security_issue_related is false.
Evidence
+S3 bucket owner verification for exporting findings| When you configure settings to export GuardDuty findings to an Amazon S3 bucket, you can now optionally specify the AWS account ID of the expected bucket owner. With this feature, you can make sure that GuardDuty exports findings only to a bucket that the specified account owns. For more information, see [Verifying the S3 bucket owner](https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_exportfindings.html#guardduty-exportfindings-expected-bucket-owner).| October 19, 2026
Diff
diff --git a/guardduty/latest/ug/doc-history.md b/guardduty/latest/ug/doc-history.md index 377959c..280140c 100644 --- a//guardduty/latest/ug/doc-history.md +++ b//guardduty/latest/ug/doc-history.md @@ -14,0 +15 @@ Change| Description| Date +S3 bucket owner verification for exporting findings| When you configure settings to export GuardDuty findings to an Amazon S3 bucket, you can now optionally specify the AWS account ID of the expected bucket owner. With this feature, you can make sure that GuardDuty exports findings only to a bucket that the specified account owns. For more information, see [Verifying the S3 bucket owner](https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_exportfindings.html#guardduty-exportfindings-expected-bucket-owner).| October 19, 2026