Vulnerability Discussion

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).

Satisfies: SRG-OS-000355-GPOS-00143, SRG-OS-000356-GPOS-00144

Check

The SUSE operating system clock must be configured to synchronize to an authoritative DoD time source when the time difference is greater than one second.

Check that the SUSE operating system clock must be configured to synchronize to an authoritative DoD time source when the time difference is greater than one second with the following command:

> sudo grep maxpoll /etc/chrony.conf

server 0.us.pool.ntp.mil maxpoll 16

If nothing is returned, "maxpoll" is greater than "16", or is commented out, this is a finding.

Verify the "chrony.conf" file is configured to an authoritative DoD time source by running the following command:

> sudo grep -i server /etc/chrony.conf
server 0.us.pool.ntp.mil

If the parameter "server" is not set, is not set to an authoritative DoD time source, or is commented out, this is a finding.

Fix

The SUSE operating system clock must be configured to synchronize to an authoritative DoD time source when the time difference is greater than one second.

To configure the system clock to synchronize to an authoritative DoD time source at least every 24 hours, edit the file "/etc/chrony.conf". Add or correct the following lines by replacing "[time_source]" with an authoritative DoD time source:

server [time_source] maxpoll 16