I need to provide the Reset Password Feature for my product. For this I have two competing solutions:

  1. Send the password reset link in mail to the user
  2. Provide the Security Question based solution

Based on the assessment by our security team, the security questions are deemed not secure. The reason is that security questions generally ask for personal information like in which city you met your spouse, name of your elementary school etc. This type of personal information widely available on the net courtesy the social media.

So, is this assessment correct and should the security question based solution for reset password be avoided?

  • 6
    Why are these solutions competing with each other?
    – techraf
    Commented Jun 8, 2016 at 7:25
  • 1
    What @techraf said ! You should be authenticating the user (security question) before giving them access (password reset link) ! Commented Jun 8, 2016 at 7:28
  • @techraf: These solutions provide two different ways of implementing the reset password functionality, I can combine these two but that is not an option at the moment. Commented Jun 8, 2016 at 8:41
  • 1
    @Manchanda.P , well forgive me, but quite frankly pretty stupid to blindly send out reset links without first taking a few steps to verify the identity of who you're sending it to ! (email accounts can get hacked etc.) Commented Jun 8, 2016 at 9:49
  • 5
    @LittleCode why would you want them to remember a set of passwords before being able to get their reset email? If they've forgotten one then they've probably forgotten them all. Commented Jun 8, 2016 at 22:47

3 Answers 3


I agree with your security team. The "security question" is not secure on its own: cities can be found over ip, names can be googled and nicknames of pets can be guessed.

However, you could combine both methods: first send the mail, and when the user clicks the link, ask the question. This way you would add at least a bit more security to the procedere. Also think about a lock (e.g. 12 hours) after three bad attempts to ensure bruteforcing isn't possible.

  • Combining the two actively harms usability and is still something that can be googled or brute forced. Now they also have to be stored encrypted, and have the same security procedures in two places. Commented Jun 8, 2016 at 20:25
  • Yes thats right. This practice is just another option, clearly not the best. The only real safe way would be two factor authentication, but that implies the biggest expense too.
    – licklake
    Commented Jun 9, 2016 at 5:57

I agree with your security team, these kind of questions are too easy to lift from social media, online research or just guesswork. It can be made a lot better then 'what is your dogs name', but its still antiquated.

Depending on your needs, in most situations I recommend an third choice. Required mobile phone number registration and SMS to the mobile phone with a verification code on password change.

Sadly, some users have the same/similar password everywhere. And what if this customer of yours have had an attacker start with taking his email account? Then finding he have an account on your product from reading his emails. Then taking over his account with your company, then .. changing the password since you email the password changing link to him/her ..

  • Thanks @Simply G, for your quick response. I understand that email account can also be taken over. My thought process was that the reset link in the email would have an expiry (probably of few hours). If user doesn't uses that link within stipulated time then (s)he would need to regenerate the same. Sending verification code to mobile phone is also a good option but it costs money (security always expensive :-) ). Thanks Commented Jun 8, 2016 at 7:13
  • Of course, as I said it depends on your needs.
    – Simply G.
    Commented Jun 8, 2016 at 13:29
  • 1
    Mobile phone messages are only security through obscurity. SMS is sent un-encrypted. Commented Jun 8, 2016 at 20:24
  • While there is a point to that, I'd say that the main issue is that SMS is the best current way to multi-factor authentication. Because 'everyone' owns a mobile phone. It doesn't make things worse from the reset-link email, most emails are sent in cleartext?
    – Simply G.
    Commented Jun 9, 2016 at 4:51
  • Yahoo, gmail, microsoft (live, putlook, hotmail, etc) are the three big ones and all use encrypted mail transfer. Most companies do as well because SSH/TLS enforcement on mail servers is just as easy to do on Web servers. Commented Jun 9, 2016 at 7:36

Let's us an example of why security questions are a bad system:

You have forgotten your password, and go to a page to reset your password by answering questions. We all know these questions are horrible and easy to guess, or find out. So recomended advice is to choose an answer and change a few letter into numbers and symbols to prevent it from being easily guessed by people or machines. Now you've forgotten what those changes you made were! So worse yet if the answer was short it is easily brute forced with enough computing power. Let's do another comparison:

  • Password: Send a payload to a server to compare against a hash

  • Security questions: Send a payload to a server to compare against a hash.

The similarities don't stop there. To keep the personally identifiable information secure you must hash or encrypt it (ideally hash) it in the database. In other words security questions are nothing more than extra passwords to remember. OWASP even recommends against them because they fail to all of the exact same tests as passwords. They are hard to remember if safe from guessing, and worse yet actively harm usability. However to an attacker at this point it is only just slightly more viable for them to brute force the password on the account directly than trying to figure out or brute force the security questions and also hack the email account. You have gained no extra security because this actively hurts users if they forget these passwords security questions and it means they can't ever reset their password.

Only using a password reset link should be sufficient of the two methods because it also uses the security features of the email account, including rate limiting and hopefully mfa authentication. So really don't use password reset questions. Even better if the email uses TLS it is sent encryoted.


  • 1
    Reason for the down vote would be nice. Commented Jun 8, 2016 at 21:28
  • The point of a security question is that it is a fact about your life that you are not going to forget. "What city did you grow up in" is not something you have to keep in your password manager. The last two paragraphs assume that there is a support contact through which the security questions can be circumvented, but there is no basis for that assumption. There is nothing about a support contact in the question.
    – Sjoerd
    Commented Jun 9, 2016 at 7:10
  • ...and just the same amount of security as only using the reset email.; your second sentence and it's already not true because an attacker needs to know or brute force security questions as well. How these questions should be chosen is a different topic, apparently not "What's your dog's name?"
    – Potaito
    Commented Jun 9, 2016 at 7:12
  • If that happens enough and an attacker gains access to their email and then just emails support to get access to the account again No, if properly implemented and applied the support would simply be able to provide a link to a reset form, which shows a bunch of security questions. And you could only reset the password if you had all answers. All questions should be on the same page to make things harder for a cracker.
    – Potaito
    Commented Jun 9, 2016 at 7:13
  • owasp.org/index.php/… Commented Jun 9, 2016 at 7:14

Not the answer you're looking for? Browse other questions tagged .