Passwords stored securely (hashed)
What it means
Passwords are stored only as salted hashes made with a modern algorithm, never in plain text.
Why it matters
If the database leaks, plain or weakly hashed passwords expose users on every other site where they were reused.
Legal and technical reference: GDPR Art. 32
How to pass this check
Quick fix: Store passwords only with a modern hash (bcrypt, Argon2). Never in plain text.
- Use bcrypt, scrypt or Argon2 through your framework’s standard function.
- Never email passwords and never log them.
- Rehash old passwords when users log in.
How Lawscan checks it
This cannot be verified from outside. Lawscan assumes it is compliant, so it never takes points away.
Limits: Treat it as a reminder: it passes automatically, but you are still responsible for it.
Does your website pass this check?
Scan it now: you get the result of all 55 checks in a few seconds.
Other checks in this category
- SSL certificate active (HTTPS) −3
- User password policy (complexity, expiration) −1
- Two-factor authentication for admin access −2
- Admin access protected (custom URL, IP restrictions) −2
- CMS/plugins regularly updated −2
- Periodic and tested backups −2
- Protection from brute force / SQL injection attacks −3
- User role/permission management −2
- Monitoring of suspicious access logs −1
← Back to the full Compliance Index
Automated, indicative information. It is not legal advice.