Load balancer listener allows TLS 1.0 or 1.1
- Severity
- Medium
- Service
- Elastic Load Balancing
- Check ID
- ELB_TLS_POLICY_WEAK
What this check finds
An HTTPS or TLS listener on an Application or Network Load Balancer uses a security policy that still accepts TLS 1.0 or TLS 1.1. Both are deprecated: clients that can be made to downgrade negotiate a protocol with known weaknesses. ELBSecurityPolicy-2016-08, the default for listeners created outside the console, is one of them.
Passing looks like: Load balancer listeners allow TLS 1.2 or later only.
How to fix it
Switch the listener to a policy that allows TLS 1.2 and 1.3 only, such as ELBSecurityPolicy-TLS13-1-2-2021-06 (or a FIPS / PQ variant).
AWS CLI
aws elbv2 modify-listener --listener-arn LISTENER_ARN --ssl-policy ELBSecurityPolicy-TLS13-1-2-2021-06
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
EC2 → Load Balancers → select load balancer → Listeners → select listener → Edit → Security policy.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| PCI-DSS v4.0.1 |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs