Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
elbv2_insecure_ssl_ciphersProvider: AWS
Service:
elbv2Severity: MEDIUM
Categories:
encryptionResource type:
AwsElbv2LoadBalancerWhat this check verifies
ELBv2 HTTPS listeners are assessed for use of strong TLS policies. Listeners whosessl_policy is not in the approved set (TLS 1.2/1.3-focused policies) may include weak protocols or ciphers.
Risk
Legacy or weak ciphers enable downgrade and man-in-the-middle attacks, allowing decryption of sessions, credential theft, and request tampering. This undermines confidentiality and integrity of data in transit and can expose cookies or tokens for account takeover.Recommendation
Enforce modern TLS on load balancer listeners:- Use AWS recommended policies like
ELBSecurityPolicy-TLS13-1-2-2021-06 - Disable TLS 1.0/1.1 and weak ciphers; prefer suites with forward secrecy
- Periodically review and update policies
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws elbv2 modify-listener —listener-arn <listener_arn> —ssl-policy ELBSecurityPolicy-TLS13-1-2-2021-06
References
- https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-https-listener.html#describe-ssl-policies
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/ELBv2/security-policy.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = elbv2_insecure_ssl_ciphers. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks