CCI-004923

AAA Services must be configured to use at least two NTP servers to synchronize time.

AAA Services must be configured to authenticate all NTP messages received from NTP servers and peers.

The macOS system must enforce time synchronization.

The macOS system must be configured to use an authorized time server.

The macOS system must enable time synchronization daemon.

The macOS system must enable the time synchronization daemon.

The application server must compare internal application server clocks at least every 24 hours with an authoritative time source.

The Arista network device must be configured to synchronize internal system clocks using redundant authenticated time sources.

The Ubuntu operating system must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

Ubuntu 22.04 LTS must, for networked systems, compare internal information system clocks at least every 24 hours with a server synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

The Central Log Server must compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.

The Cisco router must be configured to synchronize its clock with the primary and secondary time sources using redundant authoritative time sources.

The Cisco ASA must be configured to synchronize its clock with the primary and secondary time sources using redundant authoritative time sources.

The Cisco switch must be configured to synchronize its clock with the primary and secondary time sources using redundant authoritative time sources.

The DBMS must compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.

The DNS server implementation must compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.

SSMC must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.

The HPE 3PAR OS must, for networked systems, compare internal information system clocks at least every 24 hours with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

The operating system must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

AIX must provide time synchronization applications that can synchronize the system clock to external time sources at least every 24 hours.

IBM z/OS SNTP daemon (SNTPD) permission bits must be properly configured.

IBM z/OS SNTP daemon (SNTPD) must be active.

The IBM z/OS SNTP daemon (SNTPD) must be active.

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

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

The Juniper router must be configured to synchronize its clock with the primary and secondary time sources using redundant authoritative time sources.

The Mainframe Product must compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.

The Windows 11 time service must synchronize with an appropriate DOD time source.

The Windows Server 2019 time service must synchronize with an appropriate DOD time source.

The Windows Server 2022 time service must synchronize with an appropriate DOD time source.

The network device must be configured to compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.

The Oracle Linux operating system must, for networked systems, synchronize clocks with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

OL 8 must compare internal information system clocks at least every 24 hours with a server synchronized to an authoritative time source, such as the United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

The Riverbed NetProfiler must be configured to record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.

The Palo Alto Networks security platform must compare internal information system clocks at least every 24 hours with an authoritative time server.

The Palo Alto Networks security platform must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.

Automation Controller must compare internal application server clocks at least every 24 hours with an authoritative time source.

RHEL 9 must have the chrony package installed.

RHEL 9 chronyd service must be enabled.

RHEL 9 must securely compare internal information system clocks at least every 24 hours.

RHEL 8 must securely compare internal information system clocks at least every 24 hours with a server synchronized to an authoritative time source, such as the United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

The SUSE operating system clock must, for networked systems, be synchronized to an authoritative DoD time source at least every 24 hours.

The SUSE operating system clock must, for networked systems, be synchronized to an authoritative DOD time source at least every 24 hours.

The Tanium operating system (TanOS) must, for networked systems, compare internal information system clocks at least every 24 hours with a server synchronized to one of the redundant United States Naval Observatory (USNO) time servers or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

TOSS must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

The VMM must, for networked systems, compare internal information system clocks at least every 24 hours with a server which is synchronized to one of the redundant United States Naval Observatory (USNO) time servers or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).

The ESXi host must synchronize internal information system clocks to an authoritative time source.

The web server must compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.

The vCenter Server must compare internal information system clocks at least every 24 hours with an authoritative time server.

The Windows Time Service on the forest root PDC Emulator must be configured to acquire its time from an external time source.