Ir al contenido

Autopsy

This chapter introduces the Autopsia platform and establishes the methodological workflow that we will follow in all forensic analysis. It is based on...

0views

TryHackMe | Autopsy

This chapter introduces the Autopsy platform and establishes the methodological workflow that we will follow in every forensic analysis. It is based on Tasks 1 and 2 of the Autopsy room on TryHackMe.

Autopsy is an open-source digital forensics platform and a graphical user interface (GUI) for the powerful collection of The Sleuth Kit (TSK) command-line tools. It is designed to be fast, easy to use, and extensible.

The official description defines it as:

“Autopsy is the leading open-source forensics platform that is fast, easy to use, and capable of analyzing all types of mobile devices and digital media. Its plug-in architecture allows for the extensibility of community-developed or custom modules.”

It is an industry-standard tool, used by both law enforcement agencies and corporate investigators to analyze disk images, file systems, and mobile devices.

Based on the TryHackMe module, our objectives for this manual are:

  • We will understand the Autopsy tool workflow.
  • We will identify and analyze the different Data Sources.
  • We will master the use of Ingest Modules for automated analysis.
  • We will navigate the User Interface and visualization tools fluently.

In this initial task, the goal is simply to start the virtual machine (VM) provided by TryHackMe, which already has Autopsy installed and an example case ready to be analyzed.

Task 1 Question:

We will start the virtual machine.

Response:

No response is required, we will only complete the action.

Before starting an analysis, it is crucial to follow a methodological procedure. Autopsy is designed to guide us through this process.

Our analysis will always follow these five fundamental steps:

  1. Create/Open Case: We will generate a container (the case) for the investigation.
  2. Select Data Source: We will add the digital evidence (disk image, files, etc.) to the case.
  3. Configure Ingest Modules: We will select the automated analyses that Autopsy will run on the evidence (e.g., searching web history, extracting images, etc.).
  4. Artifact Review: We will investigate the results extracted by the ingest modules.
  5. Create Report: We will generate a final report with the findings.

The first step of any investigation in Autopsy is case management.

When starting Autopsy, we'll select the “New Case” option. This will open the 'Case Information' wizard, where we need to define three critical parameters:

  • Case name: A descriptive name for the investigation (e.g., THM-Autopsy-Room).
  • Base directory: The root folder on our machine where Autopsy will store all files related to this case (logs, databases, reports, etc.).
  • Case Type:
    • Single-user: The case is local and only one analyst will work on it at a time. This will be the standard mode for our manual.
    • Multi-user: The case is hosted on a central server, allowing several analysts to collaborate on the same evidence simultaneously.

The next screen, “Optional Information” (Case number, Examiner name), is vital in a real forensic environment to maintain the chain of custody and report integrity, although it is optional for our exercises.

If we have already created a case, we can reopen it using the “Open Existing Case” (Open Existing Case) option.

Autopsy will create a main file for each case that acts as the “index” of the entire investigation. This file will have the extension .aut.

To open our TryHackMe case, we will navigate to the case folder (located on the VM Desktop) and select the Sample Case.aut file.

Important Note: If Autopsy cannot locate the original disk image associated with the case (because it has been moved or deleted), it will show a warning. It will allow us to continue to analyze the already processed results that are saved in the case database.

Task 2 Question:

What is the file extension of Autopsy files?

Response:

.aut

Additional Instruction:

We will import the “Sample Case.aut” file (located on the desktop) as shown in the task and proceed to the next task.

(Upon completing this, we will be ready to move on to Task 3, which we will cover in our next chapter.)

This chapter details the second step of our workflow: adding digital evidence to the case. It is based on Task 3 of the Autopsy room on TryHackMe.

Once a case is open, Autopsy will immediately present the “Add Data Source” wizard. If we close this window or want to add a second piece of evidence later, we can access it at any time from the toolbar.

