Nutanix OS must implement cryptographic mechanisms to protect the integrity of nonlocal maintenance and diagnostic communications, when used for nonlocal maintenance sessions.

Severity
Group ID
Group Title
Version
Rule ID
Date
STIG Version
highV-279619SRG-OS-000393-GPOS-00173NXAC-OS-000176SV-279619r1192185_rule2026-02-241

Description

Privileged access contains control and configuration information and is particularly sensitive, so additional protections are necessary. This is maintained by using cryptographic mechanisms, such as a hash function or digital signature, to protect integrity. Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. The operating system can meet this requirement through leveraging a cryptographic module. This requirement does not cover hardware/software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing "ping," "ls," "ipconfig," or the hardware and software implementing the monitoring port of an Ethernet switch).

ℹ️ Check

Confirm that the Nutanix OS OpenSSL library is configured to only use DOD-approved TLS encryption using the following command. $ sudo grep -i MinProtocol /etc/crypto-policies/back-ends/opensslcnf.config TLS.MinProtocol = TLSv1.2 DTLS.MinProtocol = DTLSv1.2 If the "TLS.MinProtocol" is set to anything older than "TLVSv1.2" or the "DTLS.Min.Protocol" is set to anything older than DTLSv1.2, this is a finding.

✔️ Fix

Configure the system to run in FIPS mode. 1. For AOS, configure FIPS mode using the following command. $ sudo salt-call state.sls security/CVM/fipsCVM 2. For Prism Central, configure FIPS mode using the following command. $ sudo salt-call state.sls security/PCVM/fipsPCVM 3. For Files, configure FIPS mode using the following command. $ sudo salt-call state.sls security/AFS/fipsAFS 4. For AHV, configure FIPS mode using the following command. $ sudo salt-call state.sls security/KVM/fipsKVM