STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Nutanix AOS 5.20.x OS Security Technical Implementation Guide

V-254224

CAT I (High)

Nutanix AOS must enable FIPS mode to implement NIST FIPS-validated cryptography.

Rule ID

SV-254224r959006_rule

STIG

Nutanix AOS 5.20.x OS Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-002450

Discussion

Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The operating system must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. Satisfies: SRG-OS-000478-GPOS-00223, SRG-OS-000396-GPOS-00176

Check Content

Confirm Nutanix AOS implements DoD-approved encryption to protect the confidentiality of remote access sessions.

Determine if the "dracut-fips" package is installed with the following command:

$ sudo yum list installed dracut-fips
dracut-fips.x86_64-033-572.el7 

If dracut-fips package is not installed, this is a finding.

Determine if FIPS mode is enabled with the following command:

$ fipscheck
usage: fipscheck [-s <hmac-suffix>] <paths-to-files>
fips mode is on

If FIPS mode is "on", Determine if the kernel boot parameter is configured for FIPS mode with the following command:

$ sudo cat /boot/grub/grub.conf | grep fips

It the  kernel output does not list "fips=1", this is a finding.

If the kernel boot parameter is configured to use FIPS mode, Determine if the system is in FIPS mode with the following command:

$ sudo cat /proc/sys/crypto/fips_enabled
1

If FIPS mode is not "on", the kernel boot parameter is not configured for FIPS mode, or the system does not have a value of "1" for "fips_enabled" in "/proc/sys/crypto", this is a finding.

Fix Text

Configure the system to run in FIPS mode by running the following command:

$ sudo salt-call state.sls security/CVM/fipsCVM