AWS guardduty: GuardDuty export findings: clarify bucket owner verification
Summary
Reordered the export-findings steps (Step 4/Step 5 and 'Verifying the Amazon S3 bucket owner'), fixed grammar, corrected 'KMS key policy' to 'bucket policy' in the JSON-syntax note, expanded the Step 4 policy-attachment instruction, and rewrote the 'expected bucket owner' guidance: added an Important warning that a mismatched account ID stops exports and that the setting cannot be removed, added a note that GuardDuty only checks the owner at export time (not on Create/UpdatePublishingDestination), removed the regional-enforcement sentence, the 'strongly recommend' sentence, and noted older AWS CLI versions don't support ExpectedBucketOwner.
Security assessment
The change documents the expected-bucket-owner verification control, which prevents findings from being exported to a bucket owned by an unintended account (misdirected export/data exposure), and adds warnings about mismatched account IDs, immutability of the setting, and needing a current AWS CLI. It also tightens security-relevant config language (bucket policy vs KMS key policy, attaching policies to both the S3 bucket and KMS key). However, no CVE, incident, or fixed vulnerability is referenced; it is guidance/behavior clarification rather than remediation of a specific weakness, and it even drops the prior 'We strongly recommend that you provide the expected bucket owner' wording.
Evidence
+Verify that the account ID that you provide is correct so that GuardDuty continues to export your findings. GuardDuty doesn't check the bucket owner when you create or update the publishing destination. GuardDuty detects an account ID that doesn't match the bucket owner only when it exports findings to the bucket.
Diff
diff --git a/guardduty/latest/ug/guardduty_exportfindings.md b/guardduty/latest/ug/guardduty_exportfindings.md index 5c3502e..e513a45 100644 --- a//guardduty/latest/ug/guardduty_exportfindings.md +++ b//guardduty/latest/ug/guardduty_exportfindings.md @@ -7 +7 @@ -ConsiderationsStep 1 – Permissions required to export findingsStep 2 – Attaching policy to your KMS keyStep 3 – Attaching policy to Amazon S3 bucketStep 4 - Exporting findings to an S3 bucket (Console)Verifying the Amazon S3 bucket ownerStep 5 – Frequency for exporting findings +ConsiderationsStep 1 – Permissions required to export findingsStep 2 – Attaching policy to your KMS keyStep 3 – Attaching policy to Amazon S3 bucketStep 4 – Exporting findings to an S3 bucket (Console)Step 5 – Frequency for exporting findingsVerifying the Amazon S3 bucket owner @@ -27,3 +27 @@ When you configure settings to export findings to an Amazon S3 bucket, GuardDuty - * Step 4 - Exporting findings to an S3 bucket (Console) - - * Verifying the Amazon S3 bucket owner + * Step 4 – Exporting findings to an S3 bucket (Console) @@ -32,0 +31,2 @@ When you configure settings to export findings to an Amazon S3 bucket, GuardDuty + * Verifying the Amazon S3 bucket owner + @@ -50 +50 @@ Before proceeding with the prerequisites and steps to export findings, consider - * **Permissions to export findings** – To configure settings for exporting active findings, your S3 bucket must have permissions that allows GuardDuty to upload objects. You must also have an AWS KMS key that GuardDuty can use to encrypt findings. + * **Permissions to export findings** – To configure settings for exporting active findings, your S3 bucket must have permissions that allow GuardDuty to upload objects. You must also have an AWS KMS key that GuardDuty can use to encrypt findings. @@ -133 +133 @@ If **Switch to policy view** is displayed, choose it to display the **Key policy - 4. Replace `SourceDetectorID` with the `detectorID` of the GuardDuty account in the specific Region where the findings generated. + 4. Replace `SourceDetectorID` with the `detectorID` of the GuardDuty account in the specific Region where the findings are generated. @@ -162 +162 @@ If you do not already have an Amazon S3 bucket where you want to export these fi - 2. The **example policy** shows how grant GuardDuty permission to export findings to your Amazon S3 bucket. If you change the path after you configure export findings, then you must modify the policy to grant permission to the new location. + 2. The **example policy** shows how to grant GuardDuty permission to export findings to your Amazon S3 bucket. If you change the path after you configure export findings, then you must modify the policy to grant permission to the new location. @@ -166 +166 @@ Copy the following **example policy** and paste it into the **Bucket policy edit -If you added the policy statement before the final statement, add a comma before adding this statement. Make sure that the JSON syntax of your KMS key policy is valid. +If you added the policy statement before the final statement, add a comma before adding this statement. Make sure that the JSON syntax of your bucket policy is valid. @@ -263 +263 @@ JSON - 4. Replace `SourceDetectorID` with the `detectorID` of the GuardDuty account in the specific Region where the findings generated. + 4. Replace `SourceDetectorID` with the `detectorID` of the GuardDuty account in the specific Region where the findings are generated. @@ -282 +282 @@ If you're using GuardDuty in an opt-in Region, replace the value for the "Servic -## Step 4 - Exporting findings to an S3 bucket (Console) +## Step 4 – Exporting findings to an S3 bucket (Console) @@ -312 +312 @@ We recommend that you provide this value. If you don't provide a value, GuardDut - 7. ###### Attach policies + 7. Attach the following policies to your Amazon S3 bucket and AWS KMS key: @@ -322,0 +323,23 @@ We recommend that you provide this value. If you don't provide a value, GuardDut +## Step 5 – Setting frequency to export updated active findings + +Configure the frequency for exporting updated active findings as appropriate for your environment. By default, updated findings are exported every 6 hours. This means that any findings that are updated after the most recent export are included in the next export. If updated findings are exported every 6 hours and the export occurs at 12:00, any finding that you update after 12:00 is exported at 18:00. + +###### To set the frequency + + 1. Open the GuardDuty console at [https://console.aws.amazon.com/guardduty/](https://console.aws.amazon.com/guardduty/). + + 2. Choose **Settings**. + + 3. In the **Findings export options** section, choose **Frequency for updated findings**. This sets the frequency for exporting updated Active findings to both EventBridge and Amazon S3. You can choose from the following: + + * **Update EventBridge and S3 every 15 minutes** + + * **Update EventBridge and S3 every 1 hour** + + * **Update EventBridge and S3 every 6 hours (default)** + + 4. Choose **Save changes**. + + + + @@ -327 +350,3 @@ When you configure settings to export findings, you identify the destination Ama -To protect against this, you can optionally specify the expected bucket owner – the 12-digit AWS account ID of the account that owns the destination Amazon S3 bucket. When you provide this value, GuardDuty verifies that the specified account owns the bucket before it exports findings. If the account ID doesn't match the actual owner of the bucket, GuardDuty doesn't export findings to that bucket and the publishing destination status changes to indicate that you need to fix the destination property. GuardDuty enforces this verification consistently, regardless of the AWS Region where your findings are generated. +To protect against this, you can optionally specify the expected bucket owner – the 12-digit AWS account ID of the account that owns the destination Amazon S3 bucket. When you provide this value, GuardDuty verifies that the specified account owns the bucket before it exports findings. If the account ID doesn't match the actual owner of the bucket, GuardDuty doesn't export findings to that bucket. + +Verify that the account ID that you provide is correct so that GuardDuty continues to export your findings. GuardDuty doesn't check the bucket owner when you create or update the publishing destination. GuardDuty detects an account ID that doesn't match the bucket owner only when it exports findings to the bucket. @@ -331 +356 @@ To protect against this, you can optionally specify the expected bucket owner -Providing the expected bucket owner is optional. If you don't specify the expected bucket owner, GuardDuty doesn't perform this verification and continues to export findings to the bucket that matches the destination ARN. We strongly recommend that you provide the expected bucket owner when possible. +Providing the expected bucket owner is optional. If you don't specify the expected bucket owner, GuardDuty doesn't perform this verification and continues to export findings to the bucket that matches the destination ARN. @@ -333 +358 @@ Providing the expected bucket owner is optional. If you don't specify the expect -You set the expected bucket owner through the **Expected bucket owner** field on the GuardDuty console (see Step 4 - Exporting findings to an S3 bucket (Console)), or through the `ExpectedBucketOwner` property of `DestinationProperties` when you call the [CreatePublishingDestination](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_CreatePublishingDestination.html) or [UpdatePublishingDestination](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdatePublishingDestination.html) API. The same property is returned by the [DescribePublishingDestination](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_DescribePublishingDestination.html) API. +You set the expected bucket owner through the **Expected bucket owner** field on the GuardDuty console (see Step 4 – Exporting findings to an S3 bucket (Console)), or through the `ExpectedBucketOwner` property of `DestinationProperties` when you call the [CreatePublishingDestination](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_CreatePublishingDestination.html) or [UpdatePublishingDestination](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdatePublishingDestination.html) API. The same property is returned by the [DescribePublishingDestination](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_DescribePublishingDestination.html) API. @@ -339 +364,18 @@ If you already export findings to an Amazon S3 bucket, we recommend that you add -Before you begin, make sure that the AWS CLI is installed and configured, and that you know your detector ID and the ID of the publishing destination. +###### Important + +Make sure that the account ID is correct. If it doesn't match the owner of the bucket, GuardDuty stops exporting findings to the bucket. Although you can change the expected bucket owner later, you can't remove it from the publishing destination. + +Before you begin, make sure that you have the following: + + * The latest version of the AWS Command Line Interface (AWS CLI), installed and configured. + + * Your detector ID. + + * The ID of the publishing destination. + + + + +###### Note + +Earlier versions of the AWS CLI don't support the `ExpectedBucketOwner` property. @@ -374,24 +416 @@ To find the `detectorId` for your account and current Region, see the **Settings -If you omit `ExpectedBucketOwner` (or pass an empty value) in an `UpdatePublishingDestination` request, GuardDuty keeps the previously configured value. To change it, provide the new 12-digit AWS account ID. - -## Step 5 – Setting frequency to export updated active findings - -Configure the frequency for exporting updated active findings as appropriate for your environment. By default, updated findings are exported every 6 hours. This means that any findings that are updated after the most recent export are included in the next export. If updated findings are exported every 6 hours and the export occurs at 12:00, any finding that you update after 12:00 is exported at 18:00. - -###### To set the frequency - - 1. Open the GuardDuty console at [https://console.aws.amazon.com/guardduty/](https://console.aws.amazon.com/guardduty/). - - 2. Choose **Settings**. - - 3. In the **Findings export options** section, choose **Frequency for updated findings**. This sets the frequency for exporting updated Active findings to both EventBridge and Amazon S3. You can choose from the following: - - * **Update EventBridge and S3 every 15 minutes** - - * **Update EventBridge and S3 every 1 hour** - - * **Update EventBridge and S3 every 6 hours (default)** - - 4. Choose **Save changes**. - - - +If you omit `ExpectedBucketOwner` (or pass an empty value) in an `UpdatePublishingDestination` request, GuardDuty keeps the previously configured value. This also applies when you clear the **Expected bucket owner** field on the GuardDuty console. To change the value, provide the new 12-digit AWS account ID. To remove the expected bucket owner, delete the publishing destination and create it again without specifying the expected bucket owner.