Configuring PCI DSS/3DS Compliance Check and TLS
In business scenarios where sensitive data is processed and transmitted, enterprises face data leakage, fraud, and compliance risks. The basic protection cannot meet PCI DSS/3DS requirements or defend against transport-layer attacks. WAF PCI DSS/3DS compliance check and TLS configuration can enable a three-layer protection system: compliance enforcement, encrypted transmission, and fraud interception.
Principles
Key concepts
- Transport Layer Security (TLS) is a cryptographic protocol that ensures confidentiality and data integrity for communications between applications. It is the foundational security layer for HTTPS. HTTPS is the protocol that combines TLS and HTTP. It provides encrypted transmission and identity authentication to ensure secure network communication.
- Cipher suite: a set of cryptographic algorithms negotiated by the client and server during the TLS handshake. It determines how to encrypt data, verify identities, and ensure data integrity.
-
PCI DSS/3DS certification check: The Payment Card Industry Data Security Standard (PCI DSS) and the 3-D Secure (PCI 3DS) are security standards designed to protect sensitive payment data, such as credit card information, during transmission and processing in the finance and e-commerce industries. After this check is enabled, WAF forcibly sets the minimum TLS version to TLS v1.2 to meet compliance requirements.
Default WAF configuration
The minimum TLS version and cipher suite need to be configured.
Minimum TLS version
To meet the compatibility requirements of most websites, TLS v1.0 is selected as the minimum TLS version by default. You can select a more secure TLS version by referring to Table 1. You can select TLS v1.0, TLS v1.1, or TLS v1.2. Later versions are more secure than earlier ones.
| Scenario | Minimum TLS Version (Recommended) | Protection Effect |
|---|---|---|
| Websites that handle critical business data, such as sites used in banking, finance, securities, and e-commerce. | TLS v1.2 | WAF automatically blocks website access requests that use TLS v1.0 or TLS v1.1. |
| Websites with basic security requirements, for example, small and medium-sized enterprise websites. | TLS v1.1 | WAF automatically blocks website access requests that use TLS v1.0. |
| Client applications with no special security requirements | TLS v1.0 | Requests using any TLS protocols can access the website. |
Cipher suites
To balance security and compatibility, the default cipher suite is Secure cipher suite. If the request does not carry SNI, WAF uses the default Classic cipher suite.
WAF supports RSA certificates (SSL/TLS certificates generated based on the RSA asymmetric cryptographic algorithm) and ECDSA certificates (SSL/TLS certificates based on elliptic curve cryptography [ECC/ECDSA]). RSA certificates only support cipher suites or algorithms that include RSA in their name. Similarly, ECDSA certificates only support algorithms that include ECDSA.
You can select a more secure cipher suite by referring to Table 2.
| Cipher Suite Name | Cryptographic Algorithm Supported | Standard Cryptographic Algorithm Supported | Cryptographic Algorithm Not Supported | Description |
|---|---|---|---|---|
| Classic cipher suite |
| The support for different TLS versions is as follows:
|
| |
| Cipher suite 1 |
| The support for different TLS versions is as follows:
|
| Recommended configuration. |
| Cipher suite 2 |
| The support for different TLS versions is as follows:
| - | |
| Cipher suite 3 |
| The support for different TLS versions is as follows:
|
| |
| Cipher suite 4 |
| The support for different TLS versions is as follows:
|
| |
| Cipher suite 5 |
| The support for different TLS versions is as follows:
|
| Supported algorithms: RSA-AES-CBC only |
| Cipher suite 6 |
| The support for different TLS versions is as follows:
| - |
|
| Security cipher suite |
| The support for different TLS versions is as follows:
|
| This cipher suite supports all algorithms in cipher suite 1, except for the CBC algorithm. Recommended. This cipher suite can meet security requirements in most scenarios.
|
| Cipher suite 8 |
| The support for different TLS versions is as follows:
|
| Supports AES-GCM, providing strong encryption and data integrity protection.
|
Browser and client compatibility
The TLS cipher suites in WAF are compatible with all browsers and clients of later versions but are incompatible with some browsers of earlier versions. Table 3 lists the incompatible browsers and clients if the TLS v1.0 protocol is used.
It is recommended that compatibility tests be carried out on the service environment to ensure service stability.
| Browser/Client | Classic Cipher Suite | Cipher Suite 1 | Cipher Suite 2 | Cipher Suite 3 | Cipher Suite 4 | Cipher Suite 5 | Cipher Suite 6 | Security Cipher Suite | Cipher Suite 8 |
|---|---|---|---|---|---|---|---|---|---|
| Google Chrome 63 /macOS High Sierra 10.13.2 | Not compatible | Compatible | Compatible | Compatible | Not compatible | Compatible | Compatible | Compatible | √ |
| Google Chrome 49/ Windows XP SP3 | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Compatible | Compatible | Not compatible | √ |
| Internet Explorer 6 /Windows XP | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible |
| Internet Explorer 8 /Windows XP | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible |
| Safari 6/iOS 6.0.1 | Compatible | Compatible | Not compatible | Compatible | Compatible | Compatible | Compatible | Not compatible | √ |
| Safari 7/iOS 7.1 | Compatible | Compatible | Not compatible | Compatible | Compatible | Compatible | Compatible | Compatible | Compatible |
| Safari 7/OS X 10.9 | Compatible | Compatible | Not compatible | Compatible | Compatible | Compatible | Compatible | Compatible | Compatible |
| Safari 8/iOS 8.4 | Compatible | Compatible | Not compatible | Compatible | Compatible | Compatible | Compatible | Compatible | Compatible |
| Safari 8/OS X 10.10 | Compatible | Compatible | Not compatible | Compatible | Compatible | Compatible | Compatible | Compatible | Compatible |
| Internet Explorer 7/Windows Vista | Compatible | Compatible | Not compatible | Compatible | Compatible | Not compatible | √ | Not compatible | √ |
| Internet Explorer 8, 9, or 10 /Windows 7 | Compatible | Compatible | Not compatible | Compatible | Compatible | Not compatible | √ | Not compatible | √ |
| Internet Explorer 10 /Windows Phone 8.0 | Compatible | Compatible | Not compatible | Compatible | Compatible | Not compatible | √ | Not compatible | √ |
| Java 7u25 | Compatible | Compatible | Not compatible | Compatible | Compatible | Not compatible | √ | Not compatible | √ |
| OpenSSL 0.9.8y | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | Not compatible | √ |
| Safari 5.1.9/OS X 10.6.8 | Compatible | Compatible | Not compatible | Compatible | Compatible | Not compatible | √ | Not compatible | √ |
| Safari 6.0.4/OS X 10.8.4 | Compatible | Compatible | Not compatible | Compatible | Compatible | Not compatible | √ | Not compatible | √ |
- If you enable PCI DSS compliance certification check, the TLS configurations are automatically changed to:
- Minimum TLS Version: TLS v1.2 or later
- Cipher Suite: Cipher suite 2 (EECDH+AESGCM:EDH+AESGCM)
- If you enable PCI 3DS compliance certification check, the minimum TLS version is TLS v1.2 or later.
- If you enable PCI DSS compliance certification check, the minimum TLS version and cipher suite cannot be changed. If you need to change the minimum TLS version or cipher suite, disable the compliance certification check.
- If you enable PCI 3DS compliance certification check, the minimum TLS version cannot be changed and the compliance certification check cannot be disabled.
- Enabling PCI DSS/3DS compliance certification checks may affect the access of the browser of an earlier version. We recommend accessing potential impact on your services before enabling them.
Impact on the System
- If you enable the PCI DSS certification check:
- The minimum TLS version and cipher suite are automatically set to TLS v1.2 and EECDH+AESGCM:EDH+AESGCM, respectively, and cannot be changed.
- To change the minimum TLS version and cipher suite, disable the check.
- If you enable the PCI 3DS certification check:
- The minimum TLS version is automatically set to TLS v1.2 and cannot be changed.
- The check cannot be disabled.
Constraints
| Function | Constraint |
|---|---|
| Access mode restrictions |
|
| Client Protocol |
|
| Enterprise Project | If you have enabled enterprise projects, ensure that you have all operation permissions for the project where your WAF instance locates. Then, you can select the enterprise project from the Enterprise Project drop-down list and configure PCI DSS or PCI 3DS and TLS for the domain names in the selected enterprise project. |
Prerequisites
You have added the website to WAF and selected HTTPS for Client Protocol.
Configuring PCI DSS/3DS Compliance Check and TLS
- Log in to the WAF console.
- Click
in the upper left corner and select a region or project. - (Optional) If you have enabled the enterprise project function, in the upper part of the navigation pane on the left, select your enterprise project from the Filter by enterprise project drop-down list. Then, WAF will display the related security data in the enterprise project on the page.
- In the navigation pane on the left, choose .
- On the Protected Objects page, click the target domain name.
- In the Basic Information area, select PCI DSS or PCI 3DS in the Compliance Certification area to enable the corresponding compliance certification check.
- If you enable PCI DSS compliance certification check, the minimum TLS version and cipher suite cannot be changed. If you need to change the minimum TLS version or cipher suite, disable the compliance certification check.
- If you enable PCI 3DS compliance certification check, the minimum TLS version cannot be changed and the compliance certification check cannot be disabled.
- Enabling PCI DSS/3DS compliance certification checks may affect the access of the browser of an earlier version. We recommend accessing potential impact on your services before enabling them.
- PCI DSS
- Enabling PCI DSS Compliance Certification check
If you select PCI DSS, by default, Minimum TLS Version is set to TLS v1.2 and Cipher Suite to Cipher suite 2, and TLS Configuration cannot be modified.
Figure 1 Enabling PCI DSS Compliance Certification check
- Disabling PCI DSS Compliance Certification check
To modify the TLS configuration, deselect PCI DSS.
After disabling PCI DSS Compliance Certification, you can change the minimum TLS version and cipher suite. For details, see 7.
- Enabling PCI DSS Compliance Certification check
- PCI 3DS
- Enabling PCI 3DS Compliance Certification check
If you select PCI 3DS, Minimum TLS Version is set to TLS v1.2 by default and cannot be changed. Cipher Suite is set to Cipher suite 2 by default and can be changed.
Figure 2 Enabling PCI 3DS Compliance Certification check
- PCI 3DS compliance certification cannot be disabled after being enabled.
- Enabling PCI 3DS Compliance Certification check
- Configure TLS. If PCI DSS or PCI 3DS Compliance Certification check is not enabled, TLS can be configured.
Click Modify next to TLS Configuration. On the TLS Configuration panel, select the minimum TLS version and cipher suite.
- Before you configure TLS, check the TLS version of your website.
- For details about the minimum TLS version and cipher suite, see TLS.
Figure 3 Configuring TLS
If the configuration works, requests using TLS versions earlier than v1.2 will fail, and requests using TLS v1.2 or later will succeed.
What is your overall rating for this page?
Thank 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