Ensure ALB desync mitigation mode is enabled
ALB desync mitigation mode should be set to defensive or strictest to protect against HTTP desync attacks.
Security Impact
HTTP desync attacks can lead to request smuggling and cache poisoning.
How to Remediate
Set desync mitigation mode to defensive or strictest: aws elbv2 modify-load-balancer-attributes --attributes Key=routing.http.desync_mitigation_mode,Value=defensive
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 Elastic Load Balancing (ELB) 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, PCI-DSS, OWASP compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-elb-13
- Service
- Elastic Load Balancing (ELB)
- Category
- Web Security
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial