For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex CloudApplication Security

AWS Access logging not enabled on S3 buckets misconfiguration detected in code

Rule Details

Cortex AppSec Rule ID

APPSEC_AWS_18

Category - Subcategory

Storage - Alerting

Provider

AWS

Severity

LOW

Framework

CloudFormation, Serverless, Terraform, Terraform Plan

Mapped CSPM/KSPM Rule

4daa435b-fa46-457a-9359-6a4b4a43a442

Impact

Checks for S3 buckets without access logging turned on. Access logging allows customers to view complete audit trail on sensitive workloads such as S3 buckets. It is recommended that Access logging is turned on for all S3 buckets to meet audit & compliance requirement

How to Fix

To fix this issue, you should ensure that your S3 bucket configuration includes the LoggingConfiguration property. Below is an example of how to set this property in a CloudFormation configuration:

Example: [source,go]

"Resources": { "MyS3Bucket": { "Type": "AWS::S3::Bucket", "Properties": { "BucketName": "my-bucket", "LoggingConfiguration": { "DestinationBucketName": "my-log-bucket", "LogFilePrefix": "log/" } } } } }

Resources: MyS3Bucket: Type: AWS::S3::Bucket Properties: BucketName: "my-bucket" LoggingConfiguration: DestinationBucketName: "my-log-bucket" LogFilePrefix: "log/"

Last updated

Was this helpful?