CloudflareNicole JustusAnnouncement
Cloudflare’s new Account Abuse Protection dashboard helps fraud teams investigate account abuse by moving beyond stateless identity checks to a stateful trust model. The dashboard uses cryptographically hashed identifiers, called Hashed User IDs, created from customer-provided identifiers like email or username, to anchor account activity across login and signup events. It provides an account population overview with metrics like total events, unique IPs, and devices to spot anomalies such as leaked credential matches or unusual login failure rates, then allows analysts to filter and drill into individual accounts. Each account view shows historical behavioral, network, and device signals, enabling teams to reconstruct events and decide on responses like WAF rules. The dashboard also introduces two new roles—Account Abuse Protection and Account Abuse Protection PII—to enforce least privilege for dashboard access and PII exposure.
Traditional identity verification checks are stateless and can be bypassed by AI-generated synthetic media and stolen credentials. Cloudflare’s Account Abuse Protection introduces a stateful trust model that evaluates account behavior over time using edge-generated signals.
The dashboard uses Hashed User IDs, cryptographically hashed from customer-provided identifiers, to aggregate login and signup events with network and device signals. It provides an account population overview for spotting anomalies, filters to narrow investigations, and individual account views with event logs. Two new roles control access to the dashboard and PII.
Account Abuse Protection uses Hashed User IDs to create privacy-preserving, per-domain account profiles from login and signup events.
The dashboard provides an investigative funnel from population-level metrics to individual account event logs, enabling reconstruction of abuse patterns.
Two new roles—Account Abuse Protection and Account Abuse Protection PII—allow customers to enforce least privilege access to the dashboard and sensitive data.
Customers configure an identifier like email or username from their login flow. Cloudflare cryptographically hashes that value to create a per-domain Hashed User ID, which anchors account activity without exposing the original identifier.
The dashboard starts with an account population overview showing total events, unique IPs, devices, and country/ASN breakdowns. Analysts can filter to suspicious cohorts and then drill into individual account views with event logs and historical signals.
After reviewing the account's event history and signals, analysts can use the Hashed User ID in a WAF rule to challenge or block future requests associated with that identifier.
Summaries are generated from the original by a language model. Check the original before relying on it.
See the idea
A tradeoff view of blockchain: a shared ledger buys verifiable settlement between parties that do not share an operator, and charges throughput, latency, and governance in return.
A model that passes benchmarks can still defect only on a trigger. This explainer maps the trade-off between deeper backdoor verification and the friction, latency, and cost it adds.
Keep reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
One useful email. Unsubscribe anytime.
