TLS Security Policy
Scenarios
HTTPS encryption is commonly used for applications that require secure transmission of data, such as banks and finance. When you add HTTPS listeners, you can select appropriate default security policies to improve security. A security policy is a combination of TLS protocols of different versions and supported cipher suites.
You can only select the default security policies for HTTPS listeners added to a shared load balancer.
Adding a Default Security Policy
- Go to the load balancer list page.
- On the displayed page, locate the load balancer and click its name.
- Under Listeners, click Add Listener.
- On the Add Listener page, set Frontend Protocol to HTTPS.
- Expand Advanced Settings and select a default security policy.
Table 1 lists the default security policies supported by shared load balancers.
Table 1 Default security policies Name
TLS Versions
Cipher Suites
TLS-1-0
TLS 1.2
TLS 1.1
TLS 1.0
- ECDHE-RSA-AES256-GCM-SHA384
- ECDHE-RSA-AES128-GCM-SHA256
- ECDHE-ECDSA-AES256-GCM-SHA384
- ECDHE-ECDSA-AES128-GCM-SHA256
- AES128-GCM-SHA256
- AES256-GCM-SHA384
- ECDHE-ECDSA-AES128-SHA256
- ECDHE-RSA-AES128-SHA256
- AES128-SHA256
- AES256-SHA256
- ECDHE-ECDSA-AES256-SHA384
- ECDHE-RSA-AES256-SHA384
- ECDHE-ECDSA-AES128-SHA
- ECDHE-RSA-AES128-SHA
- ECDHE-RSA-AES256-SHA
- ECDHE-ECDSA-AES256-SHA
- AES128-SHA
- AES256-SHA
TLS-1-1
TLS 1.2
TLS 1.1
TLS-1-2
TLS 1.2
TLS-1-2-Strict
TLS 1.2
- ECDHE-RSA-AES256-GCM-SHA384
- ECDHE-RSA-AES128-GCM-SHA256
- ECDHE-ECDSA-AES256-GCM-SHA384
- ECDHE-ECDSA-AES128-GCM-SHA256
- AES128-GCM-SHA256
- AES256-GCM-SHA384
- ECDHE-ECDSA-AES128-SHA256
- ECDHE-RSA-AES128-SHA256
- AES128-SHA256
- AES256-SHA256
- ECDHE-ECDSA-AES256-SHA384
- ECDHE-RSA-AES256-SHA384
- Shared load balancers support TLS 1.2 or earlier versions.
- The above table lists the cipher suites supported by ELB. Generally, clients also support multiple cipher suites. In actual use, the cipher suites supported by ELB and clients are used, and the cipher suites supported by ELB take precedence.
- Confirm the configurations and go to the next step.
Differences Among Security Policies
Security Policy |
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 |
hybrid-policy-1-0 |
---|---|---|---|---|---|---|---|---|---|
TLS version |
|||||||||
Protocol-TLS 1.3 |
N/A |
N/A |
N/A |
N/A |
N/A |
Supported |
Supported |
Supported |
N/A |
Protocol-TLS 1.2 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Protocol-TLS 1.1 |
Supported |
Supported |
N/A |
Supported |
N/A |
Supported |
N/A |
N/A |
Supported |
Protocol-TLS 1.0 |
Supported |
N/A |
N/A |
Supported |
N/A |
Supported |
N/A |
N/A |
N/A |
Cipher suite |
|||||||||
EDHE-RSA-AES128-GCM-SHA256 |
Supported |
Supported |
Supported |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
ECDHE-RSA-AES256-GCM-SHA384 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
ECDHE-RSA-AES128-SHA256 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
ECDHE-RSA-AES256-SHA384 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
AES128-GCM-SHA256 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
N/A |
N/A |
Supported |
AES256-GCM-SHA384 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
N/A |
N/A |
Supported |
AES128-SHA256 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
N/A |
N/A |
Supported |
AES256-SHA256 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
N/A |
N/A |
Supported |
ECDHE-RSA-AES128-SHA |
Supported |
Supported |
Supported |
Supported |
N/A |
Supported |
N/A |
N/A |
Supported |
ECDHE-RSA-AES256-SHA |
Supported |
Supported |
Supported |
Supported |
N/A |
Supported |
N/A |
N/A |
Supported |
AES128-SHA |
Supported |
Supported |
Supported |
Supported |
N/A |
Supported |
N/A |
N/A |
Supported |
AES256-SHA |
Supported |
Supported |
Supported |
Supported |
N/A |
Supported |
N/A |
N/A |
Supported |
ECDHE-ECDSA-AES128-GCM-SHA256 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
ECDHE-ECDSA-AES128-SHA256 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
ECDHE-ECDSA-AES128-SHA |
Supported |
Supported |
Supported |
Supported |
N/A |
Supported |
N/A |
N/A |
Supported |
ECDHE-ECDSA-AES256-GCM-SHA384 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
ECDHE-ECDSA-AES256-SHA384 |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
ECDHE-ECDSA-AES256-SHA |
Supported |
Supported |
Supported |
Supported |
N/A |
Supported |
N/A |
N/A |
Supported |
ECDHE-RSA-AES128-GCM-SHA256 |
N/A |
N/A |
N/A |
Supported |
N/A |
Supported |
Supported |
Supported |
Supported |
TLS_AES_256_GCM_SHA384 |
N/A |
N/A |
N/A |
N/A |
N/A |
Supported |
Supported |
Supported |
N/A |
TLS_CHACHA20_POLY1305_SHA256 |
N/A |
N/A |
N/A |
N/A |
N/A |
Supported |
Supported |
Supported |
N/A |
TLS_AES_128_GCM_SHA256 |
N/A |
N/A |
N/A |
N/A |
N/A |
Supported |
Supported |
Supported |
N/A |
TLS_AES_128_CCM_8_SHA256 |
N/A |
N/A |
N/A |
N/A |
N/A |
Supported |
Supported |
Supported |
N/A |
TLS_AES_128_CCM_SHA256 |
N/A |
N/A |
N/A |
N/A |
N/A |
Supported |
Supported |
Supported |
N/A |
DHE-RSA-AES128-SHA |
N/A |
N/A |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
N/A |
DHE-DSS-AES128-SHA |
N/A |
N/A |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
N/A |
CAMELLIA128-SHA |
N/A |
N/A |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
N/A |
EDH-RSA-DES-CBC3-SHA |
N/A |
N/A |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
N/A |
DES-CBC3-SHA |
N/A |
N/A |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
N/A |
ECDHE-RSA-RC4-SHA |
N/A |
N/A |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
N/A |
RC4-SHA |
N/A |
N/A |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
N/A |
DHE-RSA-AES256-SHA |
N/A |
N/A |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
N/A |
DHE-DSS-AES256-SHA |
N/A |
N/A |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
N/A |
DHE-RSA-CAMELLIA256-SHA |
N/A |
N/A |
N/A |
Supported |
N/A |
N/A |
N/A |
N/A |
N/A |
ECC-SM4-SM3 |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
Supported |
ECDHE-SM4-SM3 |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
N/A |
Supported |
Changing a Security Policy
When you change a security policy, ensure that the security group rules configured for backend servers allow traffic from 100.125.0.0/16 to backend servers and allows ICMP packets for UDP health checks. Otherwise, backend servers will be considered unhealthy, resulting in service interruptions.
- Go to the load balancer list page.
- On the displayed page, locate the load balancer and click its name.
- Click Listeners, locate the listener, and click its name.
- On the Summary tab, click Edit on the top right.
- In the Edit dialog box, expand Advanced Settings and change the security policy.
- Click OK.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot