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

Para os domínios dos planos Gratuito, Business e Empresarial:

• Set the Minimum TLS Version to TLS 1.2 or newer

Para os domínios do plano Pro:

• Adquira um Certificado SSL Dedicado ou faça um upgrade para o Plano Business e carregue um Certificado SSL Personalizado
• Desative o certificado SSL Universal
• 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. Clique no aplicativo SSL/TLS da Cloudflare.

5. Role na tela até a seção Versão Mínima do TLS.

6. Selecione 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. Clique no aplicativo Firewall da Cloudflare.
2. Clique na guia Regras Gerenciadas.
3. Clique em Avançadas na seção Regras Gerenciadas da Cloudflare.
4. Digite 100015 no campo de busca e clique em Pesquisar.
5. Configure o Modo da regra 100015 como Bloquear.

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

O cookie cfduid da Cloudflare é usado para fins de segurança e não pode ser desativado. O cookie cfduid não contém nenhuma informação confidencial ou sensível e é usado para observar que um usuário foi aprovado em desafios javascript como os utilizados pelo Modo Estou sob Ataque.

Sweet32 (CVE-2016-2183)

Uma vulnerabilidade no uso do algoritmo de criptografia Triplo DES (3DES) no protocolo TLS (Segurança da Camada de Transporte). No momento, o ataque Sweet32 é uma "prova de conceito" e não existe nenhum exemplo conhecido no mundo real. A Cloudflare mitigou manualmente a vulnerabilidade do TLS 1.0 da seguinte maneira:

• 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

• Compatibilidade da Cloudflare com o protocolo, cifras e navegadores SSL: entenda quais cifras e protocolos TLS são suportados pela Cloudflare. Saiba quais navegadores são compatíveis com os certificados SSL da Cloudflare e quais certificados intermediários e raiz são usados para assinar os certificados da 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.