Ensure CloudFront distributions use signed URLs or signed cookies for private content
Signed URLs and cookies provide time-limited, authenticated access to private content, preventing unauthorized sharing and hotlinking.
Security Impact
Without signed access, private content can be freely shared, bypassing subscription models and access controls.
How to Remediate
Configure trusted signers in CloudFront. Implement signed URL or signed cookie generation in the application for private content.
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 SOC 2, Access Control compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-cloudfront-11
- Service
- Amazon CloudFront
- Category
- Access Control
- Severity
- MEDIUM
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 access logging enabled
Ensure CloudFront distributions have WAF integrated