Learn how to configure Cloudflare to meet PCI scan requirements and understand what mitigations Cloudflare has in place for earlier versions of TLS/SSL.
Overview
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. Below, you can review our list of recommended Cloudflare SSL configurations for PCI compliance.
Also see what mitigations Cloudflare implements against vulnerabilities for TLS 1.0 and 1.1.
Recommended Cloudflare SSL configurations for PCI compliance
For Free, Business and Enterprise domains:
- Set the Minimum TLS Version to TLS 1.2 or newer
For Pro domains:
- Purchase a Dedicated SSL certificate or upgrade to a Business plan and upload a Custom SSL certificate
- Disable Universal SSL
- Set the Minimum TLS Version to TLS 1.2 or newer
Set Minimum TLS Version to 1.2
To configure your Cloudflare domain to only allow connections using TLS 1.2 or newer protocols:
1. Log in to the Cloudflare dashboard.
2. Click the appropriate Cloudflare account for the domain.
3. Ensure the proper domain is selected.
4. Click on the Cloudflare Crypto app.
5. Scroll to the Minimum TLS Version section.
6. Select TLS 1.2.
Cloudflare mitigations against known TLS vulnerabilities
There are several mitigations Cloudflare performs against known vulnerabilities for TLS versions prior to 1.2. For example, Cloudflare does not support:
- Header compression in TLS
- Header compression in SPDY 3.1
- RC4
- SSL 3.0
- Renegotiation with clients
- DHE ciphersuites
- Export-grade ciphers
Cloudflare mitigations protect against several attacks:
- CRIME
- BREACH
- POODLE
- RC4 Cryptographic Weaknesses
- SSL Renegotiation Attack
- Protocol Downgrade Attacks
- FREAK
- LogJam
- 3DES is disabled entirely for TLS 1.1 and 1.2 and Cloudflare implements mitigations for TLS 1.0
Cloudflare provides additional mitigations for:
- Heartbleed
- Lucky Thirteen
- CCS injection vulnerability
Cloudflare has patched all servers against these vulnerabilities. Also, the Cloudflare WAF has rules to mitigate several of these vulnerabilities including Heartbleed and ShellShock.
HTTP/2 and HTTP/1.1 Cleartext Detection (Paid Plans Only):
Use Cloudflare WAF rule 100015 to restrict connections to only port 80 and 443 if you aren't using other open Cloudflare ports. You can find WAF rule 100015 in the Cloudflare UI for your domain:
- Click the Cloudflare Firewall app.
- Click the Managed Rules tab.
- Click Advanced under the Cloudflare Managed Rules section..
- Enter 100015 in the search field and click Search.
- Set the Mode of rule 100015 to Block.
Once enabled, the additional Cloudflare ports are still open, but no data is sent to those ports as the WAF blocks the request with an HTTP 403 response.
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.
Web Application Cookies Not Marked Secure
The Cloudflare cfduid cookie is used for security purposes and cannot be disabled. The cfduid cookie doesn't contain any confidential or sensitive information and is used to note whether a user has passed javascript challenges such as used by Under Attack Mode.
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:
- attacker must collect 32GB of data from a single TLS session
- Cloudflare forces new TLS 1.0 session keys on the affected 3DES cipher well before 32GB of data is collected