CIS Amazon Web Services Foundations Benchmark v1.2.0/Logging/25 of 49
2.3Ensure the S3 bucket used to store CloudTrail logs is not publicly accessible
Control family: Logging
Control description
CloudTrail logs a record of every API call made in your AWS account. These logs file are stored in an S3 bucket. It is recommended that the bucket policy or access control list (ACL) applied to the S3 bucket that CloudTrail logs to prevents public access to the CloudTrail logs.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
CloudTrail logs show how the account is built and who runs it, which is exactly what an attacker wants to read. The bucket that holds them must not be readable by the public, through its bucket policy, its access control list or a setting someone changes later. S3 Block Public Access stops all three.
Before you start
The same on every cloud, before the steps in the tabs.
- Decide who may read CloudTrail logs, write the list down, and make sure nobody outside it, and never the public, has access.
- Review the log bucket's permissions on a schedule, such as quarterly.
Evidence
- The approved list of log readers and the record of each review
Not applicable. This benchmark covers AWS only.
On AWS the tasks turn on Block Public Access for the log bucket, remove any public grant already in place, and add the AWS Config rule that tests for public read access.
Task 1Block public access on the log bucket
- Sign in to the AWS Management Console at console.aws.amazon.com and open S3.
- Open the bucket named in the trail's Storage location and choose the Permissions tab.
- Under Block public access (bucket settings), choose Edit, select Block all public access and choose Save changes, then type confirm.
- In the navigation pane, choose Block Public Access settings for this account and turn it on for the whole account as well, unless a documented bucket needs public access.
- Check it: the bucket's Access column in the bucket list doesn't say Public.
Task 2Remove public grants from the bucket policy and ACL
- On the bucket's Permissions tab, under Bucket policy, choose Edit and remove any statement whose principal is everyone; keep only CloudTrail's write access and your log readers.
- Under Access control list (ACL), choose Edit and clear any permission for Everyone (public access) or Authenticated users group (anyone with an AWS account).
- Choose Save changes.
- Check it: IAM Access Analyzer for S3 in the S3 navigation pane lists no public access to the bucket.
Task 3Keep it checked with the AWS Config rule s3-bucket-public-read-prohibited
- Open AWS Config and choose Rules > Add rule.
- On Specify rule type, search for s3-bucket-public-read-prohibited, select it and choose Next.
- On Configure rule, keep the name, then choose Next.
- On Review and create, check the settings and add the rule.
- Check it: once the rule has finished Evaluating..., the log bucket shows as compliant.
Evidence
- The log bucket's Permissions tab, showing Block all public access on and no public grants
- The s3-bucket-public-read-prohibited rule, showing the bucket compliant, and Security Hub CSPM control CloudTrail.6 showing passed
Not applicable. This benchmark covers AWS only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.