By now you have artifacts from everywhere: deleted files, registry keys, event logs, memory. On their own they're puzzle pieces. A timeline puts them in order and turns them into a story, and the report tells that story so anyone can check it.
Understanding timestamps
Most file systems record a set of times for every file, often called MACB:
| Letter | Meaning |
|---|---|
| M | Modified: the file's content changed |
| A | Accessed: the file was read (often disabled or delayed for performance) |
| C | Changed: the metadata changed (Linux), or the MFT entry changed (NTFS) |
| B | Born: the file was created |
Tip: Always work in UTC. Mixing a server in UTC, a laptop in IST (UTC+5:30) and a firewall in US time is the fastest way to get a timeline wrong.
Quick timeline with The Sleuth Kit
fls -r -m / case01.img > bodyfile.txt
mactime -b bodyfile.txt -d -z UTC > timeline.csv
Super timeline with Plaso
Plaso (log2timeline) goes further. It pulls times from hundreds of sources at once (file system, event logs, registry, browser history, Prefetch, LNK files) into one super timeline:
log2timeline.py --storage-file case01.plaso case01.img
psort.py -o dynamic -w case01-timeline.csv case01.plaso
Open the CSV in Timeline Explorer (free, by Eric Zimmerman) or a spreadsheet, and filter to the hours around the incident.
Turning rows into a story
Start from one solid anchor, such as the first malicious login, and work forwards and backwards:
| Time (UTC) | Source | Event |
|---|---|---|
| 02:13:05 | Security.evtx, 412 × 4625 | Password guessing against "admin" from an outside IP |
| 02:19:41 | Security.evtx, 4624 type 10 | Successful Remote Desktop logon as admin |
| 02:21:10 | Prefetch | MIMIKATZ.EXE executed |
| 02:24:55 | System.evtx, 7045 | New service "WinUpdateSvc" installed |
| 02:31:02 | $MFT | backup.zip (2.1 GB) created in C:\Users\Public |
| 02:47:30 | Security.evtx, 1102 | Security log cleared |
Every row must point to the exact artifact that proves it.
Writing the forensic report
A good report can be read by a manager in two minutes and checked by another analyst in two hours.
1. Executive summary. What happened, the impact and the key recommendation, in plain language.
2. Scope and case details. Who asked for the investigation, which questions you had to answer, and the dates.
3. Evidence list. Every item with its ID, description and SHA-256 hash.
4. Tools and method. Each tool with its version, and the steps you followed.
5. Findings. Each finding with the artifact that supports it, its UTC timestamp and a screenshot or excerpt.
6. Timeline. A clean version of the table above.
7. Conclusion and recommendations. Root cause, what to fix and how to detect it next time.
8. Appendix. Hashes, raw tool output and chain-of-custody forms.
Rules that make a report trustworthy
- Separate facts ("Prefetch shows MIMIKATZ.EXE ran at 02:21:10 UTC") from opinions ("this suggests credential theft").
- Never claim more than the evidence supports.
- Another analyst should be able to repeat your steps and get the same result.
- Write the main report for a non-technical reader, and put the technical proof in the appendix.
Collection, analysis and timelines are what you do. The report is what people remember. Make it clear, honest and repeatable.