Ensure S3 bucket has server access logging enabled
Server access logging provides detailed records of requests made to the bucket, including requester, bucket name, request time, action, response status, and error codes.
Security Impact
Without access logs, security incidents, unauthorized access attempts, and data exfiltration cannot be properly investigated.
How to Remediate
Enable server access logging and store logs in a separate dedicated logging bucket. Ensure the logging bucket has appropriate retention policies.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Simple Storage Service (S3) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for CIS AWS v1.5.0, CIS AWS v2.0, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-s3-7
- Service
- Simple Storage Service (S3)
- Category
- Logging
- Severity
- MEDIUM
- CIS Benchmark
- 2.1.7
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Simple Storage Service (S3) Checks
View all checksEnsure S3 bucket has block public access enabled
Ensure S3 bucket policy does not allow public read access
Ensure S3 bucket policy does not allow public write access
Ensure MFA Delete is enabled on S3 buckets
Ensure S3 bucket has server-side encryption enabled