Keeping our users safe
Feb 16, 2018Marc Rogers
Summary
This post details Cloudflare's current practices for storing and handling user credentials (passwords and API keys) to protect against common attacks. It describes the use of bcrypt for password hashing, AES/SHA256/entropy for API key generation, audit logs for access, and HTTPS for in-transit security. It also introduces CAPTCHA challenges for viewing API keys and discusses future plans for scoped API keys and IP restrictions.
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