Time Source Synchronization and Clock Skew
You'll learn why accurate, synchronized timestamps are critical for incident timelines and how to detect and correct for clock drift across systems.
When constructing incident timelines (your previous lesson), you'll quickly discover that not all systems agree on what time it is. A firewall might log an event at 14:32:15, while the compromised server records its infection at 14:29:40—but which happened first? If the server's clock is three minutes fast, the firewall event actually preceded the infection.
Clock skew is the difference between a system's recorded time and true time (typically UTC from an authoritative source). It accumulates when systems drift from a reliable time reference or use incorrect time zones. During forensic analysis, even seconds of skew can create false cause-and-effect relationships or hide the true attack sequence.
Network Time Protocol (NTP)
NTP is the standard protocol for synchronizing clocks across networks. Well-configured systems regularly sync with NTP servers (stratum hierarchy—stratum 0 are atomic clocks, stratum 1 sync directly from them, and so on). However, misconfigured NTP, network issues, or deliberate tampering can cause drift.
Detecting and Correcting Clock Skew
During analysis:
- Identify reference timestamps: Use domain controller logs, network device logs, or external systems with known-good time sources as anchors
- Calculate offsets: Compare timestamps of correlated events (like a TCP handshake seen on both firewall and server) to determine per-system skew
- Document adjustments: Note "+3 min skew on Server-A relative to DC-01" in your analysis notes
- Normalize timelines: Apply corrections consistently when ordering events
Think of it like witnesses at a crime scene with watches running fast or slow—you need to figure out each watch's offset to reconstruct the true sequence of events.
Key Takeaway:
Clock skew corrupts timeline accuracy; always verify time synchronization configurations, identify reference sources, calculate per-system offsets, and document corrections to ensure forensically sound temporal analysis.