Ensure CloudFront distributions use origin access identity (OAI) for S3 origins
Origin Access Identity restricts S3 bucket access to only CloudFront, preventing direct public access to origin content and ensuring all traffic flows through CloudFront security controls.
Security Impact
Without OAI, users can bypass CloudFront to access S3 content directly, avoiding WAF rules, logging, and geographic restrictions.
How to Remediate
Create an Origin Access Identity and associate it with S3 origins. Update S3 bucket policy to only allow access from the OAI.
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, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-cloudfront-3
- Service
- Amazon CloudFront
- Category
- Access Control
- Severity
- HIGH
- CIS Benchmark
- 4.2
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 have access logging enabled
Ensure CloudFront distributions have WAF integrated
Ensure CloudFront distributions use field-level encryption for sensitive data