Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Timeline analysis merges timestamps from file systems, logs, registry hives, and cloud services into one ordered narrative, turning scattered artefacts into a sequence of events.

What Is Timeline Analysis?
Timeline analysis is the practice of extracting every available timestamp from the evidence, normalising it, and ordering it into a single sequence. Individually, a registry key write and a file creation and a firewall entry are three facts. Placed in order, with the right filter applied, they become the account of how an intrusion unfolded.
It is the technique that answers the questions clients actually ask: when did this start, how did they get in, what did they take, and is there a second route in that nobody has found.
$STANDARD_INFORMATION and $FILE_NAME attributes, giving eight values per file.$LogFile record operations that the MFT alone does not preserve.A super timeline, built with plaso through log2timeline and reviewed in Timesketch or a spreadsheet, extracts everything from an image. A single workstation can produce several million events, which is simultaneously its strength and its problem.
Experienced analysts therefore build two. The first is a targeted timeline drawn from a handful of high-value sources, typically the MFT, the USN Journal, key event log channels, registry execution artefacts, and prefetch, parsed with Eric Zimmerman’s tools and reviewed in Timeline Explorer. That narrows the window to hours. The full timeline is then generated only for that window, where the volume becomes manageable and the detail is worth reading.
Working outwards from a known point is the standard method. Start at the one event you are certain of, perhaps an alert or a ransom note, and expand the window in both directions until the activity stops being related. Attackers rarely act in isolation: a malicious file creation is normally preceded within seconds by a network connection and followed within minutes by a persistence mechanism.
Three problems recur in every engagement, and all three are UK-specific in part:
TimeZoneInformation registry key records what the system believed at the time.Look for clustering rather than for individual entries. A dozen file creations, a service installation, and a new scheduled task inside ninety seconds describe an automated tool running, not a user working. Look for gaps: an hour of silence in the middle of an otherwise busy intrusion often marks the point where the attacker was using a different host. Look for first and last occurrences, because the earliest reliable artefact defines the dwell time you will have to report, and the latest defines whether containment worked.
Finally, write the timeline down in narrative form as well as tabular form. A table of two hundred rows is evidence; three paragraphs explaining what those rows show is what the board, the regulator, and ultimately a court will actually read. Building both is standard practice in our Investigation and Incident Response Services.
A super timeline is a combined chronology built from every timestamped source in an image: file system metadata, event logs, registry hives, browser databases, and application artefacts. Tools such as plaso generate them automatically. The output can run to millions of events for a single machine, so it is normally filtered to a window identified through a smaller targeted timeline first.
Records held outside the compromised host are the most dependable, because the attacker cannot alter them: cloud audit logs, firewall and proxy records, and email headers from a mail platform. On the host itself, the NTFS $FILE_NAME attribute and the USN Journal resist tampering better than the commonly modified $STANDARD_INFORMATION values that most timestomping tools target.
Normalise everything to UTC and state the local offset that applied on each date, rather than converting to local time in the timeline itself. The TimeZoneInformation registry key records what the system believed its zone and bias to be. Cases spanning the clock changes in late March or late October are where the hour of error most often appears.
Start narrow. Build a targeted timeline from the Master File Table, USN Journal, selected event log channels, registry execution artefacts, and prefetch, then use it to identify a window of hours rather than weeks. Generate the full timeline only for that window, filter by the directories and accounts involved, and expand outwards from each confirmed event.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.