Account Takeover Protection and WAF mitigations to help stop Global Brute Force Campaigns
This post details the immediate rollout of WAF mitigations and the expansion of the Exposed Credential Check feature to all paid plans in response to a global brute force campaign. New WAF rules (100197 and 100197B) are introduced to block reGeorg web shell variants. The Exposed Credential Check feature, previously in beta, is now generally available for Pro plans and above, providing a header (`Exposed-Credential-Check: 1`) to origin servers when compromised credentials are detected. It supports common application types like WordPress, Joomla, and Microsoft Exchange, and can be enabled via a support ticket for immediate activation. Additional recommended mitigations include MFA, account lockout, managed IP lists for open proxies, and Super Bot Fight Mode.
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