Classic Load Balancers should be configured to use defensive or strictest desync mitigation mode

Documentos > Datadog Security > OOTB Rules > Classic Load Balancers should be configured to use defensive or strictest desync mitigation mode

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Description

This check verifies Classic Load Balancers are set to use either the defensive or strictest desync mitigation mode. HTTP desynchronization issues can lead to request smuggling, making applications vulnerable to request queue or cache poisoning. These vulnerabilities can, in turn, result in credential hijacking or the execution of unauthorized commands. Classic Load Balancers configured with the defensive or strictest desync mitigation mode help protect your application from security risks associated with HTTP desynchronization.

Remediation

To change the desync mitigation mode for a Classic Load Balancer, refer to the Modify desync mitigation mode in the User Guide for Classic Load Balancers.