← Back to VMware vRealize Operations Manager 6.x SLES Security Technical Implementation Guide

V-239556

CAT II (Medium)

The SLES for vRealize must use mechanisms meeting the requirements of applicable federal laws, Executive orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.

Rule ID

SV-239556r662119_rule

STIG

VMware vRealize Operations Manager 6.x SLES Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-000803

Discussion

Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised. SLES for vRealize utilizing encryption are required to use FIPS-compliant mechanisms for authenticating to cryptographic modules. FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets DoD requirements. This allows for Security Levels 1, 2, 3, or 4 for use on a general purpose computing system.

Check Content

Check the "/etc/default/passwd" file:

# grep CRYPT /etc/default/passwd

If the "CRYPT" setting in the "/etc/default/passwd" file is not present, or not set to "SHA256" or "SHA512", this is a finding.

If the "CRYPT_FILES" setting in the "/etc/default/passwd" file is not present, or not set to "SHA256" or "SHA512", this is a finding.

Fix Text

Edit the "/etc/default/passwd" file and add or change the "CRYPT" variable setting so that it contains:

CRYPT=sha256 
OR
CRYPT=sha512 

Edit the "/etc/default/passwd" file and add or change the "CRYPT_FILES" variable setting so that it contains:

CRYPT_FILES=sha256 
OR
CRYPT_FILES=sha512