10.6.2 Time settings consistent and accurate
Systems are configured to the correct and consistent time, with central time servers receiving time from external industry-accepted sources.
5
artefacts
2
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration showing stratum hierarchy · Cloud console / configuration management
- Time drift monitoring dashboard · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Documented external NTP sources (e.g., NIST, pool.ntp.org) · Document repository
- Sample of corrected drift events · Document repository
- Procedure for time source changes · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- No external source
- Stratum hierarchy unclear
- No drift monitoring
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet10.6.1 Time synchronization in use · 10.6.3 Time settings protected