Preventing Brute Force Logins on Websites

Question

As a response to the recent Twitter hijackings and Jeff\'s post on Dictionary Attacks, what is the best way to secure your website against brute force login attacks?

Answer 1

This is an old post. However, I thought of putting my findings here so that it might help any future developer.

We need to prevent brute-force attack so that the attacker can not harvest the user name and password of a website login. In many systems, they have some open ended urls which does not require an authentication token or API key for authorization. Most of these APIs are critical. For example; Signup, Login and Forget Password APIs are often open (i.e. does not require a validation of the authentication token). We need to ensure that the services are not abused. As stated earlier, I am just putting my findings here while studying about how we can prevent a brute force attack efficiently.

Most of the common prevention techniques are already discussed in this post. I would like to add my concerns regarding account locking and IP address locking. I think locking accounts is a bad idea as a prevention technique. I am putting some points here to support my cause.

Account locking is bad

• An attacker can cause a denial of service (DoS) by locking out large numbers of accounts.
• Because you cannot lock out an account that does not exist, only valid account names will lock. An attacker could use this fact to harvest usernames from the site, depending on the error responses.
• An attacker can cause a diversion by locking out many accounts and flooding the help desk with support calls.
• An attacker can continuously lock out the same account, even seconds after an administrator unlocks it, effectively disabling the account.
• Account lockout is ineffective against slow attacks that try only a few passwords every hour.
• Account lockout is ineffective against attacks that try one password against a large list of usernames.
• Account lockout is ineffective if the attacker is using a username/password combo list and guesses correctly on the first couple of attempts.
• Powerful accounts such as administrator accounts often bypass lockout policy, but these are the most desirable accounts to attack. Some systems lock out administrator accounts only on network-based logins.
• Even once you lock out an account, the attack may continue, consuming valuable human and computer resources.
• Consider, for example, an auction site on which several bidders are fighting over the same item. If the auction web site enforced account lockouts, one bidder could simply lock the others' accounts in the last minute of the auction, preventing them from submitting any winning bids. An attacker could use the same technique to block critical financial transactions or e-mail communications.

IP address locking for a account is a bad idea too

Another solution is to lock out an IP address with multiple failed logins. The problem with this solution is that you could inadvertently block large groups of users by blocking a proxy server used by an ISP or large company. Another problem is that many tools utilize proxy lists and send only a few requests from each IP address before moving on to the next. Using widely available open proxy lists at websites such as http://tools.rosinstrument.com/proxy/, an attacker could easily circumvent any IP blocking mechanism. Because most sites do not block after just one failed password, an attacker can use two or three attempts per proxy. An attacker with a list of 1,000 proxies can attempt 2,000 or 3,000 passwords without being blocked. Nevertheless, despite this method's weaknesses, websites that experience high numbers of attacks, adult Web sites in particular, do choose to block proxy IP addresses.

My proposition

• Not locking the account. Instead, we might consider adding intentional delay from server side in the login/signup attempts for consecutive wrong attempts.
• Tracking user location based on IP address in login attempts, which is a common technique used by Google and Facebook. Google sends a OTP while Facebook provides other security challenges like detecting user's friends from the photos.
• Google re-captcha for web application, SafetyNet for Android and proper mobile application attestation technique for iOS - in login or signup requests.
• Device cookie
• Building a API call monitoring system to detect unusual calls for a certain API endpoint.

Propositions Explained

Intentional delay in response

The password authentication delay significantly slows down the attacker, since the success of the attack is dependent on time. An easy solution is to inject random pauses when checking a password. Adding even a few seconds' pause will not bother most legitimate users as they log in to their accounts.

Note that although adding a delay could slow a single-threaded attack, it is less effective if the attacker sends multiple simultaneous authentication requests.

Security challenges

This technique can be described as adaptive security challenges based on the actions performed by the user in using the system earlier. In case of a new user, this technique might throw default security challenges.

We might consider putting in when we will throw security challenges? There are several points where we can.

• When user is trying to login from a location where he was not located nearby before.
• Wrong attempts on login.

What kind of security challenge user might face?

• If user sets up the security questions, we might consider asking the user answers of those.
• For the applications like Whatsapp, Viber etc. we might consider taking some random contact names from phonebook and ask to put the numbers of them or vice versa.
• For transactional systems, we might consider asking the user about latest transactions and payments.

API monitoring panel

To build a monitoring panel for API calls.

• Look for the conditions that could indicate a brute-force attack or other account abuse in the API monitoring panel.
• Many failed logins from the same IP address.
• Logins with multiple usernames from the same IP address.
• Logins for a single account coming from many different IP addresses.
• Excessive usage and bandwidth consumption from a single use.
• Failed login attempts from alphabetically sequential usernames or passwords.
• Logins with suspicious passwords hackers commonly use, such as ownsyou (ownzyou), washere (wazhere), zealots, hacksyou etc.

For internal system accounts we might consider allowing login only from certain IP addresses. If the account locking needs to be in place, instead of completely locking out an account, place it in a lockdown mode with limited capabilities.

Here are some good reads.

• https://en.wikipedia.org/wiki/Brute-force_attack#Reverse_brute-force_attack
• https://www.owasp.org/index.php/Blocking_Brute_Force_Attacks
• http://www.computerweekly.com/answer/Techniques-for-preventing-a-brute-force-login-attack