Skip to content
Tutorials Center
My learning

Topics

Lesson 29 of 36 ยท Timeline and Artifact Analysis

Super Timelines and Correlation

Learn how super timelines combine file, log and artifact events, how Plaso and Timesketch fit in, and how to filter, de-duplicate and correlate events into attack stages.

A super timeline merges every time-stamped event you can extract from a system into one sorted list: file system times, registry key write times, event logs, browser history, Prefetch, shortcuts and more. A single disk can yield millions of rows. The power is completeness (you see everything near an event); the problem is volume. This lesson explains how super timelines are produced and, more importantly, how to cut them down to a story.

How they are produced

The best-known tool is Plaso (log2timeline.py creates a storage file, psort.py filters and outputs it). Timesketch is a web interface for collaboratively exploring and tagging timelines. Typical commands, shown read-only as an illustration:

Terminal
# Extract events from a disk image into a Plaso storage file
log2timeline.py --storage-file case42.plaso evidence.E01

# Sort, filter by date and write a CSV
psort.py -o l2tcsv -w timeline.csv case42.plaso \
  "date > '2026-11-12 14:00:00' AND date < '2026-11-12 15:00:00'"

The output contains a timestamp, a source type (for example WEBHIST, FILE, REG, EVT), a description and a message. Hash the storage file and record the tool version, since parsers change between releases.

Why volume is the real problem

A fresh Windows install produces hundreds of thousands of events before anyone uses it. Nearly all are normal. The goal is to remove noise safely, which means filtering in ways you can explain.

Strategies:

  1. Time window. Start from the incident and expand outward.
  2. Source filters. For a malware question, look at Prefetch, Amcache, services and file creation before browser history.
  3. Known-good removal. Exclude files that match a known-good hash list (for example a reference database of standard operating system files).
  4. Keyword and path search. Temp folders, user profile roots, unusual extensions.
  5. Stacking (frequency analysis). Count how often each event type or path occurs; rare things are interesting.
  6. Tagging. Mark important rows so they survive into the report.

Filter and stack events

Python Filter a timeline and find rare events

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice that the filter is a rule you can write in the report ("excluded temp files matching a pattern, N rows"). Never delete rows silently: say what you removed and why.

Correlate events into stages

Correlation groups events into steps of a story. A common frame is the attack lifecycle: initial access, execution, persistence, command and control, actions on objectives. Matching rows to stages shows what is known and where there are gaps.

flowchart LR
  A["Initial access: download"] --> B["Execution: Prefetch"]
  B --> C["Persistence: Run key"]
  C --> D["Command and control: outbound"]
  D --> E["Objective: data staged"]

Label each stage with the supporting rows and mark stages with no evidence as unknown.

Python Map events to attack stages

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Keyword matching is crude: it is a note-taking aid, not an analysis. In a real case you assign stages by reading the evidence, and you state your confidence.

De-duplicate and cross-check

Many artifacts record the same moment (a file's creation, a Prefetch run and a registry write for one execution). Group close events (within a second or two) into one "occurrence" with several supporting sources. Three independent sources that agree are strong evidence (Windows artifacts). A claim with only one fragile source should be labeled as such.

Practical advice

  • Start narrow and widen; do not try to read everything.
  • Record every filter, the tool version and the commands.
  • Check parser errors: unparsed sources are silent gaps in the timeline.
  • Preserve both the full timeline and the reduced working one.
  • Present a short, annotated timeline in the report and attach the full data.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a super timeline?

    It combines file, log, registry, browser and other events into one sorted view.
  2. 2. Which tool pair is commonly used to build and filter super timelines?

    Plaso's log2timeline creates the storage file and psort filters and exports it.
  3. 3. What should you do when you remove noise from a timeline?

    Filters must be explainable and repeatable; keep the original data.
  4. 4. Why is frequency analysis (stacking) useful?

    Normal activity is repetitive, so uncommon items deserve a closer look.

Summary

  • Super timelines merge many artifact types; Plaso and Timesketch are standard tools.
  • The challenge is volume: filter by time, source, known-good lists and stacking.
  • Document every filter; never delete rows silently.
  • Map events to stages and mark unknown stages honestly.
  • Corroborate with independent sources and report the evidence level.

Next: Writing a Forensic Report