Before you start

You must configure Brute Force Protection and set up logs and alerts for thresholds.
Attackers can employ brute force techniques (TT1110) to gain access to sensitive systems. Often unsophisticated, most brute-force attacks are easily defeated, but defense can be resource-intensive. Below are some common brute-force attack techniques and guidance on how to identify and investigate potential attacks against your tenant.

​
Find log events of interest

Before blocking IPs or otherwise responding to an attack, identify breaches by sifting through the log messages of interest. The attack may be coming from a limited set of IPs or from a single autonomous system number or country. The following log event types are relevant when investigating a brute force attack. They are found in the Auth0 tenant logs.

​
Password guessing

Attackers with little prior knowledge of your tenant’s policies can repeatedly attempt to guess passwords (TT1110.001) in an attempt to access accounts. Since attackers are merely guessing whether a user exists with an unknown password, your Auth0 logs will display many fp, fu and fcoa log events. For more information, read Auth0’s Breached Password playbook.

​
Password spraying

Attackers try many commonly-used passwords (TT1110.003) to gain access to legitimate user accounts. These often trip Auth0’s brute force protections and leave many fp, fu, and fcoa log events in your logs.

​
Credential stuffing

Credential stuffing (TT1110.004) is most effective when used against tenants that employ passwords but no additional factors. By taking advantage of password leaks and attempting to log in to a victim’s account using a dictionary of leaked passwords, credential stuffing attacks generate fp log events and pwd_leak log events.

​
Signup attacks

Attackers can attempt to sign up for a large number of accounts in a short window of time as part of a username enumeration attack (T1087), where attackers attempt to see whether a user account exists on your tenant or signup fraud campaigns. The goal is to create many accounts to take advantage of signup incentives or create aged accounts for later attacks. Signup attacks generate fs, ss and signup_pwd_leak log events.

​
Detection using the Auth0 Management API

The Auth0 Management API allows tenant logs to be queried using log search query syntax for log types in the time range of interest. More advanced use cases are supported by log aggregation tooling like data warehouses or SIEMs by leveraging Auth0 log streams. When using the Auth0 , the potential attack timeframe is specified as date:[startdate to enddate] in YYYY-MM-DD format. For example, 2024-10-01. Use * to represent the current date. By limiting the time of interest to a potential attack window, you can retrieve all log events of the type you’re interested. Below is an example query that searches for brute force attacks from October 1, 2024 to the present: 
date:[2024-10-01 TO *] AND (type:"f" OR type:"fu" OR type:"fp" OR type:"pwd_leak" OR type:"limit_wc" OR type:"limit_sul" OR type:"limit_mu" OR type:"fcoa")
For advanced analysis or to correlate login activities with applications outside Auth0, enable log streaming to the external tool of your choice. Review the Management API documentation to understand how to extract a subset of log events from your tenant for analysis.

​
Mitigation strategies

For optimal protection from attacks, consider the following strategies:
  • Enable Breached Password Detection or Credential Guard to protect against breached credentials with minimal user friction, noting that neither protects against dictionary attacks.
  • Activate CAPTCHA for one or more flows and increase CAPTCHA frequency as needed, but remember that CAPTCHA is a deterrent, not a solution.
  • Change your CAPTCHA provider if attackers bypass your current CAPTCHA or consider migrating to Auth0’s Auth Challenge or another supported provider.
  • Temporarily disable account creation by everyone, including malicious actors.
  • Change your web application firewall rules with an edge provider, or use tenant access control lists, to block abusive IPs, autonomous system numbers, geographic locations, TLS clients, or HTTP header elements like user-agent strings, and consider employing a reverse proxy.
  • Tighten Brute Force and Suspicious IP thresholds to reduce allowed connection limits and mitigate brute-force attacks.
  • Disable unused endpoints by modifying your Cross-Origin Authentication settings if you see frequent fcoa and scoa events, remembering that Auth0 does not recommend using cross-origin authentication.
  • Enforce step-up MFA for compromised accounts, up to and including requiring for potentially compromised accounts.
  • Migrate to stronger MFA options by replacing SMS or voice-based MFA with OTP or Webauthn to mitigate SMS pumping or toll fraud attacks.
  • Implement SMS/voice provider security fraud protection like Twilio’s Preventing Fraud in Verify when using SMS/voice MFA.