Store only a derived hash, never the plaintext password. Use a key derivation function such as Argon2, PBKDF2, bcrypt, or scrypt with a unique CSPRNG salt per password and a tuned work factor. The goal is to make each guess expensive enough that stolen hashes are impractical to brute force with modern hardware.
Why password storage should make offline guessing expensive
Good password storage is designed for the breach scenario, not the login scenario. Once a database is copied, the defender no longer controls the attacker’s pace, so the hash format and work factor must be strong enough to make each guess costly. For teams that need a practical baseline, NHIMG’s Password Security and Password Manager Guide and Password Manager Buyer’s Guide reinforce the same principle from policy and product angles.
The core design choice is to store a one-way derived value, not a reversible secret. A unique salt ensures two equal passwords do not produce the same stored value, which blocks precomputation and rainbow-table reuse. A work factor or memory-hard setting then slows repeated guessing enough that stolen hashes are far less attractive to crack at scale.
That is why the right question is not whether hashing was used, but whether the chosen password hashing scheme is slow enough, memory-hard where appropriate, and tuned for current hardware. A fast general-purpose hash may be technically one-way and still be a poor password storage choice because it gives attackers too many guesses per second after compromise.
What good password hashing looks like in practice
For modern password storage, the usual recommendation is an adaptive KDF such as Argon2, PBKDF2, bcrypt, or scrypt, paired with a per-password CSPRNG salt. The stored record should preserve the parameters needed to verify the password later, because those parameters are part of the security decision, not implementation noise. If you standardise on one scheme, keep the verifier logic consistent and avoid homegrown formats that weaken migration later.
NHIMG’s Password Manager Breach Response Playbook is useful here because it shows the downstream implications of weak or stolen password material, including priority-based rotation and re-enrolment decisions. The same operational logic applies when a password database is exposed: the stored verifier should buy you time, not pretend compromise is harmless.
Work factor tuning should reflect your threat model and performance budget. If verification is cheap enough for an attacker to test billions of guesses, it is too cheap. If the settings are so aggressive that they create avoidable authentication latency or deployment failures, teams will quietly bypass the control, which defeats the purpose.
How to judge whether your storage design is actually resilient
Resilience depends on more than the algorithm name. You need to confirm that each password has its own salt, that the salt is generated with a cryptographically secure source, and that the chosen parameters are still expensive under current commodity hardware. You also need to know whether the application exposes password-reset or account-recovery paths that bypass the hash entirely, because those paths often become the practical attack route after a database compromise.
For a broader implementation view, NHIMG’s Database Credential and Access Security Guide and Database Security Guide help teams separate credential storage from wider database hardening. That distinction matters because a strong hash does not compensate for weak database access, exposed backups, or leaked application connection secrets.
In practice, teams should treat password hashes as sensitive security material even though they are not plaintext passwords. If the storage layer, backups, logs, or exports leak, the hashes become an offline cracking target, and the attack becomes a compute problem instead of an online control problem.
Risk and Threat Considerations
Once a password database is stolen, the attacker can work offline, at scale, and without lockout controls. Weak salts, fast hashes, or outdated work factors turn a credential store into a cracking queue, and the resulting compromise can cascade into account takeover, reuse attacks, and access to linked systems.
Failure mechanism: The defence fails when the stored verifier is cheap to test, reused across users, or easy to precompute against, allowing attackers to run large password dictionaries and GPU-accelerated cracking against the dump.
Impact: Successful cracking can expose user accounts, enable password reuse attacks elsewhere, and force incident response actions well beyond the original database, including credential resets and session invalidation.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP ASVS, NIST SP 800-53 Rev 5, NIST SP 800-63 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP ASVS | V6 — Authentication | Password hashing is part of authentication verifier design. |
| Recommendation — Use strong password verification requirements and tune password verifiers for offline resistance. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Covers password/verifier lifecycle and secure storage of authenticators. |
| IA-7 — Cryptographic Module Authentication | Supports secure use of cryptographic mechanisms for password verification. | |
| Recommendation — Store and manage authenticators so stolen values are harder to misuse offline. Use approved cryptographic mechanisms for authentication-related verification. | ||
| NIST SP 800-63 | Digital Identity Guidelines | Defines modern password verifier expectations and resistance to compromise. |
| Recommendation — Follow digital identity guidance for salt, verifier strength, and throttling decisions. | ||
| CIS Controls v8 | 5 — Account Management | Password storage and verifier handling are part of account protection practices. |
| Recommendation — Protect account credentials with strong storage, rotation, and recovery controls. | ||
Practitioner Guidance
What to verify: Confirm that your verifier stores only the derived password hash plus per-password salt and algorithm parameters, and that the scheme is one your team can tune and migrate safely. Check backup copies, exports, and debug logs for any plaintext password leakage, because a perfect hash design does not help if the original password is copied somewhere else.
Decision rule: If the stored value can be validated cheaply or reversed at all, treat it as a design defect rather than an implementation detail. If the application still needs a legacy hash format, plan a staged rehash on successful login and prioritise the highest-value accounts first.
Practitioner takeaway: Password storage is secure only when stolen hashes remain economically unattractive to crack, so the control must be designed around offline attacker cost, not just authentication convenience.
Related resources from NHI Mgmt Group
- How should security teams speed up CloudTrail investigations when they need to check for compromise after a breach announcement?
- What do security teams get wrong when they focus on detection after a supply chain compromise but ignore access design?
- What do security teams get wrong when they rely on manual remediation after a suspected compromise?
- What should security teams do first when they suspect an adversary has already established footholds after a compromise?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org