Upon clicking, Autopsy will ask what type of data source we want to analyze. The main options will include:

  • Disk Image or VM File: This is the most common option and the one we will primarily use. It refers to a forensic image (a bit-for-bit dump) of a hard drive, a USB drive, an SD card, or a virtual machine file.
  • Local Disk: Allows analyzing a physical disk (HDD, SSD, USB) connected directly to our analysis machine.
  • Logical Files: Allows adding a folder or a set of individual files, instead of a full disk image.
  • Unallocated Space Image File: Allows analyzing a file that contains only the unallocated space of a disk, which may have been previously extracted.

For our manual, we will focus on the “Disk Image or VM File” option. Autopsy is compatible with a wide variety of industry-standard forensic image formats. The most important ones are:

  • Raw (Simple/Divided):
    • Extension: .img, .dd, .raw, .bin (for simple images).
    • Extension: .001, .002, .aa, .ab (for split images).
    • Description: It is the most basic format, a bit-for-bit copy without compression or additional metadata. If the image is split (e.g., imagen.001, imagen.002), we only need to select the first file (.001 or .aa) and Autopsy will automatically find and assemble the rest.
  • EnCase:
    • Extension: .e01, .e02, etc.
    • Description: It is one of the most popular formats in the forensic field. Unlike the Raw format, the .e01 format (also known as EWF - Expert Witness Format) includes important metadata about the case (examiner name, notes, etc.), uses compression to save space, and stores hashes (digital signatures) of the data, allowing for verification of evidence integrity.
  • Virtual Machines:
    • Extension: .vmdk (VMware), .vhd (Hyper-V).
    • Description: Allows direct analysis of virtual machine hard drives without the need to convert them first.

Task 3 Question:

What is the name of the “e01” format disk image?

Analysis: The question refers to the formal or commercial name of the file format that uses the .e01 extension. As documented above, this is the proprietary format of the Guidance Software tool.

Response:

EnCase

This chapter covers the “brain” of Autopsy's automated analysis: Ingest Modules. It represents the third step of our workflow and is based on Task 4 of the Autopsy room on TryHackMe.

Ingest Modules are small programs or plugins designed to perform specific analysis tasks on the data source. Instead of us (the analysts) having to manually search for each type of artifact, ingest modules do it for us.

Each module is specialized in a task, for example:

  • We will extract web browsing history.
  • We will search for files by their signatures (MIME types).
  • We will identify credit card numbers or IP addresses.
  • We will compare the hash of each file against a known malware database (NSRL).
  • We will extract EXIF metadata from images.

When we run them, the results we find will automatically populate the “Results” section in the Tree Viewer, ready for our analysis.

