INTEGRITY Cloudflare Docs

← Ssl / ssl / reference

PCI compliance and vulnerabilities mitigation

Both TLS 1.0 and TLS 1.1 are insufficient for protecting information due to known vulnerabilities. Specifically for Cloudflare customers, the primary impact of PCI is that TLS 1.0 and TLS 1.1 are insufficient to secure payment card related traffic.

PCI standards recommend using TLS 1.2 or higher. Refer to Compliance standards for a list of recommended cipher suites.

Cloudflare also implements mitigations against known vulnerabilities for TLS 1.0 and 1.1.

Set Minimum TLS Version to 1.2

To configure your Cloudflare domain to only allow connections using TLS 1.2 or newer protocols:

  1. In the Cloudflare dashboard, go to the Edge Certificates page.

    Go to Edge Certificates ↗

  2. For Minimum TLS Version, select TLS 1.2 or higher.

Refer to Minimum TLS version for more information about this setting and other setup options.

Known vulnerabilities mitigations

There are several mitigations Cloudflare performs against known vulnerabilities for TLS versions prior to 1.2. For example, Cloudflare does not support:

Cloudflare mitigations protect against several attacks:

Cloudflare provides additional mitigations for:

Cloudflare has patched all servers against these vulnerabilities. Also, the Cloudflare Web Application Firewall has managed rules that mitigate several of these vulnerabilities including Heartbleed and ShellShock.

Return of Bleichenbacher's Oracle Threat (ROBOT)

Security scans that note the presence of ROBOT while on Cloudflare are a false positive. Cloudflare checks padding in real time and swaps to a random session key if the padding is incorrect.

Sweet32 (CVE-2016-2183)

A vulnerability in the use of the Triple DES (3DES) encryption algorithm in the Transport Layer Security (TLS) protocol. Sweet32 is currently a proof of concept attack, there are no known examples of this in the wild. Cloudflare has manually mitigated the vulnerability for TLS 1.0 in the following manner: