💼 [ELB.14] Classic Load Balancer should be configured with defensive or strictest desync mitigation mode

• Contextual name: 💼 [ELB.14] Classic Load Balancer should be configured with defensive or strictest desync mitigation mode

• ID: /frameworks/aws-fsbp-v1.0.0/elb/14

• Located in: 💼 Elastic Load Balancing (ELB)

Description

HTTP Desync issues can lead to request smuggling and make applications vulnerable to request queue or cache poisoning. In turn, these vulnerabilities can lead to credential hijacking or execution of unauthorized commands. Classic Load Balancers configured with defensive or strictest desync mitigation mode protect your application from security issues that may be caused by HTTP Desync.

Similar

• AWS Security Hub
  • https://docs.aws.amazon.com/securityhub/latest/userguide/elb-controls.html#elb-14
• Internal
  • ID: dec-c-e50a12aa

Similar Sections (Give Policies To)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(21) Information Flow Enforcement _ Physical or Logical Separation of Information Flows		35	39
💼 NIST SP 800-53 Revision 5 → 💼 CA-9(1) Internal System Connections _ Compliance Checks			15
💼 NIST SP 800-53 Revision 5 → 💼 CM-2 Baseline Configuration	7		13
💼 PCI DSS v4.0.1 → 💼 6.2.4 Software engineering techniques or other methods are defined and in use by software development personnel to prevent or mitigate common software attacks and related vulnerabilities in bespoke and custom software.

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags