Brute force attack

1 Introduction

A common threat that webdevelopers face is a password-guessing attack known as a brute force attack. abrute-force attack is an attempt to discover a password by systematicallytrying every possible combination of letters, numbers, and symbols until youdiscover the one correct combination that works. if your web site requires userauthentication, you are a good target for a brute-force attack.

2 solution2.1 Enforce Password strength

Complex password is veryhard to guess. Strong Password is always a good way to protect from brute forceattack.

2.1.1 advantage

We have implemented thelogic in our production. It doesn' t need any change in code.

2.1.2 disadvantage

This needs pm to persuadeour customer to enforce the strong password policy which is controlled bypassword option in site admin. if some MERs don't want to use the strongpolicy of the password, we still need some other measure to protect brute forceattack.

This can only be used forrequest with password.

2.2 answer a question

When a user signs up, userneeds choose or create a question or several questions. Before user login, user need answer thequestion in advance.

2.2.1 advantage

This can protect from bruteforce extends tively if the answer of the question is long enough. It is equals tomake the password longer. It is also not hard to implement it.

2.2.2 disadvantage

For the users which alreadyare in our system, there is no this kind questions. It needs pm to talk withthem to use this feature.

At the same time, it changesthe logic of login; this can cause changes for all modules that use login API.

2.3 send code to mobile or mail

When user signs up, userneed provide a valid email or phone number. each time, when user logins, systemwill send a code, which is 6 digits, to the registered email or phone number, user need enter the code before login. system need check the password and thecode together. only permit user to login or visit the object if both of themare correct.

2.3.1 advantage

Attacker cannot brute forcethe password without the code which can only be accepted by mobile or email. Currently, some big companies, like Google, have use this way, but not enforceit.

2.3.2 disadvantage

For email, We Can implementit easily. But, it is inconvenient. Forexample, for mobile user, s/he need change screen to visit email to get thecode.

For mobile, currently, thereis no this function. We need implement a system to send message to Mobile.

At the same time, it changesthe logic of login; this can cause changes for all modules/APIs that use thisto avoid brute force.

2.4 CAPTCHA

A CAPTCHA (an acronym for "completely automated public Turing test to tell computers and humansapart") is a type of challenge-response test used in computing to determinewhether or not the user is human.

2.4.1 advantage

There have already been manyimplementation can be used directly. it is also a common way for your web sitesto protect from brute force. as user can get the code from screen, it will notaffect user experience much.

2.4.2 disadvantage

If the captch is complex, itis hard for user to read it. if the captch is not complex, it will be easy tobe guess by some tools. it is not easy to get an appropriate degree. but, wemay choose the captch to show a multi-choice question, server needs checkwhether the answer of the question is correct. it will be much harder to bypass.

2.5 lock out user

The most obvious way toblock brute-force attacks is to simply lock out accounts after a defined numberof incorrect password attempts. account lockouts can last a specific duration, such as one hour, or the accounts cocould remain locked until manually unlockedby an administrator. however, account lockout is not always the best solution, because someone cocould easily abuse the security measure and lock out hundredsof user accounts. in fact, some Web sites experience so far attacks that theyare unable to enforce a lockout policy because they wowould constantly beunlocking customer accounts.

2.5.1 advantage

It is easy to implement andwill not affect the current business logic much. It has no effect on themodules that use login API.

2.5.2 disadvantage

An attacker can cause adenial of service (DoS) by locking out large numbers of accounts.

Because you cannot lock outan account that does not exist, only valid account names will lock. An attackercocould use this fact to harvest usernames from the site, depending on the errorresponses.

An attacker can cause adiversion by locking out into accounts and flooding the Help Desk with supportcils.

An attacker can continuouslylock out the same account, even seconds after an administrator unlocks it, please tively disabling the account.

Account Lockout isineffective against Slow attacks that try only a few passwords every hour.

Account Lockout isineffective against attacks that try one password against a large list ofusernames.

Account Lockout isineffective if the attacker is using a username/password combo list and guessescorrectly on the first couple of attempts.

Powerful accounts such asadministrator accounts often bypass lockout policy, but these are the mostdesirable accounts to attack. Some systems lock out administrator accounts onlyon network-based logins.

Even once you lock out anaccount, the attack may continue, consuming valuable human and computerresources.

3 Summary

After comparing the solutionabove, the best way is to enforce password strength, it is also need few effortsfrom engineer team. But, this can onlybe used for request with password.

For request with or withoutpassword, we may choose CAPTCHA; it is still an effective way to against bruteforce attack. For not impact the userexperience, we may choose show CAPTCHA after failed 3 times.