Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 36 ยท Getting Started

Forensic Toolkit and Lab Setup

Tour the standard digital forensics toolkit (imagers, analysers, memory and network tools) and learn how to build a safe, isolated practice lab without touching real evidence.

A forensic examiner relies on a small set of trusted tools and a workspace where mistakes cannot damage evidence. You do not need expensive hardware to learn. A laptop, a virtual machine and a few free tools are enough, as long as you practice only on data you created or that was published for training. This lesson names the common tools by job, shows what a lab looks like, and explains how to check that a tool does what it claims.

The tool outputs shown as plain code blocks in this course are read-only sample output, written to look realistic. They are not produced by this page. The runnable examples are small Python stand-ins that teach the same ideas on made-up data.

Tools by job

Job Free and open-source examples Commercial examples
Imaging / acquisition dd, dc3dd, ewfacquire, FTK Imager (free) X-Ways, EnCase
Disk and file-system analysis The Sleuth Kit (fls, icat, mmls), Autopsy EnCase, FTK, Magnet AXIOM
Carving and recovery foremost, scalpel, photorec Many suites include carving
Memory analysis Volatility 3, Rekall (archived) Magnet RAM Capture, Belkasoft
Network analysis Wireshark, tcpdump, Zeek, NetworkMiner Network-recorder appliances
Timelines Plaso (log2timeline), Timesketch Suite features
Mobile ALEAPP / iLEAPP, libimobiledevice Cellebrite, Oxygen
Hashing and triage sha256sum, hashdeep, KAPE (collection) Suite features

Learn the ideas in open tools first. The concepts carry over to commercial suites, which mostly package the same steps behind a friendlier interface.

Hardware and workspace

  • Write blockers (hardware or software) sit between a suspect drive and your computer so that nothing can be written to it by accident (details).
  • Storage: an image is as large as the disk, so labs need plenty of space and a separate drive for case data.
  • A dedicated analysis machine that is never used for browsing or email, because opening unknown files can run malicious code.
  • Evidence storage: locked, labelled, with an access log.
  • Notes: a bound notebook or a controlled digital log.

A safe practice lab

For learning, build everything virtual:

flowchart TD
    H["Host computer"] --> V1["Analysis VM<br/>(forensic tools)"]
    H --> V2["Practice target VM<br/>(made-up user data)"]
    V1 --- N["Host-only network<br/>(no internet)"]
    V2 --- N
    H --> S["Case folder<br/>images, notes, hashes"]

The target VM is something you built yourself. The host-only network keeps everything away from the internet.

Practice data you can use legally: images you create from your own test VMs, public training images published by forensic educators (check each licence), and the made-up data in this course. Never practise on a friend's phone or a used drive from an auction site.

Read-only sample output

This is what an fls listing of a small file system image looks like (sample output, not run here):

TEXT
$ fls -r practice.dd
d/d 11:    lost+found
r/r 12:    notes.txt
d/d 13:    photos
+ r/r 14:  holiday.jpg
+ r/r * 15:    (deleted) receipt.pdf

The * marks a deleted entry whose name still survives in the directory. You will meet this idea again in deleted files and slack space.

Validate your tools

Forensic tools can have bugs, and courts may ask whether yours were tested. A practical habit is to run a tool on a known data set where you already know the right answer, and compare. The stand-in below plays that role for a file-signature identifier: it is checked against samples whose true types are known.

Python Validating a tool against known answers

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.

If a test fails you investigate before using the tool on real evidence, and you note the tool version in your report.

Keep a tool log

Reports must say which tool and version produced each result, because behaviour changes between versions. The next stand-in records that metadata automatically.

Python Recording tool name and version with each result

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.

The tool names here are invented. In real work you would copy the exact version string the program prints.

Safety rules for the lab

  • Never open evidence files with normal desktop programs; use tools that treat them as data.
  • Keep the analysis VM disconnected from the internet unless you need it.
  • Take snapshots before experimenting, so you can return to a clean state.
  • Hash every image you create and store the hash separately from the image.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which tool class prevents accidental writes to a suspect drive?

    Write blockers sit between the drive and the examiner's computer and refuse write commands.
  2. 2. Why test a forensic tool on a known data set?

    Known inputs with known outputs show whether the tool behaves as claimed.
  3. 3. Where is it appropriate to practise?

    Practise only with data you created or have permission and licence to use.
  4. 4. The * in an fls listing marks what?

    In The Sleuth Kit output the asterisk marks a deleted directory entry.

Summary

  • Tools are chosen by job: imaging, file-system analysis, carving, memory, network, timelines, mobile.
  • A lab means a dedicated analysis machine, storage, write blockers and careful notes.
  • Practise only on data you created or have legal permission to use.
  • Validate tools on known data and record the version of every tool in your report.
  • Open-source tools teach the concepts that commercial suites package.

Next: Bits, bytes and hex for examiners