CMMC Practice AU.2.043



CMMC Version 1.02, pg. 89

Bold Coast Security Guidance

Imagine having a different time in each bedroom of your house? If they're off by a minute or two, its no big deal. But off by 30 minutes? An hour? What if one person is on Eastern Time and another on Pacific? What time did everyone get up today? The same problem would occur on your network if you are trying to trace a problem on your network, and everyone is using a different time source. Differences of even a second may lead to incorrect conclusions about what happened when doing an investigation. There are several "authoritative" time servers out there which you can use. Pick one and its backup, and use it across your network. And remember to verify your setting on a regular basis! Operating systems can shed settings like this due to faulty patches, mistakes by administrators, or malicious activity.

Discussion From Source

DRAFT NIST SP 800-171 R2 Internal system clocks are used to generate time stamps, which include date and time. Time is expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. The granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks, for example, clocks synchronizing within hundreds of milliseconds or within tens of milliseconds. Organizations may define different time granularities for different system components. Time service can also be critical to other security capabilities such as access control and identification and authentication, depending on the nature of the mechanisms used to support those capabilities. This requirement provides uniformity of time stamps for systems with multiple system clocks and systems connected over a network.