Autentikasi dan sesi for Cloudflare

high5 checks

Authentication is the highest-value target on any site: credential stuffing, session fixation and CSRF all aim at the same door.

What Cloudflare must have

  • Login forms post over HTTPS with a CSRF token
  • Rate limiting and lockout on failed attempts
  • MFA available for privileged accounts
  • Passwords screened against known breach corpora
  • No account enumeration through error messages

How to fix it

  1. 1Add per-account and per-IP throttling
  2. 2Enforce MFA for admins and screen passwords with a k-anonymity API

Cloudflare context

CDN, DNS and WAF provider sitting in front of the origin.

Origin IPs must be firewalled to Cloudflare only, otherwise the WAF is bypassable by hitting the origin directly.