Are you storing any passwords in plaintext?
Explanation
Example Responses
Example Response 1
No, we do not store any passwords in plaintext All user passwords are hashed using the bcrypt algorithm with a work factor of 12 and unique salts for each password This approach ensures that even if our database were compromised, the original passwords could not be recovered from the stored hash values Additionally, our system administrators and developers have no capability to view user passwords at any point in the authentication process.
Example Response 2
No, our organization does not store passwords in plaintext We implement the Argon2id password hashing algorithm with appropriate memory, iterations, and parallelism parameters as recommended by NIST guidelines All password hashing operations occur server-side before storage, and we maintain separate salt values for each user account We regularly review our password storage mechanisms as part of our security program to ensure they remain aligned with current best practices.
Example Response 3
Yes, our current system does store some passwords in plaintext in our legacy customer database This has been identified as a critical security risk in our most recent security assessment, and we have an active remediation project underway We are implementing a new authentication system using industry-standard password hashing (PBKDF2 with SHA-256) that will be completed within the next 60 days In the interim, we have implemented additional access controls and monitoring around the database containing plaintext passwords to reduce risk.
Context
- Tab
- Product
- Category
- Authentication, Authorization, and Account Management

