Security Questions Are Weak: Safer Alternatives for Account Recovery

By Information Security Asia · November 21, 2026 · 3 min read

Short answer: security questions are weak because the answers are often public, guessable or reused. If a site forces you to use them, treat the answer as a second password: give a random, unrelated string and store it in your password manager. Where possible, use an authenticator app, passkey or recovery codes instead.

Security Questions Are Weak: Safer Alternatives for Account Recovery

Last reviewed: November 2026.

Why security questions are weak

  • Answers can be found. Your birthplace, school, pet’s name and mother’s maiden name can appear on social media, in public records or in earlier data breaches.
  • Answers can be guessed. Many questions have a small set of likely answers, such as common colours, cities and pet names.
  • Answers are shared by people who know you, so family and former friends may know them.
  • Answers do not change. You cannot easily replace your first school if it leaks.
  • Answers get reused across sites, so one breach exposes many accounts.

Security questions give an attacker a way around a strong password. The account is only as safe as the easiest recovery path.

If you must use them

  1. Do not answer truthfully. Treat the question as a label and the answer as a password.
  2. Use a random string or a long random phrase generated by your password manager, with a different one for each account.
  3. Store question and answer in the manager’s notes field for that login.
  4. Never answer with information found on your social media profiles.
  5. Do not give the real answer to a person on the phone. If a support agent asks for it, you can read the random string, but be sure it is really support, and see our guide to phone scams.

A downside: a random answer is hard to remember and nobody can recite it. That is fine as long as it is saved somewhere safe. Our password manager guide covers this.

Security Questions Are Weak: Safer Alternatives for Account Recovery

Better recovery options

  • Authenticator app or security key. Use these for sign-in and for recovery. Compare options in two-factor methods compared.
  • Passkeys. They resist phishing and remove the password. See passkeys vs passwords.
  • Recovery codes. One-time codes the service gives you when you set up two-factor. Print them or save them in the password manager.
  • A recovery email you control, secured with strong sign-in of its own.
  • A trusted contact or device, where a service offers it.

SMS is better than nothing as a recovery method, but can be attacked through SIM swapping. See SIM swap protection.

For website owners and developers

Modern guidance from standards bodies discourages knowledge-based questions as an authenticator. If you build a service, offer recovery through verified email, recovery codes or passkeys, rate-limit attempts, and notify the user of any recovery request.

If a question leaked

Change the answer on that account and any other account where you used it. Then review where else the same facts are used. Check your email for breaches with the steps in our data breach guide.

Frequently asked questions

Are security questions ever safe?

Only when the answers are random and secret. Honest answers to real personal questions are not safe.

Is lying to a security question wrong?

No. The answer is a credential, not a statement of fact.

What if the website does not let me change the answers?

Use unrelated random answers for new accounts, and consider closing accounts that offer only weak recovery.

Sources and further reading

  • NIST Special Publication 800-63B, Digital Identity Guidelines: pages.nist.gov/800-63-3
  • National Cyber Security Centre (UK), guidance on passwords and recovery: ncsc.gov.uk

Keep reading