Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-32972 | SRG-OS-000056-MOS-000026 | SV-43370r1_rule | Low |
Description |
---|
Determining the correct time a particular application event occurred on a system is critical when conducting forensic analysis and investigating system events. Periodically synchronizing internal clocks with an authoritative time source is needed in order to correctly correlate the timing of events that occur across the enterprise. The two authoritative time sources for mobile operating systems are an authoritative time server which is synchronized with redundant United States Naval Observatory (USNO) time servers as designated for the appropriate DoD network (NIPRNet or SIPRNet) or the Global Positioning System (GPS). Timestamps generated by the audit system in mobile operating systems shall include both date and time. The time may be expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. |
STIG | Date |
---|---|
Mobile Operating System Security Requirements Guide | 2012-10-01 |
Check Text ( C-41272r1_chk ) |
---|
Examine the mobile operating system configuration to determine if the internal clock synchronizes at least once every 24 hours with an authoritative time server or the Global Positioning System. If the mobile operating system does not synchronize the internal clock with an authoritative time source at least once every 24 hours under normal operating conditions, this is a finding. If the mobile operating system is not synchronizing the internal clock with an authoritative time server or the GPS, this is a finding. |
Fix Text (F-36886r1_fix) |
---|
Configure the mobile operating system to synchronize the internal clock at least once every 24 hours with an authoritative time server or the Global Positioning System. |