The Sentry providing encryption intermediary services must implement NIST FIPS-validated cryptography to generate cryptographic hashes.

Severity
Group ID
Group Title
Version
Rule ID
Date
STIG Version
mediumV-251036SRG-NET-000510-ALG-000025MOIS-AL-001340SV-251036r1028203_rule2024-09-253
Description
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The network element must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.
ℹ️ Check
Verify the Sentry uses encryption services that implement NIST FIPS-validated cryptography to protect the confidentiality of remote access sessions. On the Sentry CLI console, do the following: 1. SSH to Sentry Server from any SSH client. 2. Enter the administrator credentials set when Sentry was installed. 3. Enter "enable". 4. When prompted, enter the "enable secret" set when Sentry was installed. 5. Enter "show FIPS". 6. Verify "FIPS 140 mode is enabled" is displayed. If the Sentry Server does not report that FIPS mode is "enabled", this is a finding.
✔️ Fix
Configure the Sentry Server to use a FIPS 140-2 validated cryptographic module. On the Sentry console, do the following: 1. SSH to Sentry Server from any SSH client. 2. Enter the administrator credentials set when Sentry was installed. 3. Enter "enable". 4. When prompted, enter the "enable secret" set when Sentry was installed. 5. Enter "configure terminal". 6. Enter the following command to enable FIPS: FIPS 7. Enter the following command to proceed with the necessary reload: do reload 8. Enter "Yes" at saved configuration modified prompt. 9. Enter "Yes" at proceed do reload.