Detections
Analytics

GEN000240 - The system clock must be synchronized to an authoritative DoD time source - 'NTP peer is configured'

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

To assure the accuracy of the system clock, it must be synchronized with an authoritative time source within DoD. Many system functions, including time-based login and activity restrictions, automated reports, system logs, and audit records depend on an accurate system clock. If there is no confidence in the correctness of the system clock, time-based functions may not operate as intended and records may be of diminished value.

Authoritative time sources include authorized time servers within the enclave synchronized with upstream authoritative sources. Specific requirements for the upstream synchronization of Network Time Protocol (NTP) servers are covered in the Network Other Devices STIG.

For systems located on isolated or closed networks, it is not necessary to synchronize with a global authoritative time source. If a global authoritative time source is not available to systems on an isolated network, a local authoritative time source must be established on this network and used by the systems connected to this network. This is necessary to provide the ability to correlate events and allow for the correct operation of time-dependent protocols between systems on the isolated network.

If the system is completely isolated (no connections to networks or other systems), time synchronization is not required as no correlation of events between systems will be necessary. If the system is completely isolated, this requirement is not applicable.

Solution

Use a local authoritative time server synchronizing to an authorized DoD time source. Ensure all systems in the facility feed from one or more local time servers feeding from the authoritative time server.

View the current system (x)ntpd man page for a detailed discussion of configuration option details:
# man xntpd

Create/edit the ntp.conf file, delete any non-local and/or non-U.S. DoD sources and insert the local or an authoritative U.S. DoD source.

Example /etc/ntp.conf file:
#
# server : ntp server used (poll) to obtain time
server <IP or hostname for 1st server>
server <IP or hostname for 2nd server>
#
# peer : a peer relationship with another ntp server
peer <IP or hostname for ntp peer>
#
# driftfile : track local clock time (drift of the local clock)
driftfile <drift file name, default is /etc/ntp.drift>

Stop/restart (x)ntpd. The default system script to start ntp should be found in the system startup directory /sbin/init.d :
# /sbin/init.d/xntpd start

See Also

https://iasecontent.disa.mil/stigs/zip/U_HPUX_11-31_V1R19_STIG.zip

Item Details

Category: CONFIGURATION MANAGEMENT

References: 800-53|CM-6, CAT|II, CCI|CCI-001492, CSCv6|3.1, Rule-ID|SV-38428r1_rule, STIG-ID|GEN000240, Vuln-ID|V-4301

Plugin: Unix

Control ID: 7d1bfe402b05e89204f688c40e41fbc7ffaae9bbdeac22c824edbeb685e47aa9