HIGH

Ensure CloudFront distributions enforce origin SSL/TLS for custom origins

Communication between CloudFront and custom origins should use HTTPS to prevent data interception in AWS network backbone.

Security Impact

HTTP communication to origin exposes data within AWS network and violates encryption in transit requirements.

How to Remediate

Set Origin Protocol Policy to 'HTTPS Only' for all custom origins. Ensure origin servers have valid SSL/TLS certificates.

Affected Resources

AWS::CloudFront::Distribution

Compliance Frameworks

PCI-DSSHIPAASOC 2NIST 800-53

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 PCI-DSS, HIPAA, SOC 2 compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-cloudfront-7
Service
Amazon CloudFront
Category
Encryption
Severity
HIGH

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Amazon CloudFront Checks

View all checks
aws-cloudfront-1high

Ensure CloudFront distributions use secure SSL/TLS protocols

aws-cloudfront-2high

Ensure CloudFront distributions enforce HTTPS-only viewer connections

aws-cloudfront-3high

Ensure CloudFront distributions use origin access identity (OAI) for S3 origins

aws-cloudfront-4medium

Ensure CloudFront distributions have access logging enabled

aws-cloudfront-5high

Ensure CloudFront distributions have WAF integrated