skip to content

Autopsy

Autopsy, the forensic platform built on The Sleuth Kit: adding a disk image to a case, running ingest modules, reading the timeline and tagging findings. The free suite DFIR candidates practise on.

on this pageshow

explore

questions

6

In Autopsy, what is a case, what is a data source, and which data source types can an examiner add?

level: juniorimportance: must knowfreq 45%

answer

  1. a folder plus a database
  2. case first, evidence second
  3. the evidence is referenced, not copied
  4. image, local disk, logical files
  5. raw, split raw, E01, VMDK, VHD

basics

~20 s

An Autopsy case is a folder with its own case database, settings and reports; a data source is evidence the case references rather than copies: a disk image or VM file, a local disk, logical files or an unallocated space image.

solid answer

~50 s

In Autopsy you create a **case** first, because a data source can only be added to an open case. The case is a directory holding the `.aut` configuration file, the case database, module output and a `Reports` folder; a single-user case uses embedded services, a multi-user case a shared PostgreSQL database and Solr index. A **data source** is the evidence: a *Disk Image or VM File* (Raw Single, Raw Split, `E01`, `VMDK`, `VHD`), a *Local Disk*, *Logical Files*, an *Unallocated Space Image File* or Autopsy Logical Imager results. Autopsy reads it through The Sleuth Kit, which is why it shows volumes and file systems, and stores a reference rather than a copy, so the image must stay reachable at that path while the case is worked. One case can hold several data sources from one or many computers.

go deeper

for a junior

Recall the order: case first, then data sources. Name the data source types and the disk image formats, and say that the case references the evidence rather than copying it.

for a middle

Explain what each wizard choice changes: host, time zone for FAT, orphan file finding, sector size and entered hashes, and why Logical Files never shows unallocated space or deleted files.

for a senior

Show you plan the case around the evidence: one case per matter with several hosts, evidence on a stable path, UNC paths for shared cases, and the data source type the question actually needs.

for a principal

Weigh what the lab standardises: where evidence lives so cases stay openable, when single-user cases suffice, and which data source types are acceptable so nobody drops unallocated space by habit.

