Title

RHEL 8 must employ FIPS 140-2 approved cryptographic hashing algorithms for all stored passwords. (Cat II impact)

Discussion

The system must use a strong hashing algorithm to store the password. Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.

Check Content

Confirm that the interactive user account passwords are using a strong password hash with the following command: $ sudo cut -d: -f2 /etc/shadow $6$kcOnRq/5$NUEYPuyL.wghQwWssXRcLRFiiru7f5JPV6GaJhNC2aK5F3PZpE/BCCtwrxRc/AInKMNX3CdMw11m9STiql12f/ Password hashes "!" or "*" indicate inactive accounts not available for logon and are not evaluated. If any interactive user password hash does not begin with "$6$", this is a finding.

Fix Text

Lock all interactive user accounts not using SHA-512 hashing until the passwords can be regenerated with SHA-512.

Additional Identifiers

Rule ID: SV-230232r877397_rule

Vulnerability ID: V-230232

Group Title: SRG-OS-000073-GPOS-00041

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.