Ensure CloudFront distributions use secure SSL/TLS protocols
CloudFront distributions should enforce TLS 1.2 or higher to protect data in transit. Older protocols like TLS 1.0 and 1.1 have known vulnerabilities.
Security Impact
Weak TLS protocols are vulnerable to POODLE, BEAST, and other attacks that can decrypt sensitive data in transit.
How to Remediate
Update the security policy to TLSv1.2_2021 or higher in distribution settings. Test client compatibility before enforcement.
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, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-cloudfront-1
- Service
- Amazon CloudFront
- Category
- Encryption
- Severity
- HIGH
- CIS Benchmark
- 4.1
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 enforce HTTPS-only viewer connections
Ensure CloudFront distributions use origin access identity (OAI) for S3 origins
Ensure CloudFront distributions have access logging enabled
Ensure CloudFront distributions have WAF integrated
Ensure CloudFront distributions use field-level encryption for sensitive data