Capacity
CCI-001891
The information system compares internal information system clocks on an organization-defined frequency with an organization-defined authoritative time source.
Choose one
29
Rule
Severity: Medium
Ensure Chrony is only configured with the server directive
30
Rule
Severity: Medium
A remote time server for Chrony is configured
17
Rule
Severity: Medium
Configure Time Service Maxpoll Interval
11
Rule
Severity: Medium
Specify a Remote NTP Server
2
Rule
Severity: Medium
Chrony Configure Pool and Server
1
Rule
Severity: Low
The A10 Networks ADC must compare internal information system clocks at least every 24 hours with an authoritative time server.
1
Rule
Severity: Low
AAA Services must be configured to use at least two NTP servers to synchronize time.
1
Rule
Severity: Medium
AAA Services must be configured to authenticate all NTP messages received from NTP servers and peers.
2
Rule
Severity: Medium
The Windows Time Service on the forest root PDC Emulator must be configured to acquire its time from an external time source.
1
Rule
Severity: Medium
The application server must compare internal application server clocks at least every 24 hours with an authoritative time source.
1
Rule
Severity: Medium
The DBN-6300 must compare internal information system clocks at least every 24 hours with an authoritative time server.
1
Rule
Severity: Medium
CounterACT must compare internal information systems clocks at least every 24 hours with an authoritative time server.
1
Rule
Severity: Medium
The HP FlexFabric Switch must compare internal information system clocks at least every 24 hours with an authoritative time server.
1
Rule
Severity: Low
The storage 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).
1
Rule
Severity: Low
The DataPower Gateway must compare internal information system clocks at least every 24 hours with an authoritative time server.
1
Rule
Severity: Low
The MQ Appliance messaging server must compare internal MQ Appliance messaging server clocks at least every 24 hours with an authoritative time source.
1
Rule
Severity: Medium
The MQ Appliance network device must compare internal information system clocks at least every 24 hours with an authoritative time server.
1
Rule
Severity: Low
Nutanix AOS must be configured to synchronize internal information system clocks using redundant authoritative time sources.
1
Rule
Severity: Low
Nutanix AOS must 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).
1
Rule
Severity: Medium
The SEL-2740S must be configured to compare internal information system clocks at least every 24 hours with an authoritative time server.
1
Rule
Severity: Medium
Symantec ProxySG must compare internal information system clocks at least every 24 hours with an authoritative time server.
2
Rule
Severity: Medium
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).
1
Rule
Severity: Medium
The macOS system 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).
3
Rule
Severity: Medium
The macOS system must 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).
2
Rule
Severity: Medium
The macOS system must enforce time synchronization.
2
Rule
Severity: Medium
The macOS system must be configured to use an authorized time server.
2
Rule
Severity: Medium
The macOS system must enable time synchronization daemon.
3
Rule
Severity: Medium
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).
1
Rule
Severity: Medium
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).
2
Rule
Severity: Medium
SSMC must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second.
2
Rule
Severity: Medium
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).
2
Rule
Severity: Medium
AIX must provide time synchronization applications that can synchronize the system clock to external time sources at least every 24 hours.
3
Rule
Severity: Medium
IBM z/OS SNTP daemon (SNTPD) permission bits must be properly configured.
1
Rule
Severity: Medium
IBM z/OS SNTP daemon (SNTPD) must be active.
2
Rule
Severity: Medium
The IBM z/OS SNTP daemon (SNTPD) must be active.
3
Rule
Severity: Low
The Windows 11 time service must synchronize with an appropriate DOD time source.
2
Rule
Severity: Low
The time service must synchronize with an appropriate DoD time source.
3
Rule
Severity: Low
The Windows Server 2019 time service must synchronize with an appropriate DOD time source.
3
Rule
Severity: Low
The Windows Server 2022 time service must synchronize with an appropriate DOD time source.
2
Rule
Severity: Medium
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).
1
Rule
Severity: Medium
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).
2
Rule
Severity: Low
The Palo Alto Networks security platform must compare internal information system clocks at least every 24 hours with an authoritative time server.
1
Rule
Severity: Medium
Automation Controller must compare internal application server clocks at least every 24 hours with an authoritative time source.
1
Rule
Severity: Medium
The Red Hat Enterprise 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).
2
Rule
Severity: Medium
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).
2
Rule
Severity: Medium
RHEL 9 must have the chrony package installed.
2
Rule
Severity: Medium
RHEL 9 chronyd service must be enabled.
2
Rule
Severity: Medium
RHEL 9 must securely compare internal information system clocks at least every 24 hours.
3
Rule
Severity: Medium
The SUSE operating system clock must, for networked systems, be synchronized to an authoritative DoD time source at least every 24 hours.
1
Rule
Severity: Medium
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).
1
Rule
Severity: Medium
The ESXi host must configure NTP time synchronization.
3
Rule
Severity: Medium
The ESXi host must synchronize internal information system clocks to an authoritative time source.
4
Rule
Severity: Medium
The vCenter Server must compare internal information system clocks at least every 24 hours with an authoritative time server.
2
Rule
Severity: Medium
Configure Systemd Timesyncd Servers
2
Rule
Severity: Medium
Configure Systemd Timesyncd Root Distance Servers
1
Rule
Severity: Low
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).
1
Rule
Severity: Medium
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).
1
Rule
Severity: Medium
SLEM 5 clock must, for networked systems, be synchronized to an authoritative DOD time source at least every 24 hours.
1
Rule
Severity: Medium
The SUSE operating system clock must, for networked systems, be synchronized to an authoritative DOD time source at least every 24 hours.
Patternfly
PatternFly elements
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.
Modules
66%