There are two moments when we can run the ingest modules:

  1. When Adding the Data Source: This is the most common methodology. Immediately after selecting our disk image (as seen in Chapter 2), the wizard shows us the “Configure Ingest Modules” window.
  2. After Adding the Data Source: If we have already loaded the evidence and want to re-analyze it (or run a module that we didn't select at the beginning), we can do so at any time. We right-click on the data source in the Tree Viewer and select “Run Ingest Modules”.

The “Configure Ingest Modules” window is our control panel.

By default, modules are configured to run on all files and unallocated space.

  • Global Settings: Some modules have configurations that apply to all cases. For example, this is where we will configure our hash databases (NSRL) or our global keyword lists.
  • Per-Run Settings: Sometimes, a module will have a yellow warning triangle next to its name. This is not an error. It indicates that the module has options that we can configure only for this specific run. A great example is the “Keyword Search” module, which allows us to add “ad-hoc” keywords just for this case.

Once we click “Finish,” the ingest begins. This process can take anywhere from minutes to many days, depending on the size of the evidence and the number of selected modules.

We can monitor progress in the Status Area, in the bottom right corner of the Autopsy interface. A progress bar will show us which module is running and the percentage completed.

While the modules are running, they can generate real-time alerts if they find “notable” items (marked with a red flag) or “suspicious” items (marked with a yellow flag). These findings will appear in the Inbox, accessible from the toolbar. This will allow us to start investigating critical findings without having to wait for the entire ingest to complete.

This task is purely for reading and is designed to explain the concepts we have detailed above. The TryHackMe room opts not to run the ingest modules in the example case (Sample Case.aut) because it is a time-consuming process, and the case has already been previously processed.

Task 4 Question:

Let's read the previous task.

Response:

No answer is required; we will just complete the task.

Chapter 4: Navigating the Interface and Reporting

Sección titulada «Capítulo 4: Navegando la Interfaz y Reportando»

This chapter is our map of the Autopsy user interface (UI). It covers the 5 main work areas and how we will generate reports with our findings. It is based on Tasks 5 and 6 from the Autopsy room on TryHackMe.

The Autopsy interface is divided into 5 logical sections that work together.

It is the main navigation panel, located on the left. We organize all case information into 5 root nodes:

  • Data Sources: Shows the evidence we have added (e.g., Sample Case.aut). It allows us to explore the file and folder structure just as we would in a Windows explorer, including hidden and deleted files.
  • Views: An incredibly useful section. Instead of navigating through the folder structure, this node groups files by logical categories, regardless of where they are on the disk. Key views include:
    • File Types: We group files by extension (.jpg, .pdf) or by MIME type. The “By MIME Type” view is crucial for detecting files that have been renamed with fake extensions (e.g., a .exe file renamed to .txt).
    • Deleted Files: We group all files that have been deleted.
  • Results: This is where we see the results of the Ingest Modules (Chapter 3)! Each module that finds something creates a subsection here. Common examples:
    • Contenido Extraído
    • Historial Web
    • Información del Sistema Operativo
    • Archivos Interesantes
  • Tags: Shows the files or results that we, the analysts, have manually marked (tagged) during the investigation.
  • Reports: Contains a list of the reports we have generated.

It is the top center window. When we click on any element of the “Tree Viewer” (e.g., the “Results” folder), this panel shows us the list of files or artifacts contained in that element. It has two main tabs:

  • Table: The default view, which shows files in a list with columns (Name, Modification date, Size, etc.).
  • Thumbnail: Very useful when selecting “Images” or “Videos” views, as it provides a visual preview.

It is the bottom center window. When we select a single file in the “Result Viewer”, this panel shows its content. It is our microscope. Its tabs change depending on the file type:

  • Hex: Shows raw data in hexadecimal format.
  • Strings: Extracts and displays any readable text from the file.
  • Media: Shows a preview of images or videos.
  • Application: Attempts to display the content as the original application would (e.g., a text document, a PDF).
  • Metadata: Shows the file's metadata (MAC dates, hash, etc.).

Task 5 also asks us to identify three special columns in the “Result Viewer”:

  • S (Score): Score. Shows a red ! for files tagged as Notable or a yellow triangle for Suspicious.
  • C (Comment): Comment. A yellow page indicates that an analyst has left a comment on that file.
  • O (Occurrence): Occurrence. Indicates how many times this file has been seen in previous cases (requires a configured Central Repository).

Located in the top right corner. It allows for quick (AD-HOC) keyword searches across all evidence, without having to configure a full ingestion module.

Located in the bottom right corner. This is where we monitor the progress bar of the ingestion modules (as discussed in Chapter 3).

Question 1:

Expand the "Data Sources" option; what is the number of available sources?

Analysis:

By expanding the "Data Sources" node in the Sample Case.aut Tree Viewer, we will see the main data source that was loaded.

Response:

4

Question 2:

What is the number of "Deleted" files detected?

Analysis: We will navigate in the Tree Viewer to Vistas -> Archivos Eliminados. Task 5 shows the number in parentheses.

Response:

10

Question 3:

What is the name of the file found in the “Interesting Files” section?

Analysis: We will navigate in the Tree Viewer to Resultados -> Archivos Interesantes -> Interesting Files. Upon selecting this folder, the “Results Viewer” will display the found file.

Response:

LOCK

In addition to detailed navigation, Autopsy offers high-level tools.

By clicking on the name of the data source (just below “Data Sources”), the “Results Viewer” will switch to a “Summary” tab. This is an excellent management view that gives us an instant overview of the evidence:

  • File types: A pie chart showing the distribution (% of images, documents, videos, etc.).
  • OS Version: Identifies the operating system.
  • User Accounts: Lists the user accounts found.
  • Artifacts: Quick counts of web history, USB devices, etc.

This view is fundamental for deciding where to focus our investigation.

The last step of our workflow. Autopsy can compile our findings into a professional report.

  1. We click the “Generate Report” button on the toolbar.
  2. We choose a format. The most common are HTML and Excel.
  3. We configure which results we want to include (all results, specific artifacts only, or only the items we have tagged).
  4. Autopsy will generate the report and save it in the “Reports” folder within our case directory.

The HTML report is interactive and allows us to navigate through the artifacts in a similar way to the Autopsy interface itself.

Question 1:

What is the full name of the operating system version?

Analysis: We will navigate in the Tree Viewer to Resultados -> Información del Sistema Operativo. Upon selecting this option, the “Results Viewer” will show us detailed OS information.

Response:

Windows 7 Home Basic

Question 2:

What percentage of the drive consists of documents? Include the % in your answer.

Analysis: We will select the img_manto-s001.e01 data source in the Tree Viewer to view the “Summary” tab. We will look at the “File Types” pie chart.

Response:

1.2%

Question 3:

Generate an HTML report as shown in the task and view the “Case Summary” section. What is the job number for the “Interesting File Identifier” module?

Analysis: We will follow the procedure: Generar Informe -> HTML -> Siguiente -> Finalizar. We will open the generated HTML report (index.html) and in the “Case Summary” section, we will look for the “Ingest Modules” table.

Response:

12

In this chapter, we will apply the knowledge from previous chapters (Workflow, Data Sources, Ingestion Modules, and User Interface) to solve a forensic investigation scenario.

This chapter is based on the Mini Scenario presented in Task 7 of the Autopsy room on TryHackMe.

Scenario:

“It was suspected that an employee was leaking company data. A disk image of the machine was recovered. We are assigned to perform the initial analysis. Additional actions will be determined based on the initial findings.”

As we mentioned in Chapter 1, the Sample Case.aut file we are opening is a pre-processed case. The original disk image (.e01) is not present on the TryHackMe virtual machine (to save space).

For this reason, if we try to view the content of a file (e.g., in the “Media” or “Hex” tab) in the Content Viewer, Autopsy will not show anything. However, all the metadata and artifacts extracted by the ingestion modules are indeed in the case database. Our analysis will be based on these extracted results, which is the main goal of the room.

Below, we will document the answer to each question in the scenario, detailing the forensic process to find it.

Question 1:

What is the name of a program installed with version number 6.2.0.2962?

Analysis: To find installed software, our first destination is the “Results” node in the Tree Viewer.

  1. We will go to Resultados -> Programas Instalados (Installed Programs).
  2. Upon clicking, the “Results Viewer” (central panel) will show a list of all programs that Autopsy has identified (likely by parsing the Windows Registry).
  3. We will search or sort by the “Version” column until we find 6.2.0.2962.

Response:

eraser 6.2.0.2962

Question 2:

A user has a password hint. What is the value?

Analysis: Password hints are a classic artifact stored in the SAM registry, associated with user accounts.

  1. We will go to Resultados -> Cuentas del Sistema Operativo (Operating System User Accounts).
  2. The “Results Viewer” will show us the detected accounts (e.g., manto).
  3. By selecting the user account manto, the “Content Viewer” (bottom panel) will update.
  4. We will look for the “Password Hint” field.

Response:

IAMAN

Question 3:

Numerous SECRET files were accessed from a network drive. What was the IP address?

Analysis: Access to recent files, especially from network drives, is tracked through LNK files (shortcuts). The Recent Activity module extracts this information.

  1. We will go to Resultados -> Elementos Recientes (Recent Documents).
  2. In the “Results Viewer”, we will filter or search for files containing the word “SECRET”.
  3. Upon selecting one of these files, we will examine the “Path” column. Network paths are identified because they start with \\.
  4. The network path will show the IP address of the file server.

Response:

10.11.11.128

Question 4:

Which web search term has the most entries?

Analysis: The “Web History” ingest module aggregates all searches from different browsers in one place.

  1. We will go to Resultados -> Búsqueda Web (Web Search).
  2. The “Results Viewer” will show us a list of all search terms performed by the user.
  3. We will look for the “Count” column and sort it in descending order to find the most searched term.

Response:

information leakage cases

Question 5:

What was the web search performed on 25/03/2015 21:46:44?

Analysis: Using the same location as the previous question (Resultados -> Búsqueda Web), we will perform a different analysis.

  1. We will go to Resultados -> Búsqueda Web (Web Search).
  2. In the “Results Viewer”, we will locate the “Date” or “Access Date/Time” column.
  3. We will sort by this column and locate the exact entry corresponding to the timestamp 25/03/2015 21:46:44.
  4. We will read the search term in that row.

Response:

anti-forensic tools

Question 6:

What MD5 hash value of the binary appears as an interesting file?

Analysis: In Chapter 4, we identified a LOCK file in “Interesting Files”. However, the question specifies a “binary”. This implies there is another file that the “Interesting File Identifier” module has flagged, likely because it is a .exe or has a suspicious file signature.

  1. We will go to Resultados -> Archivos Interesantes.
  2. We will identify the binary file (e.g., calc.exe).
  3. We will select this file in the “Results Viewer”.
  4. In the “Content Viewer” (bottom panel), we will click on the “Metadata” tab.
  5. We will locate the MD5 hash value.

Response:

fe18b02e890f7a789c576be8abccdc99

Question 7:

What security message did the ‘Informant’ write to themselves on a sticky note? (without spaces)

Analysis: Windows “Sticky Notes” are a common artifact. Ingest modules extract the text from these notes.

  1. We will navigate to Resultados -> Contenido Extraído (Extracted Content).
  2. Within this node, we will look for a subfolder named Sticky Notes.
  3. Upon selecting it, the “Results Viewer” will display the notes found.
  4. In the “Content Viewer”, we can read the text of the note.
  5. Alternatively: We can use the “Keyword Search” tool (top right) and search for terms like “informant”, “security”, or “message”.

Response:

Tomorrow… Everything will be OK…

In previous chapters, we have analyzed artifacts in static views. However, to build a narrative and understand when events occurred, Autopsy provides specialized visualization tools.

This chapter is based on Task 8 of the Autopsy room on TryHackMe and focuses on the most important temporal analysis tool: The Timeline (Timeline).

Autopsy includes several interfaces designed to group and visualize specific types of data in a more intuitive way than result tables:

  • Images/Videos (Images/Videos): A gallery to quickly review all multimedia content.
  • Communications (Communications): A viewer that groups emails, chat messages, and other communication artifacts, showing relationships between accounts.
  • Timeline (Timeline): The tool that we will explore in detail.

This tool allows us to visualize file system events and extracted artifacts (such as web searches, logs, etc.) in chronological order. To access it, simply click the “Timeline” icon in the toolbar.

The Timeline interface consists of three main areas:

  1. Filters (Filters - Left): It allows us to narrow down which events we want to see. We can filter by event type (e.g., only “Web Activity” or only “File System Events”) and by date range.
  2. Events (Events - Top): The main viewing panel. It shows events according to the selected view mode.
  3. Files/Content (Files/Content - Bottom): Upon selecting an event in the top panel, this panel shows the details, similar to the “Result Viewer” and “Content Viewer” of the main interface.

Task 8 highlights three view modes for the “Events” panel:

  • Counts (Counts): This is the default view. It shows a bar chart where the height of each bar represents the amount of events that occurred in that time range (year, month, day). It is excellent for identifying activity spikes.
  • Details (Details): Shows events grouped into “clusters”. A cluster (marked with a green icon and a number) represents multiple events that occurred very close together in time. You can click on the green + to expand the cluster and see the individual events.
  • List (List): The most granular view. It shows each event as a row in a table, similar to the main “Result Viewer”.
  • Expand/Collapse Clusters: In the “Details” view, we will use the + (green) and (red) icons to navigate through the event groups.
  • Pinning (Pinning): The map marker icon will allow us to “pin” an event, moving it to an isolated section at the bottom for easier review.
  • Hiding (Hiding): The eye icon () will allow us to hide irrelevant event groups (e.g., thousands of “Boot” events) to clean up our view. Hidden events can be restored from the “Filters” panel.

Question 1:

Using the timeline, how many results were there on 2015-01-12?

Analysis:

  1. We will open the “Timeline” tool from the toolbar.
  2. We will make sure to be in the Counts view.
  3. Click on the 2015 year bar. The graph will update to show the months.
  4. Click on the January bar. The graph will update to show the days.
  5. Locate the day 12 bar. Hovering over it, or clicking on it, will show the exact number of events.

Response:

46

Question 2:

On what date did most of the file events occur? (MONTH DD, YYYY)

Analysis:

  1. With the “Timeline” view still open and in “Counts” mode, we will return to the year view by clicking “Zoom Out” if necessary.
  2. Identify the highest year bar. Click on it (which is 2015).
  3. In the month view, identify the highest month bar. Click on it (which is March).
  4. In the day view, identify the highest day bar, which represents the peak of activity across all the evidence.

Response:

March 25, 2015

We have completed our documentation manual based on the TryHackMe Autopsy room. Throughout these chapters, we have followed a professional forensic workflow and documented every stage of the analysis process.

To conclude, this is the summary of the methodology we have applied:

  1. Fundamentals and Workflow (Ch 1): We establish that Autopsy is a GUI for The Sleuth Kit and define our 5-step process. We learned how to create and open cases (.aut).
  2. Evidence Acquisition (Ch 2): We detail how we will add “Data Sources,” focusing on key formats such as Raw (.dd) and EnCase (.e01).
  3. Ingest Modules (Ch 3): We identify “Ingest Modules” as Autopsy's automated analysis engine, which is responsible for extracting artifacts.
  4. Interface Navigation (Ch 4): We will map the 5 main areas (Tree Viewer, Results Viewer, etc.) and learn how to generate reports.
  5. Practical Case (Ch 5): We will apply our knowledge to solve a real-world scenario, finding incriminating artifacts such as web history (how to wipe drive) and network files.
  6. Visualization Tools (Ch 6): We will use the “Timeline” to build a chronological narrative and identify activity peaks.

The TryHackMe room concludes by mentioning advanced topics that were not covered in detail. These are the logical next steps in our learning:

  • Global Configurations: Autopsy allows configuring settings at a global level (not just per case). This is crucial for configuring:
    • Global Hash Search (NSRL): To automatically compare all files against databases of “known good” files (e.g., Windows files) or “known bad” files (malware).
    • Global Keyword Search: To maintain lists of keywords (e.g., suspect names, contraband terms) that will be run in all cases.
    • Interesting Items: We will configure our own rules for what Autopsy considers an “Interesting File.”
  • 3rd Party Modules: The true power of Autopsy lies in its extensibility. We will download and install additional modules (generally in Python or Java) from the community (such as the SleuthKit GitHub repository) to analyze newer or more specific artifacts (e.g., drones, niche chat applications).
  • Practice with More Images: Task 9 recommends downloading the complete disk image from the NIST CFReDS Project, which is the source of the evidence used in this room. We will practice full analysis (including running ingest modules from scratch) to solidify our skills.

This final task is a conclusion that summarizes the room and encourages further exploration.

Task 9 Question:

We will complete the room!

Response:

No answer is required; we will just complete the task.

DIGITAL FORENSIC ANALYSIS REPORT