---
title: Load Balancers should use the latest security policy
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > Load Balancers should use the latest
  security policy
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Load Balancers should use the latest security policy
 
## Description{% #description %}

Use the latest predefined AWS security policy on your Application Load Balancer (ALB) so TLS negotiation uses current protocol versions and post-quantum (PQ) key exchange. This check evaluates every TLS listener on the ALB independently: a listener is treated as TLS when its protocol is HTTPS or TLS, or when it has a security policy set. Each TLS listener must use one of these 2025-09 PQ policies, and a single listener with an older or missing policy fails the check even when other listeners comply:

- `ELBSecurityPolicy-TLS13-1-2-PQ-2025-09`
- `ELBSecurityPolicy-TLS13-1-2-Res-PQ-2025-09`
- `ELBSecurityPolicy-TLS13-1-3-PQ-2025-09`
- `ELBSecurityPolicy-TLS13-1-2-FIPS-PQ-2025-09`
- `ELBSecurityPolicy-TLS13-1-2-Res-FIPS-PQ-2025-09`
- `ELBSecurityPolicy-TLS13-1-3-FIPS-PQ-2025-09`

The extended-cipher `Ext0`, `Ext1`, and `Ext2` PQ variants fail because they negotiate weaker cipher suites.

ALBs with only HTTP listeners or without listeners are skipped. Network and Gateway Load Balancers are not evaluated. Load balancers whose type is missing or empty fail.

## Remediation{% #remediation %}

1. Review the [security policies for your Application Load Balancer](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/describe-ssl-policies.html) and choose an approved 2025-09 PQ policy that your clients support.
1. For every HTTPS listener that does not use an approved policy, [update the security policy](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-update-certificates.html#update-security-policy) to the chosen policy.
