ELB Listeners Have Specified Security Policies Added

Rule Details

**Table 1** Rule details
Parameter	Description
Rule Name	elb-predefined-security-policy-https-check
Identifier	ELB Listeners Have Specified Security Policies Added
Description	If a specified security policy is not configured for the HTTPS listener of a dedicated load balancer, this dedicated load balancer is non-compliant.
Tag	elb
Trigger Type	Configuration change
Filter Type	elb.loadbalancers
Rule Parameters	predefinedPolicyName: indicates the specified security policy. The default value is tls-1-0. Example values: tls-1-0, tls-1-1, tls-1-2, tls-1-0-inherit, tls-1-2-strict, tls-1-0-with-1-3, tls-1-2-fs-with-1-3, tls-1-2-fs, and hybrid-policy-1-0. For more information, see TLS Security Policy.

Application Scenarios

You are advised to configure HTTPS encryption for your load balancers to ensure secure data transmission. ELB allows you to use common TLS security policies to secure your data.

You can use later TLS versions for applications that require enhanced security, and earlier TLS versions for applications that need wider compatibility.

Solution

Configure TLS security policies for encrypted communication.

Rule Logic

If a specified security policy is not configured for the HTTPS listener of a load balancer, this load balancer is non-compliant.
If a specified security policy is configured for the HTTPS listener of a load balancer, this load balancer is compliant.

Parent topic: Elastic Load Balance

Previous topic: Load Balancers Should Not Use EIPs

Next topic: ELB Listeners Are Configured to Use HTTPS or TLS