STIGQter STIGQter: STIG Summary: Ivanti Connect Secure NDM Security Technical Implementation Guide Version: 2 Release: 3 Benchmark Date: 01 Oct 2025:

The ICS must be configured to synchronize internal information system clocks using redundant authoritative time sources.

DISA Rule

SV-258610r997509_rule

Vulnerability Number

V-258610

Group Title

SRG-APP-000373-NDM-000298

Rule Version

IVCS-NM-000360

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

In the ICS Web UI, navigate to System >> Status >> Overview.
1. Under "Appliance Details", and "System Date and Time", click "Edit".
2. Click "Use Pool of NTP Servers".
3. Set the IP address or hostname of the first time source.
4. In the "Key 1" box, type the number, algorithm, and key value using this format: 1 SHA1 testingkey
5. Set the IP address or hostname of the second time source, noting that this must be a time source different from the first.
6. In the "Key 2" box, type the number, algorithm, and key value using this format: 1 SHA1 testingkey.
7. Click "Save Changes".
8. Navigate to System >> Log/Monitoring >> Events >> Log on the Web UI.
9. Look in the logs for successful or unsuccessful time sync messages.

Check Contents

In the ICS Web UI, navigate to System >> Status >> Overview.

Under "Appliance Details", and "System Date and Time", click "Edit".

If the Time Source is not set to at least two NTP time sources, this is a finding.

If the Time Sources are not specific to a DOD authoritative time source, this is a finding.

If the Time Sources are not configured to use a SHA1 preshared key for authentication, this is a finding.

Vulnerability Number

V-258610

Documentable

False

Rule Version

IVCS-NM-000360

Severity Override Guidance

In the ICS Web UI, navigate to System >> Status >> Overview.

Under "Appliance Details", and "System Date and Time", click "Edit".

If the Time Source is not set to at least two NTP time sources, this is a finding.

If the Time Sources are not specific to a DOD authoritative time source, this is a finding.

If the Time Sources are not configured to use a SHA1 preshared key for authentication, this is a finding.

Check Content Reference

M

Target Key

5558