Time Synchronization
Also called NTP, Clock Sync.
Keeping system clocks aligned so log timestamps can be correlated.
What it is
Time synchronization keeps the clocks of systems across an environment aligned to a common reference, most commonly using the Network Time Protocol. Consistent, accurate time is what lets timestamps from different sources be placed on a single shared timeline.
Why it matters
Without synchronized clocks, correlating events across hosts and devices becomes unreliable and a coherent incident timeline may be impossible to build. Recording the time zone and offset alongside synchronization is equally important, since a skewed or misconfigured clock can scatter related events or hide their true order.
In practice
Reconstructing an attacker's hop between two servers only because both were NTP-synced, so their logon timestamps lined up to the second.
What to look for
- Clock drift between hosts and log sources.
- NTP sources that are internal and trusted.
- Logs recorded in local time without offsets.
Common mistake
Correlating logs from unsynced clocks. A few minutes of drift can reverse the order of events.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Splunk Enterprise Security Commercial
A SIEM where these logs are searched with SPL and turned into correlation searches.
-
Microsoft Sentinel Commercial
Microsoft's cloud SIEM, queried with KQL and fed by connectors for these log sources.
-
Elastic Security Commercial
A SIEM built on Elasticsearch, with a detection rules library and timeline investigations.
-
Wazuh Open source
An open source platform that collects, decodes and alerts on host and log data.
Read next
- Log Aggregation: Collecting logs from many sources into a central, searchable store.
- Log Normalization: Mapping diverse log formats onto a single common schema.
- Log Forwarding: Transmitting logs off their source host to a remote collector.