SRG-OS-000120-ESXI5 - Password hashes stored on the system must be generated using FIPS 140-2 approved crypto hashing algorithm

Information

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Temporarily disable Lockdown Mode and enable the ESXi Shell via the vSphere Client. Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials. If connecting to vCenter Server, click on the desired host. Click the Configuration tab. Click Software, Security Profile, Services, Properties, ESXi Shell and Options, respectively. Start the ESXi Shell service, where/as required. As root, log in to the host and verify the expected setting is configured in the /etc/pam.d/system-auth file. The entry format will look similar to 'password sufficient /lib/security/$ISA/pam_unix.so use_authtok nullok shadow'. Edit the file and replace the existing hash key ( md5, des, or sha256) with sha512 or append sha512, if there is no existing key. For example: 'password sufficient /lib/security/$ISA/pam_unix.so use_authtok nullok shadow sha512'. Re-enable Lockdown Mode on the host

See Also

http://iasecontent.disa.mil/stigs/zip/U_ESXi5_Server_V1R10_STIG.zip

Item Details

References: CAT|II, CCI|CCI-000803, Group-ID|V-39260, Rule-ID|SV-51076r1_rule, STIG-ID|SRG-OS-000120-ESXI5, Vuln-ID|V-39260

Plugin: VMware

Control ID: d0d43f967572cfa31d112a3d361c1a5f42dfa825dca6003027cd5e1afb3978da