Choosing a Two-Factor Authentication System
Nov 28, 2012Matthew Prince
Summary
This post details Cloudflare's exploration and adoption of two-factor authentication (2FA) to enhance account security. It highlights the decision to implement Time-based One-time Password (TOTP) based solutions, specifically favoring Authy over alternatives like SMS or Google Authenticator due to security concerns (e.g., carrier network insecurity, Google's past flaws, inability to revoke tokens, sync issues, and cumbersome phone upgrades). The post emphasizes Authy's superior implementation, including better token revocation, clock synchronization, seamless phone upgrades, and stronger cryptographic standards, ultimately leading to the rollout of 2FA as a feature for all customers.
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