Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 37 ยท Projects and Practice

Project: Reconstruct an Incident Timeline from a Capture

Practice incident response analysis: take a sample capture of a suspicious host, extract key events, order them in a timeline, and write a clear findings report.

When something goes wrong, the first question is "what happened, and in what order?". A timeline answers that. In this project you will analyze a sample incident, an invented one, and build the timeline with Wireshark-style steps and a script that sorts events from different sources.

The data is fictional (documentation IP ranges and made-up names). Use the same method only on captures you are authorized to examine, and handle real captures as sensitive evidence.

The scenario

An office laptop, 10.0.0.42, was reported "acting strangely" after its user opened an email attachment. You have a one-hour capture taken at the office gateway. Your goals: find when the odd behavior began, what the laptop contacted, and whether data left the network.

Step 1: triage

Work through these views, writing down findings as you go.

  1. Capture File Properties: time range, packet count, interface.
  2. Protocol Hierarchy: anything unexpected? (A large amount of DNS or an unusual protocol.)
  3. Conversations, IPv4: sort by bytes. Where did 10.0.0.42 send most data?
  4. Filter the host: ip.addr == 10.0.0.42.
  5. DNS: dns && ip.src == 10.0.0.42. List the names it asked for, and the failures.
  6. TLS and HTTP: server names (SNI), user agents, paths.
  7. Time gaps: I/O Graph for the host, to see when activity started.

Step 2: record events

Each important observation becomes one row: time, source of evidence, what, and the packet number.

TEXT
Time (UTC)  Pkt     Event
10:02:11    1204    DNS query for docs-share.example.net from 10.0.0.42 (new name)
10:02:12    1209    HTTP GET /invoice.zip from 198.51.100.20 (download, 412 KB)
10:03:40    2310    DNS queries for 25 random-looking names, most NXDOMAIN
10:04:02    2688    TLS Client Hello, SNI update-check.example.org, to 203.0.113.80
10:34:02    7410    same destination again (30 minutes later)
10:41:15    8802    upload of 38 MB to 203.0.113.80

Note that a download, DNS noise, a first contact, repeated contact, and a large upload together tell a story that each row alone would not. Compare the patterns in Malware Traffic and Beaconing.

Step 3: build the timeline in code

Events come from several places: a capture, firewall logs, DNS logs. A script that merges and sorts them by time makes the story easy to read.

Python Merge evidence sources into a timeline

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.

Times must be in one time zone and from synchronized clocks. Write the zone in your report.

Step 4: quantify the impact

Answer concrete questions with numbers.

Python How much data left, and to where?

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.

Step 5: write the report

A clear incident note has these parts:

  1. Summary: two or three sentences for a manager.
  2. Scope: hosts affected, time range, evidence used.
  3. Timeline: the table above.
  4. Indicators: IPs, domains, file names and hashes observed.
  5. Impact: data volume and destinations, confidence level.
  6. Recommendations: isolate the laptop, reset credentials used on it, block the indicators, scan for the same indicators on other hosts, user education.
  7. Limits: "TLS content was not decrypted; conclusions about the upload rely on size and destination only."

State what you know separately from what you infer. An analyst who says "I believe" and shows the packets is trusted more than one who is certain without evidence.

Preserve the original capture with a checksum (for example SHA-256) and work on copies. If the matter might become legal, keep a note of who handled the file and when.

Extensions

  • Add a column with the Wireshark filter that finds each event.
  • Cross-check each indicator against a threat-intelligence source.
  • Turn the timeline into a diagram (a mermaid sequence diagram) for the report.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why merge events from several sources into one timeline?

    Different sources confirm one another and reveal gaps, so the story becomes reliable.
  2. 2. What must be true about timestamps from different systems?

    Mismatched clocks or zones misorder events and break the story.
  3. 3. How should an analyst present uncertain conclusions?

    Clear confidence levels and limits make a report trustworthy.
  4. 4. Why keep the original capture untouched and work on copies?

    An unmodified original with a recorded checksum supports later review.

Summary

  • Triage with statistics, then filter to the host in question.
  • Record each event with time, evidence and packet number.
  • Merge sources into one sorted timeline, in one time zone.
  • Report facts, inferences, impact and recommendations, and preserve the original evidence.

Next: Project: A Retransmission Report Tool