Ir al contenido

Disk Analysis and Autopsy

In this case study, we start from a scenario provided by TryHackMe (autopsy2ze0) where we are provided with an Autopsy case (.aut) and the image...

0views

TryHackMe | Disk analysis and autopsy

In this case study, we start from a scenario provided by TryHackMe (autopsy2ze0) where an Autopsy case (.aut) and the corresponding disk image (.E01) are provided.

Unlike a standard investigation where we would create a case from scratch, here we face a scenario of collaboration or review, where a pre-existing case must be opened on a new analysis machine.

Before starting, it is fundamental that we understand what the .aut file is.

  • It is not the evidence: It does not contain the disk image (.E01).
  • This is the case file: It's a database (SQLite) that stores all the metadata of our investigation. This includes:
    • The path (or pointer) to the data source (the image E01).
    • All results from the ingestion modules (keyword indices, hashes, extracted artifacts, etc.).
    • Any tag (Tag), note, or report we have generated.

The THM scenario informs us that “the ingestion modules have already been run.” This means the .aut file they provide already contains all those results, saving us hours of processing.

Our first step is to open the “case file” on our forensic workstation.

  1. We will start Autopsy.
  2. On the welcome screen, we will select the option “Open Existing Case”.
  3. We will navigate to the location of the .aut file provided in the TryHackMe room and open it.

Once the case is open, we will encounter a fundamental forensic step: re-linking the evidence.

The Problem (The “Why”):

Autopsy will show a critical warning. In the “Data Sources” panel, we will see the disk image (.E01) listed, but marked with an error (usually a red icon ❗️).

This occurs because the .aut file stores the original absolute path where the image was located when the case was created (e.g., C:\MaquinaDelCreador\Desktop\imagen.E01). That path does not exist on our analysis virtual machine.

The Solution (The “How”):

Autopsy detects this discrepancy and provides us with the solution.

  1. A warning will appear ('Data source is missing') asking if we want to locate the file. We'll select “Yes”.
    • Alternatively: If the warning does not appear, we can right-click on the corrupt data source (with the error icon) and select .
  2. A file explorer will open.
  3. We will navigate to the current location of the disk image .E01 within our virtual machine (e.g., C:\Users\Administrator\Desktop\evidence.E01).
  4. We will select the file.

The Result:

Autopsy will verify the image. It will “connect” the database .aut (with all pre-calculated ingestion results) to the physical data source. The error icon will disappear.

At this point, the case is fully loaded and ready for analysis. All artifacts previously found by the ingestion modules (as seen in “Results” > “Extracted Content”) are now available for our manual review.