For secure password storage, I would use a hash table with a strong hash function like bcrypt. This is important because it protects passwords by not storing them in plaintext and makes it computationally difficult for attackers to reverse-engineer the original password.
In depth
Using a hash table for password storage is crucial because it allows us to store only the hashed version of the password, ensuring that even if a database is compromised, the actual passwords remain secure. A strong hash function, like bcrypt, adds an additional layer of security by incorporating a salt and making the hashing process intentionally slow, which deters brute-force attacks. It’s important to avoid weak or fast hash functions like MD5 or SHA-1, as they can be easily cracked due to their speed and known vulnerabilities. Additionally, it's advisable to use a peppering technique where a secret is added to the input before hashing, providing another barrier against attacks.
Example scenario
In a web application I worked on, we implemented password storage using bcrypt to hash user passwords before saving them to the database. This not only ensured that we never stored plaintext passwords but also made it significantly harder for attackers to retrieve the original passwords, even in the case of a data breach. The application also enforced strong password policies and used salting to further enhance security, making it robust against common attack vectors such as dictionary attacks.
Common mistakes
A common mistake is using a fast hashing algorithm such as SHA-256 for password storage, believing it to be secure due to its strength in other contexts. This is incorrect because faster hashes allow for quicker brute-force attacks. Another mistake is failing to use salts, which can lead to vulnerabilities where identical passwords yield the same hash, making it easier for attackers to use precomputed hash tables. Developers sometimes also forget to update their hashing strategy, continuing to use outdated methods as technologies evolve.
Follow-up questions
- What are the differences between hashing and encryption?
- Can you explain what a salt is and why it's important?
- How would you handle password resets securely?
- What measures would you take if a data breach occurred?

Want all 2,000 questions in one PDF?
- Short answers, in-depth explanations, common mistakes and follow-ups
- 89 topics, from Beginner to Architect, with a clickable contents list
- 226 extra questions that are not on this website
- Free Bonus Pack: 30-day study plan, behavioral questions, salary scripts
Includes 226 extra questions that are not on this site, plus a free Bonus Pack.
Get both books for $9.99 (save $2.99):
The material stays free to read online. This is the organised, offline, print-ready PDF edition. Secure payment by PayPal; your personal download link is emailed after payment is confirmed. Digital product, no shipping.