Brute-Force Protection (2024)

Brute-force protection safeguards against a single IP address attacking a single user account. When a given IP address tries and fails multiple times to log in as the same user, brute-force protection:

• Blocks the suspicious IP address from logging in as that user.

• Sends a notification to the affected user.

If an IP address is blocked due to brute-force protection, it remains blocked until one of these events occurs:

• An administrator removes the block.

• An administrator raises the Brute Force Threshold described below.

• Thirty (30) days pass from the last failed login attempt.

  See Also

  What is a Brute Force | Common Tools & Attack Prevention | ImpervaBrute Force Attacks: Techniques, Types & Prevention | SplunkHow to Stop Brute Force Attacks in Their TracksHow do you prevent or mitigate brute force attacks on encrypted data?

• The affected user selects the unblock link in the email notification (if configured).

• The affected user changes their password (on all linked accounts).

Auth0 strongly recommends that you do not disable brute-force protection for the connection. If you disable it, you can enable it again using the Dashboard.

1. Go to Dashboard > Security > Attack Protection and select Brute-force Protection. Enable the toggle at the top of the page if it is disabled.

   

2. In the Detection section:

   1. Under Brute Force Threshold, select Default to use the standard limit of 10 maximum attempts, or select Custom to set the limit of maximum attempts to a value between 1 and 100.

   2. Under Manage IP Addresses, enter the list of trusted IP addresses in the IP AllowList field. Brute-force protection will not be enforced for login attempts originating from these IP addresses.

3. In the Response section:

   1. Under Block Settings, enable the Block Brute-force Logins toggle to block attempts from suspicious IP addresses to safeguard against brute-force attacks that occur from a single IP address and target a single user account.

   2. Under Block Settings, enable Account Lockout to trigger blocks irrespective of IP address. When this setting is enabled and a user consecutively attempts and fails to login, future attempts to log in from that user from any IP address will be blocked. You can adjust maximum attempts under Brute Force Threshold. By default, the Account Lockout toggle is disabled.

   3. Under Notifications, enable the Send notifications to the affected users toggle to send an email notification to the user when their account has been blocked.

4. Click Save.

If Send notifications to the affected users is enabled, Auth0 sends an SMS or email notification to a user when their account has been blocked.

Auth0 sends an SMS to the user if they use a phone identifier in the login flow. SMS notifications are limited at a maximum of 1 per hour per identifier.

Auth0 sends an email to the user if they use a non-phone identifier in the login flow. Email notifications are limited at a maximum of 1 per hour per unique IP address.

By default, email notifications contain a link that allows the user to unblock their account. To learn more, read Customize Blocked Account Emails.

Because brute-force protection depends on the IP address of the user, the following use cases require additional configuration:

• ROPG on the backend: Using this call does not get the IP address of the user; however, to make brute-force protection work correctly, you can configure your application and send the IP address of the user as part of the request.

• User authentication from the same IP address: Users who are behind a proxy are more likely to reach set limits and trigger brute-force protection.

To learn more, read Avoid Common Issues with Resource Owner Password Flow and Attack Protection.

• Flexible Identifiers and Attributes
• Activate and Configure Attributes for Flexible Identifiers
• Customize Blocked Account Emails
• View Attack Protection Log Events
• User/Password Authentication Rate Limits