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

문서 > Datadog 보안 > OOTB Rules > Classic Load Balancers should be configured to use defensive or strictest desync mitigation mode

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

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.