Tracking our SSL configuration
May 3, 2014John Graham-Cumming
Summary
This post details Cloudflare's proactive approach to managing and evolving its SSL/TLS configuration in response to emerging security threats. It introduces a new mechanism for tracking these changes via a GitHub repository (sslconfig) and highlights specific security vulnerabilities addressed, such as Lucky 13, BEAST, and RC4 biases. The post also emphasizes the adoption of advanced cryptographic techniques like ECDSA and Perfect Forward Secrecy to enhance customer security.
More from the Website Security & Threat Management trail
- We tested our own WAF with frontier AI models. Here’s what we found
- When scanners miss the attack: how Cloudflare Client-Side Security protects storefronts
- Introducing automatic remediation policies with Cloudflare CASB
- Introducing context-aware vulnerability discovery and remediation with Cloudflare Managed Defense and OpenAI Daybreak Models
- Introducing Adaptive Intelligence: undermining the economics of every bot attack