Ensure CloudFront distributions have access logging enabled
Access logs provide detailed records of every request, including viewer location, request type, response codes, and user agents. Essential for security monitoring and compliance.
Security Impact
Without access logs, security incidents, bot traffic, and unusual access patterns cannot be detected or investigated.
How to Remediate
Enable access logging in distribution settings. Configure an S3 bucket to store logs with appropriate retention and lifecycle 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 Amazon CloudFront 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 v2.0, SOC 2, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-cloudfront-4
- Service
- Amazon CloudFront
- Category
- Logging and Monitoring
- Severity
- MEDIUM
- CIS Benchmark
- 4.3
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon CloudFront Checks
View all checksEnsure CloudFront distributions use secure SSL/TLS protocols
Ensure CloudFront distributions enforce HTTPS-only viewer connections
Ensure CloudFront distributions use origin access identity (OAI) for S3 origins
Ensure CloudFront distributions have WAF integrated
Ensure CloudFront distributions use field-level encryption for sensitive data