10.6.3 Time settings protected
Time synchronization settings and data are protected, with access to time data restricted and changes logged and monitored.
5
artefacts
3
held by a system
0
at each review
easy
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- RBAC on NTP configuration · Cloud console / configuration management
- Audit log of NTP configuration changes · SIEM / log platform
- Sample monitoring records · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Alerting on NTP source changes · Policy repository / GRC workspace
- Procedure for approved time changes · Policy repository / GRC workspace
First move
Automate the pull from your SIEM / log platform. Retention and alert rules exported from the SIEM; review evidence is the closed-alert record with reviewer and time.
Common gaps auditors find
- Anyone can change time
- Changes not logged
- No alerts
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.2 Time settings consistent and accurate · 10.7.1 Critical security control failure detection (SP)