Every individual who has online accounts to access services or applications invariably has had to establish answers to security questions. We logon to a new bank account, social media service, or check out via our favorite online paid service, and we are required to enter initial responses to security questions. The purpose of these questions is to periodically re-affirm our identity, or to regain access if we forget our password, by providing our personal secret answers.
Here are examples of some common security questions:
- In what city were you born?
- What is the name of your favorite pet?
- What is your mother's maiden name?
- What high school did you attend?
- What was the name of your elementary school?
- What was the make of your first car?
- What was your favorite food as a child?
- Where did you meet your spouse?
- What year was your father (or mother) born?
Why Are Common Security Questions a Problem?
The problem with common security questions (and with our answers) is they become a liability when the results are leaked online, such as through a data breach, or become public knowledge via outlets like social media. Why? Because many (in fact, thousands) of sites potentially use identical security questions. The variation from site-to-site is low, and questions for each user frequently, and inevitably, overlap across their many accounts. This standardization of security questions creates a substantial, but unnecessary, risk.
The threat of common security questions is comparable to reusing passwords. Security pros, and end users, should know they should never reuse a password across accounts. This is because, if one account is compromised, the password is no longer secret and is associated with your credentials/identity and could be used for future attacks against any account you own that has the same (or similar) usernames. When passwords are re-used across dozens of accounts, the compromise of just one account could potentially lead to the compromise of all the other un-related accounts and ultimately your identity.
How Do I Make My Security Questions Stronger?
While we do usually have control over the passwords we choose, as individuals, we do not have the power to change the security questions these websites and services require. However, we can answer these questions in creative ways to make our accounts more secure and eliminates the threat of multiple accounts being compromised. Here is some basic guidance on how make security questions stronger:
1. Choose Different Security Questions Across Sites: As much as is possible, do not select the same security questions across multiple sites. Keep your selections unique when the site allows you to pick your own questions. This will help limit the fallout and compromise of other accounts if the security question/answer is ever leaked. This is especially important for public figures whose history may be a part of public record or biographies posted on websites. For example, we all know the city our favorite musician or actor was born in, right?
2. Use Special Characters in Your Answers: Do not answer security questions in plain English (or your native language). That is what is expected, but it’s a security misstep. Treat your answers like passwords and introduce complexity in your response and its characters. For example, let’s say I was born in Little Rock, Arkansas. The security question for, “what city where you born in” would require the response, “Little Rock”. Now, add some password complexity. The new entry could therefore be, “L!ttl3 r0ck”. This answer is more difficult to guess or crack through automated tools and provides a simple layer of obfuscation to protect your security question responses. And, if anyone ever asks, you can honestly state your mother’s maiden name does have numbers and symbols in it. Doesn’t yours? I think you get the point—a little obfuscation can go along way to secure your answers.
3. Use Fictitious Information: In many instances, the best course of action is to provide fictitious information to these questions to keep them unique. You could use a personal password manager to populate the answer fields with password-like responses. Next, store each question and response in your password manager. For example, for an ecommerce site, you could create the entry “ecommercesite.com/question_birthcity” as the account and then enter a random, recommended password as the security response. This provides the secure storage you need in case of a password problem, while keeping your answers to same security question completely random and unique across sites and applications.
Why Mitigating the Use of Common Security Questions Is Important
Security questions were designed with the intent of strengthening identity validation for access to applications and websites, particularly in the case of a password issue or other fault. However, just as with password reuse, reusing security question and answer pairs across multiple sites has enabled threat actors to compromise many accounts associated with an identity. Typically, this requires a hacker to compromise a secondary application as well, like email or SMS texting, to pair a password reset with the knowledge of these security questions. Unfortunately, some websites and applications do not even go that far, and knowledge of a security question answer is sufficient to compromise the account, if the user provide the correct response
For IT and security professionals interested in a more rigorous and thorough examination of all the ways identities (corporate and personal) are at risk or under attack, and the best strategies for protecting them, check out: Identity Attack Vectors: Implementing an Effective Identity and Access Management Solution, a book co-authored by Darran Rolls, former CTO at SailPoint, and I. You can also watch our joint webinar on-demand here: Deconstructing Identity as a Cyberattack Vector.
This blog has been updated since it was originally published on June 4, 2020.
