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 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Ivanti Sentry 9.x ALG Security Technical Implementation Guide

V-251014

CAT II (Medium)

The Sentry providing intermediary services for remote access communications traffic must use NIST FIPS-validated cryptography to protect the integrity of remote access sessions.

Rule ID

SV-251014r1028180_rule

STIG

Ivanti Sentry 9.x ALG Security Technical Implementation Guide

Version

V3R1

CCIs

CCI-001453

Discussion

Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Remote access is access to DoD-nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include broadband and wireless connections. Remote access methods include, for example, proxied remote encrypted traffic (e.g., TLS gateways, web content filters, and webmail proxies). Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. This requirement applies to ALGs providing remote access proxy services as part of its intermediary services (e.g., OWA or TLS gateway).

Check Content

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 Text

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 save configuration modified prompt.
9. Enter "Yes" at proceed do reload.