What evidence do auditors commonly ask for on LOG-06 Clock Synchronization?

NTP or time service configuration on hosts and network devices; Monitoring of clock drift; Policy naming the authoritative time source; Sample logs with consistent timestamps across systems.

What is the most common gap auditors find on LOG-06?

Some appliances on default unsynchronised clocks

CSA CCM v4.1 · LOG - Logging and Monitoring

`LOG-06` Clock Synchronization

Use a dependable time source across every relevant information processing system.

Source: CSA CCM v4.1, LOG-06. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.

Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.

artefacts

held by a system

at each review

easy

to go live

Endpoint management (MDM / EDR)

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

NTP or time service configuration on hosts and network devices · Endpoint management (MDM / EDR)
Sample logs with consistent timestamps across systems · SIEM / log platform

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Monitoring of clock drift · Policy repository / GRC workspace
Policy naming the authoritative time source · Policy repository / GRC workspace

First move

Automate the pull from your Endpoint management (MDM / EDR). Device compliance report from the MDM (encryption, EDR agent, OS version) on a daily pull.

Common gaps auditors find

Some appliances on default unsynchronised clocks
Different time zones across log sources hampering correlation
Drift not monitored

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 sheet

LOG-05 Audit Logs Monitoring and Response · LOG-07 Logging Scope