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 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to HYCU Protege Security Technical Implementation Guide

V-268269

CAT I (High)

The HYCU virtual appliance must use FIPS 140-2-approved algorithms for authentication to a cryptographic module.

Rule ID

SV-268269r1038744_rule

STIG

HYCU Protege Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000803

Discussion

Unapproved mechanisms that are used for authentication to the cryptographic module are not validated and therefore cannot be relied upon to provide confidentiality or integrity, and DOD data may be compromised. Network devices 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. However, authentication algorithms must configure security processes to use only FIPS-approved and NIST-recommended authentication algorithms.

Check Content

When FIPS mode is enabled, the HYCU application will use FIPS-compliant behavior. Validate the FIPS status using the following command:
'cat /proc/sys/crypto/fips_enabled' 

If command output does not show "1", this is a finding.

'fips-mode-setup --check'

If command output does not show "FIPS mode is enabled", this is a finding.

'update-crypto-policies --show'

If command output does not show "FIPS", this is a finding.

Fix Text

Stop the HYCU web server: 
sudo systemctl stop grizzly.service

Enable FIPS-compliant mode: 
sudo /opt/grizzly/bin/enable_fips.sh

Reboot the HYCU virtual machines:
shutdown -r now