Restrict and Secure Password Authentication

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

Run SHOW CLUSTER SETTING server.user_login.password_encryption; (must be scram-sha-256) and review SHOW USERS; plus SELECT username FROM system.users WHERE "hashedPassword" IS NOT NULL. Privileged and service accounts should use certificates; any remaining password hashes should be SCRAM-SHA-256 and passwords must meet length policy (server.user_login.min_password_length).

How it is fixed

Fix method: Guidance or infrastructure patch

1. Enable SCRAM-SHA-256 for new passwords Configure the cluster to use SCRAM-SHA-256 for all newly set passwords: SET CLUSTER SETTING server.user_login.password_encryption = 'scram-sha-256'; This ensures that any CREATE USER ... WITH PASSWORD or ALTER USER ... WITH PASSWORD operations store SCRAM-SHA-256 hashes. 2.