---
title: "How should I store passwords securely?"  
description: "How should I store passwords securely?"  
author: "Arnaud Simon"  
published: 2026-11-19  
updated: 2026-11-19  
canonical: https://www.mindstick.com/forum/163081/how-should-i-store-passwords-securely  
category: "Cloud and Security"  
tags: ["password storage", "hashing", "bcrypt", "security", "authentication"]  
reading_time: 1 minute  

---

# How should I store passwords securely?

Our old system stores passwords hashed with MD5. How should it be done properly?

## Replies

### Reply by Isha Srivastava

MD5 and SHA-1 (and plain SHA-256) are far too fast for passwords. Attackers can try billions of guesses a second against a stolen database. Plain text or reversible encryption is worse.

Do this instead:

- Use a **slow, salted, purpose-built password hash**: Argon2id, bcrypt, scrypt or PBKDF2 with a high iteration count. A salt (random value per user) is built into these, and stops identical passwords from having identical hashes.
- **Do not invent your own scheme.** In ASP.NET Core, use ASP.NET Identity's PasswordHasher, which handles salt and the work factor.
- Tune the cost factor so a login takes tens or hundreds of milliseconds, and raise it over the years.
- **Migrate gradually**: when a user logs in, check the old hash, then re-hash the password with the new algorithm and save it.
- Support **multi-factor authentication**, rate-limit login attempts, and check new passwords against lists of leaked passwords.

Never log, email or display a password, and never offer a "show my password" feature.


---

Original Source: https://www.mindstick.com/forum/163081/how-should-i-store-passwords-securely

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.
