CloudFlare, PRISM, and Securing SSL Ciphers
Jun 12, 2013Matthew Prince
Summary
This post addresses concerns about government surveillance programs like PRISM and their potential impact on SSL/TLS security. It explains how Cloudflare's default use of 2048-bit keys and preference for ECDHE cipher suites (which use a different private key for each session) significantly enhances security against potential decryption of historical traffic. The post also discusses the technical feasibility of breaking SSL keys and suggests alternative theories for how surveillance might occur, emphasizing Cloudflare's commitment to trust, security, and transparency.
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