Ensure that Object-level logging for read events is enabled for S3 bucket

From Console

1. Open the Amazon S3 console S3
2. Choose the required bucket from the bucket list.
3. Choose Properties tab to see in detail bucket configuration.
4. Navigate to AWS CloudTrail data events section to select the CloudTrail name for the recording activity.
5. You can choose an existing Cloudtrail or create a new one by navigating to the Cloudtrail console link from S3.
6. Once the Cloudtrail console, navigate to Data events : S3 section.
7. If the current status for Object-level logging is set to Disabled, then object-level logging of read events for the selected s3 bucket is not set
   • Select Edit to enable the Read event.
   • You can choose to select All current and future S3 buckets or Individual bucket.
8. Repeat steps 2 to 7 to enable object-level logging of read events for other S3 buckets.

From Command Line

1. To enable object-level data events logging for S3 buckets within your AWS account, run put-event-selectors command using the name of the trail that you want to reconfigure as identifier:

aws cloudtrail put-event-selectors --region <region-name> --trail-name <trail-name> --event-selectors '[{ "ReadWriteType": "ReadOnly", "IncludeManagementEvents":true, "DataResources": [{ "Type": "AWS::S3::Object", "Values": ["arn:aws:s3:::<s3-bucket-name>/"] }] }]'

1. The command output will be object-level event trail configuration.
2. If you want to enable it for all buckets at once then change Values parameter to ["arn:aws:s3"] in command given above.
3. Repeat step 1 for each s3 bucket to update object-level logging of write events.
4. Change the AWS region by updating the --region command parameter and perform the process for other regions.

Multiple Remediation Paths

AWS

SERVICE-WIDE (RECOMMENDED when many resources are affected): Deploy centralized guardrails and remediation using AWS Config Conformance Packs and (if applicable) AWS Organizations SCPs.

aws configservice put-organization-conformance-pack --organization-conformance-pack-name <pack-name> --template-s3-uri s3://<bucket>/<template>.yaml

ASSET-LEVEL: Apply the resource-specific remediation steps above to only the affected assets.

PREVENTIVE: Add CI/CD policy checks (CloudFormation/Terraform validation) before deployment to prevent recurrence.

References for Service-Wide Patterns

• AWS Config Conformance Packs: https://docs.aws.amazon.com/config/latest/developerguide/conformance-packs.html
• AWS Organizations SCP examples: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps_examples.html

Operational Rollout Workflow

Use this sequence to reduce risk and avoid repeated drift.

1. Contain at Service-Wide Scope First (Recommended)

• AWS: deploy/adjust organization conformance packs and policy guardrails.

aws configservice put-organization-conformance-pack --organization-conformance-pack-name <pack-name> --template-s3-uri s3://<bucket>/<template>.yaml

2. Remediate Existing Affected Assets

• Execute the control-specific Console/CLI steps documented above for each flagged resource.
• Prioritize internet-exposed and production assets first.

3. Validate and Prevent Recurrence

• Re-scan after each remediation batch.
• Track exceptions with owner and expiry date.
• Add preventive checks in IaC/CI pipelines.