## The case is the container Autopsy will not analyse anything until a **case** exists: data sources are added to an open case, never the other way round. You create one from the opening splash screen or the **Case > Create New Case** menu item, giving a case name and a base directory; Autopsy makes a directory for the case inside it. That directory holds: - the case configuration file with the `.aut` extension, which is what you open later; - the **case database**, where Autopsy records an entry for every file it finds and the results, tags and comments that follow; - module output and the `Reports` folder, where generated reports land. A **single-user** case uses embedded services on the examiner's workstation. A **multi-user** case, offered only when Autopsy has been configured with multi-user settings, keeps its data in a shared PostgreSQL database with a shared Solr keyword index so several examiners can have it open at once. The choice is made when the case is created. One case can hold several data sources, from several drives of one computer or from several computers. For matter `2026-0142`, the departing employee's laptop image and a USB stick returned with it can sit in one case under one host or two. ## What a data source is A **data source** is the thing being analysed. The Add Data Source wizard first asks which **host** it belongs to (generate a host from the data source name, specify a new host name, or use an existing host), then its type: | Data source type | What it is | What Autopsy can see | |---|---|---| | Disk Image or VM File | a byte-for-byte copy of a drive or card, or a virtual machine disk | volumes, file systems, deleted files, unallocated space | | Local Disk | an attached device read in place, for example through a write blocker | the same, but files added after it was added are not seen | | Logical Files | chosen files and folders, or a logical evidence (L01) file | allocated files only; their timestamps are ignored by default | | Unallocated Space Image Files | a file with no file system that should still go through ingest | raw content, optionally broken into chunks | | Autopsy Logical Imager Results | the output of Autopsy's own logical imager | whatever that collection captured | The disk image formats the user guide lists are Raw Single (`.img`, `.dd`, `.raw`, `.bin`), Raw Split (`.001`, `.aa`), the `E01` evidence format, and `VMDK` and `VHD` virtual disks. You browse to the first segment only and Autopsy finds the rest. An `AD1` or `AFF` file is not on that list. ## The choices made while adding an image 1. **Orphan file finding on FAT**: optional and slow, because it looks at every sector of the device. 2. **Time zone**: the zone the image came from. FAT stores no time zone, so Autopsy needs this to normalise FAT times to UTC; a wrong answer shifts every FAT timestamp in the views and the timeline. 3. **Sector size**: Auto Detect works for most images; another size is a fallback when adding fails. 4. **Hashes**: optional values saved in the image metadata, which the Data Source Integrity module can verify later. An `E01` already carries its own. 5. **Ingest modules**: chosen next, or an ingest profile if the lab has saved one. Autopsy then makes a basic pass that populates the case database with an entry for each file; you can browse while the ingest modules keep running. ## Reference, not copy Autopsy does **not** copy the data source into the case folder; the case holds a reference to it. An image at `E:\Evidence\2026-0142\WS-FIN-07.E01` must stay reachable at that path for the duration of the analysis. In a multi-user case every client must reach it at the same path, which is why the documentation recommends UNC paths. Logical Files deserve a second look. Their timestamps are ignored by default because they may be the times the files were copied to the examination machine, and a USB stick added this way shows only its allocated files: no unallocated space and no deleted files. ## The Sleuth Kit underneath Autopsy describes itself as a graphical interface to **The Sleuth Kit** and other open-source tools. The Sleuth Kit's library layers read the image format, then the volume system (DOS and GPT partition tables among others), then the file systems (NTFS, FAT and exFAT, ext2/3/4, HFS+, APFS, ISO 9660 and more). That is why a data source appears in the tree as volumes and file systems rather than as one opaque file. ## Where Autopsy stops Autopsy is built to examine evidence that has already been acquired; producing and verifying the image is the imaging step's job, even though a Local Disk source can optionally be copied to a VHD during analysis. Adding a data source records what is there. It does not decide what any of it means; that is the examiner's work after ingest.

  • Why does Autopsy ask for a time zone when you add a disk image?
    FAT file systems store no time zone, so Autopsy uses the zone you pick to normalise their times to UTC. Pick the wrong zone and every FAT timestamp in the file views and the timeline is shifted by the difference. The user guide calls it most important for FAT; record the zone you chose in your notes.
  • What do you lose by adding a suspect USB stick's folders as Logical Files instead of adding the device or its image?
    Logical Files sees only allocated files, so unallocated space and deleted files never enter the case, and the PhotoRec Carver has nothing to carve. Their timestamps are also ignored by default, because they may be copy times. The guide says to add the device itself to analyse unallocated space.
  • Can you move the evidence drive after adding an E01 to an Autopsy case?
    Not freely. The case stores a reference to the image, not a copy, so the data source must stay accessible at that path while the case is analysed. For multi-user cases every client needs the same path, which is why UNC paths are recommended over mapped drive letters.

  • Adding a data source copies the disk image into the case folder.
  • You can load the evidence first and create the Autopsy case afterwards.
  • Adding a USB stick as Logical Files still shows its deleted files.
  • Autopsy's Add Data Source wizard takes an AD1 image like any disk image.
  • An Autopsy case can only hold one data source.
  • The time zone choice cannot affect FAT timestamps because FAT stores UTC.
open as a page

In Autopsy, how do files travel through the ingest modules, and why does module order inside the file pipeline matter?

level: middleimportance: must knowfreq 38%

basics

~20 s

Autopsy sends each file down a pipeline, module by module, in an order fixed by its pipeline configuration: Hash Lookup first, then File Type Identification, whose results Extension Mismatch and Keyword Search rely on. Extracted and carved files re-enter the pipeline.

open as a page

In Autopsy's Hash Lookup module, how do known, notable and no-change hash sets differ, and what does an NSRL hit tell you?

level: middleimportance: should knowfreq 32%

basics

~20 s

Hash Lookup matches each file's MD5 against hash sets: known sets mark files to ignore, notable sets flag files of concern, no-change sets record informative matches. An NSRL hit makes a file 'known', which says it was catalogued, not that it is good.

open as a page

In Autopsy's Timeline viewer, what do the Counts, Details and List views each show, and what decides which events appear?

level: middleimportance: should knowfreq 30%

basics

~20 s

Autopsy's Timeline opens in the Counts view, a stacked bar chart of events per period; Details clusters events by description; List shows every event in order. Which events exist depends on the ingest modules that ran; filters decide which are shown.

open as a page

An Autopsy case of a departing employee's laptop image shows no keyword hits and no carved files; how do you find which settings caused the gaps?

level: seniorimportance: should knowfreq 26%

basics

~20 s

Check what ran before trusting the silence: since Autopsy 4.23.0 Keyword Search is off by default during ingest, in-line mode allows no later ad hoc search, and a file filter or Logical Files source keeps unallocated space from the PhotoRec Carver.

open as a page

Should a DFIR lab adopt Autopsy as its standard examination suite, and what must it add so findings survive review?

level: principalimportance: should knowfreq 18%

basics

~20 s

Autopsy can be a lab's standard if the lab pins a release, validates it on reference images, enforces ingest profiles, decides single- versus multi-user deployment, and adds peer review and a second tool for key findings; Autopsy produces leads, not conclusions.

open as a page