Email and Cyber Security · #73
Online Security Incident Timeline Builder
Merges EDR, firewall, SIEM and team notes into one sorted, time-zone-corrected timeline.
- Data is processed in your browser and not sent to a server
- Export: CSV
Tool
What does this tool do?
After a security incident the answers to 'when did it start, when did we notice, when did we stop it' are spread across systems logging in different time zones. The tool converts timestamps to UTC, sorts events, shows elapsed time from the first event (T+) and long logging gaps; with a phase column it calculates time to detect (TTD) and time to contain (TTC).
How to use it
- CSV header:
time, eventrequired;source, host, user, phaseoptional. phase: initial, detect, contain, recover (TR/DE equivalents accepted). - Enter the offset (e.g. +03:00) for timestamps without a zone and the gap threshold (minutes).
- Press Run; attach the timeline as CSV to the incident report.
Fields
- Event records (CSV)
- Time: YYYY-MM-DD HH:MM[:ss][Z|±HH:MM] or DD.MM.YYYY HH:MM.
- Default time zone
- Used when a timestamp has no zone.
- Gap threshold (min)
- Gaps longer than this between consecutive events are flagged.
Worked example
| Input | Value |
|---|---|
| Event records (CSV) | |
| Default time zone | +03:00 |
| Gap threshold (min) | 60 |
Expected result: 7 events over 12 h 16 min; first sign at 02:14, analyst confirmation at 07:05: time to detect 4 h 51 min, containment 27 min. Four long gaps flagged.
The gap of more than 3 hours between the successful logon at 03:40 and confirmation at 07:05 is when the attacker moved most freely; DC01 and WS-114 logs for that window need separate review. To shorten detection, consider automatic forwarding of EDR alerts to the SOC at night.
Second scenario
| Input | Value |
|---|---|
| Event records (CSV) | |
| Default time zone | +03:00 |
| Gap threshold (min) | 60 |
Expected result: Three formats (Z, local default +03:00, +02:00) sort correctly as 10:00, 10:05 and 10:30 UTC.
Method and assumptions
If a timestamp contains Z or ±HH:MM it is used, otherwise the default zone applies; sorting is by UTC, ties keep input order.
TTD = first 'detect' − first 'initial' (or first event). TTC = first 'contain' − first 'detect'. Gap = time between consecutive events > threshold.
Using the result and troubleshooting
Attach the timeline to the incident report and lessons-learned meeting; gaps reveal missing log coverage, long TTD reveals monitoring issues. Pass fields with personal data through the Log Masking tool before sharing.
Limits and common mistakes
- Accuracy of source system clocks (NTP drift) is unknown; sub-second ordering is not exact. Daylight saving changes must be entered via the offset.
Frequently asked questions
How do I merge logs from different time zones without mistakes?
Export each source with an offset (ISO 8601, e.g. 2026-11-20T02:14:00+03:00) or UTC (Z) if possible. The default zone here is right for only one source; fix sources separately and then merge.
Related tools and service
- Log Masking ToolMasks personal and secret data on your device before you share logs with third parties.
- Windows Event XML ViewerTurns event XML from Event Viewer or PowerShell into a readable table and CSV.
Related service: Cyber Incident Response and Exercises