AAAI-08
Critical
Weight: 10

Plaintext Password Storage Risks

Plain English Explanation

This question asks if passwords are stored in readable form anywhere in your system - like keeping them in a spreadsheet or database where anyone with access can read them directly. It's equivalent to writing down everyone's passwords on sticky notes. Passwords should be scrambled using one-way encryption (hashing) so even your own team can't read them.

Business Impact

Storing passwords in plaintext is a catastrophic security failure that violates virtually every compliance standard and can result in massive fines under GDPR, CCPA, and other regulations. A single breach exposing plaintext passwords destroys customer trust permanently and often leads to lawsuits, regulatory penalties, and business closure. This practice is so egregious that discovering it typically ends vendor relationships immediately and can trigger mandatory breach notifications even without an actual attack.

Common Pitfalls

Some teams encrypt passwords but store the decryption key in the same database, which is effectively the same as plaintext. Another mistake is properly hashing passwords in the main database but storing them in plaintext in logs, backups, or email systems. Development and staging environments are often overlooked, with plaintext passwords lingering in test databases.

Expert Guidance

Upgrade to SOFT_GATED tier to unlock expert guidance

Implementation Roadmap

Upgrade to DEEP_GATED tier to unlock implementation roadmap

Question Information

Category
Authentication, Authorization, and Account Management
Question ID
AAAI-08
Version
4.1.0
Importance
Critical
Weight
10/10

Unlock Premium Content

Get expert guidance, business impact analysis, and implementation roadmaps for all questions.

Get Access