Ensure ELB uses secure TLS protocols
Load balancers should use TLS 1.2 or higher. Disable SSLv3, TLS 1.0, and TLS 1.1.
Security Impact
Older TLS versions have known vulnerabilities (POODLE, BEAST) that can be exploited.
How to Remediate
Use security policies that enforce TLS 1.2+: ELBSecurityPolicy-TLS13-1-2-2021-06 or similar.
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, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-elb-3
- Service
- Elastic Load Balancing (ELB)
- Category
- Encryption
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial