Ensure CloudFront distributions use Lambda@Edge for additional security controls
Lambda@Edge functions can implement custom authentication, request/response manipulation, and additional security controls at CloudFront edge locations.
Security Impact
Missing edge security controls may require expensive origin requests or allow unauthorized access patterns.
How to Remediate
Deploy Lambda@Edge functions for custom security logic like token validation, header manipulation, or geographic access controls.
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 Defense in Depth compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-cloudfront-18
- Service
- Amazon CloudFront
- Category
- Security Enhancement
- Severity
- LOW
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