OpenControls Logo

STIG Viewer

STIGViewer Support

Ubuntu OS 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) to synchronize clocks between NetIM components.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-275613RIIM-OS-252010SV-275613r1149439_ruleCCI-004923medium
Description
Inaccurate time stamps make it more difficult to correlate events and can lead to an inaccurate analysis. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. Sources outside the configured acceptable allowance (drift) may be inaccurate. Synchronizing internal information system clocks provides uniformity of time stamps for information systems with multiple system clocks and systems connected over a network. Organizations should consider endpoints that may not have regular access to the authoritative time server (e.g., mobile, teleworking, and tactical endpoints). Note that USNO offers authenticated NTP service to DOD and U.S. Government agencies operating on the NIPR and SIPR networks. Visit https://www.usno.navy.mil/USNO/time/ntp/DOD-customers for more information. Satisfies: SRG-OS-000355-GPOS-00143, SRG-OS-000785-GPOS-00250
STIGDate
Riverbed NetIM OS Security Technical Implementation Guide2025-10-02

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

MON-07.1Synchronization With Authoritative Time Source
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (9) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(9)Disconnect or Disable Access
1.00
AU-8Time Stamps
1.00
AU-8(1)Synchronization with Authoritative Time Source
1.00
AU-8(2)Secondary Authoritative Time Source
1.00
CM-6Configuration Settings
1.00
IA-3(1)Cryptographic Bidirectional Authentication
1.00
SC-45System Time Synchronization
1.00
SC-45(1)Synchronization with Authoritative Time Source
1.00
SC-45(2)Secondary Authoritative Time Source
1.00
CCI1 mapping
CCI-004923
1.00

Details

Check Text (C-275613r1149439_chk)

Verify Ubuntu OS is configured to compare the system clock at least every 24 hours to the authoritative time source by using the following command: Note: If the system is not networked, this requirement is not applicable. $ sudo grep maxpoll -ir /etc/chrony* server tick.usno.navy.mil iburst maxpoll 16 If the "maxpoll" option is set to a number greater than 16, the line is commented out, or is missing, this is a finding. Verify that the "chrony.conf" file is configured to an authoritative DOD time source by using the following command: $ sudo grep -ir server /etc/chrony* server tick.usno.navy.mil iburst maxpoll 16 server tock.usno.navy.mil iburst maxpoll 16 server ntp2.usno.navy.mil iburst maxpoll 16 If "server" is not defined, is not set to an authoritative DOD time source, is commented out, or missing, this is a finding.

Fix Text (F-79620r1147888_fix)

Configure Ubuntu OS to compare the system clock at least every 24 hours to the authoritative time source. Add or modify the following line in the "/etc/chrony/chrony.conf" file: server [source] iburst maxpoll = 16 Restart "chrony.service" for the changes to take effect by using the following command: $ sudo systemctl restart chrony.service