Other Articles

Load Balancer – Use Strong TLS Policies

Secure Configuration Checks > AWS

This check ensures that the HTTPS and TLS listeners of your load balancers use a security policy that requires TLS 1.2 or newer. Older protocol versions, TLS 1.0 and TLS 1.1, have known weaknesses and are no longer considered secure.

Check Details

  • Resource: Application Load Balancer and Network Load Balancer listener
  • Check: Use strong load balancer TLS policies (TlsPolicyStrong)
  • Risk: Attackers can force a weak protocol version and break or downgrade the encryption of traffic to your application

Security policy examples

The name of a policy shows the lowest TLS version that it allows. The policies below are examples. Use aws elbv2 describe-ssl-policies to see the full, current list.

  • Compliant: ELBSecurityPolicy-TLS13-1-2-2021-06, ELBSecurityPolicy-TLS13-1-3-2021-06, ELBSecurityPolicy-TLS-1-2-2017-01, ELBSecurityPolicy-TLS-1-2-Ext-2018-06
  • Non-compliant: ELBSecurityPolicy-2016-08, ELBSecurityPolicy-TLS-1-0-2015-04, ELBSecurityPolicy-TLS-1-1-2017-01, ELBSecurityPolicy-FS-2018-06

Remediation via AWS Console

  1. Open the Amazon EC2 console and select Load Balancers under Load Balancing.

    Amazon EC2 Console
  2. Select the affected load balancer and open the Listeners and rules tab.

    Load balancer listeners and rules tab
  3. Click the listener's Protocol:Port link for the HTTPS or TLS listener.

  4. Open the Security tab and click Edit secure listener settings.

  5. Under Secure listener settings, select a Security policy that requires TLS 1.2 or newer, such as ELBSecurityPolicy-TLS13-1-2-2021-06.

    Select a security policy for a listener
  6. Click Save changes. Repeat for every secure listener on each affected load balancer.

Remediation via AWS CLI

  1. Log in to the AWS Management Console and click the CloudShell icon (>_) in the top-right corner.

    AWS CloudShell
  2. List the HTTPS and TLS listeners that use a policy which still allows TLS 1.0 or TLS 1.1. The output shows the listener ARN and the policy name:

    WEAK=$(for t in application network; do
      aws elbv2 describe-ssl-policies --load-balancer-type $t \
      --query "SslPolicies[?contains(SslProtocols, 'TLSv1') || contains(SslProtocols, 'TLSv1.1')].Name" \
      --output text
    done)
    
    for arn in $(aws elbv2 describe-load-balancers \
      --query 'LoadBalancers[?Type==`application` || Type==`network`].LoadBalancerArn' \
      --output text); do
      aws elbv2 describe-listeners --load-balancer-arn "$arn" --output json | \
     jq -r --arg weak "$WEAK" '
        ([$weak | splits("\\s+")]) as $w
        | .Listeners[]
        | select(.Protocol == "HTTPS" or .Protocol == "TLS")
        | select(.SslPolicy as $p | ($w | index($p)) != null)
    | [.ListenerArn, .SslPolicy]
    | @tsv'
    done
    
    

    The command covers one region. Add --region <region> to each aws command to check another.

  3. Change the security policy of the listener:

    aws elbv2 modify-listener \
    --listener-arn <listener-arn> \
    --ssl-policy ELBSecurityPolicy-TLS13-1-2-2021-06
    
  4. Verify the policy of the listeners:

    aws elbv2 describe-listeners \
    --load-balancer-arn <load-balancer-arn> \
    --query "Listeners[?Protocol=='HTTPS' || Protocol=='TLS'].[ListenerArn,SslPolicy]" \
    --output table
    

    Each listener must show a policy that requires TLS 1.2 or newer.

Replace <listener-arn> with the ARN of the listener that step 2 lists. Replace <load-balancer-arn> with the ARN of the load balancer. Repeat steps 3 and 4 for each listener that step 2 lists.

Updated on 04 November, 2026