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

Pour les domaines relevant des offres Free, Business et Enterprise :

• Set the Minimum TLS Version to TLS 1.2 or newer

Pour les domaines Pro :

• Achetez un certificat SSL dédié ou passez à une offre Business et chargez un certificat SSL personnalisé
• Désactivez le SSL universel
• 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. Ouvrez l'application Cloudflare SSL/TLS.

5. Desendez jusqu'à la rubrique Version TLS minimale.

6. Sélectionnez 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:

1. Header compression in TLS
2. Header compression in SPDY 3.1
3. RC4
4. SSL 3.0
5. Renegotiation with clients
6. DHE ciphersuites
7. 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:

1. Ouvrez l'application Cloudflare Firewall.
2. Ouvrez l'onglet Règles gérées.
3. Cliquez sur Avancées dans la rubrique Règles gérées Cloudflare.
4. Saisissez 100015 dans le champ de recherche et cliquez sur Rechercher.
5. Définissez le Mode de la règle 100015 sur Bloquer.

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

Le cookie Cloudflare cfduid est utilisé à des fins de sécurité et ne peut être désactivé. Le cookie cfduid ne contient pas de données confidentielles ou sensibles et sert à vérifier si un utilisateur a passé les tests javascript comme ceux utilisés par le mode Je subis une attaque.

Sweet32 (CVE-2016-2183)

Le protocole TLS (Transport Layer Security) est une vulnérabilité de l'algorithme de chiffrement Triple DES (3DES). Sweet32 n'est pour le moment qu'une attaque spéculative, aucun cas réel n'a été signalé à ce jour. Cloudflare a atténué manuellement la vulnérabilité du TLS 1.0 de la manière suivante :

• 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

Related resources

More articles on TLS, cipher, browser, and protocol support

undefined

• Prise en charge du chiffrement, du navigateur et du protocole SSL Cloudflare - Découvrez quels sont les systèmes de chiffrement et les protocoles TLS pris en charge par Cloudflare. Découvrez quels navigateurs les certificats SSL Cloudflare prennent en charge et quels certificats intermédiaires et racine sont utilisés pour signer les certificats Cloudflare.
• Using Minimum TLS Version in Cloudflare SSL/TLS - Transport Layer Security (TLS) guarantees encrypted communications between a client and a web server via HTTPS. It replaces the now deprecated Secured Sockets Layer (SSL) protocol.