Ir al contenido

Section 1: Introduction and Case Management

Introduction to the Autopsy platform and the forensic case management workflow.

0views

Autopsy® is an open-source digital forensics platform designed for analyzing hard drives, smartphones, and other digital media. It provides an intuitive graphical interface built on The Sleuth Kit® and other digital forensics modules. Its modular architecture allows for extended functionality to address diverse investigative needs.

Key Autopsy Principles:

  • Extensible: Allows adding new functionalities through modules (plugins) developed in Java or Python.
  • Easy to Use: Offers a graphical interface that guides the user through the forensic process.
  • Collaborative (Multi-user): Allows multiple examiners to work on the same case simultaneously.
  • Fast: Incorporates parallel analysis and other optimizations to accelerate data processing.

This manual aims to serve as a comprehensive guide for the effective use of Autopsy in digital forensic investigations, following best practices and methodologies.

1.2 The Concept of a “Case” in Autopsy

Sección titulada «1.2 El Concepto de “Caso” en Autopsy»

In Autopsy, a Case is the primary container for all information related to a specific investigation. It groups:

  1. Data Sources: Forensic images (E01, dd, etc.), local disks, logical folders, etc., that contain the evidence to be analyzed. A case must have at least one data source but can contain multiple.
  2. Case Metadata: Administrative information such as case name, reference number, examiner name, and the base directory where all case files will be stored.
  3. Case Database: A database (generally SQLite or PostgreSQL for multi-user cases) where Autopsy stores all findings, file metadata, ingest module results, tags, reports, etc.
  4. Configuration Files and Logs: Audit trails, case-specific configurations, and logs generated during the analysis.

Why is it crucial to create a case?

  • Organization: Keeps all evidence and investigation results logically grouped and separate from other investigations.
  • Integrity: Ensures that analyses and results are stored in a structured manner and referenced to the original evidence.
  • Collaboration: Facilitates teamwork in multi-user cases.
  • Persistence: Saves the analysis state, allowing the case to be closed and reopened to continue the investigation later.

When starting Autopsy, a welcome screen is usually presented. To start a new investigation, we will follow these steps:

  1. Start the Wizard:

    • We click “Create New Case” on the welcome screen or select “File” > “New Case” from the main menu if we already have Autopsy open.
  2. Case Information:

    • Case Name: We introduce a descriptive and unique name for the investigation (e.g., Investigacion_Portatil_XYZ, Analisis_USB_Empleado_ABC). This name will also be used for the main case folder.
    • Base Directory: We select the location on our file system where the main case folder will be created. All files generated by Autopsy for this case (database, logs, reports, extracted files, etc.) will be stored within this folder. It is essential to choose a location with enough free space. Autopsy will display the full path where the case data will be stored below this field.
    • Case Type:
      • Single-user: We create a case stored locally using a SQLite database. It's the standard option for a single examiner working on a single machine.
      • Multi-user: Allows real-time collaboration between multiple examiners. Requires prior configuration of centralized network services (PostgreSQL for the database, Solr for indexing, ActiveMQ for communication). Note: Detailed multi-user case configuration is an advanced topic we'll cover in a later section. To get started, we'll always select 'Single-user'.
  3. Additional Information (Optional):

    • Case Number: We introduce a reference number or official identifier associated with the investigation (e.g., 2025-00123).
    • Examiner: We introduce our name or the name of the primary examiner responsible for the case.

    Important: This information will be included in the generated reports and helps maintain a formal record. We recommend completing these fields.

  4. Finish:

    • We click on “Finish”. Autopsy will create the necessary folder structure and the case database in the specified base directory.

Once the case is created, Autopsy will generally proceed automatically to request the addition of the first Data Source, which will be the next logical step in our forensic workflow and the subject of our next subsection.

After creating a case, the next step is to add digital evidence. The “Add Data Source” wizard starts automatically after creating a new case, or we can start it manually from the “Case” > “Add Data Source” menu or via the corresponding button in the toolbar.

Autopsy allows ingesting several types of data sources:

  • Disk Image or VM File: This is the most common option in forensic analysis. It allows adding complete forensic images of hard drives, USB drives, memory cards, etc.
    • Supported formats include:
      • Raw (dd): Sector-by-sector images; they may be split into multiple files (.001, .002, ...).
      • E01 (EnCase): Common forensic format that includes metadata and optional compression.
      • VMDK (VMware): VMware virtual disk files.
      • VHD (Microsoft): Microsoft virtual disk files.
      • Other formats compatible with The Sleuth Kit.
  • Local Disk: Allows direct analysis of a physical disk (e.g., /dev/sda, \\.\PhysicalDrive1) or a logical partition (e.g., C:, /dev/sda1) connected to the analysis machine.
    • Forensic Caution! Analyzing a local disk directly may alter it if a physical or software write blocker is not used. This option is useful in controlled scenarios or for quick analysis, but ingesting a forensic image is generally the recommended practice to maintain the integrity of the original evidence.
  • Logical Files: Allows adding a specific folder or a set of individual files to the case. Useful for targeted analysis of specific directories (e.g., user profile, log exports, specific memory dumps) without the need to process a complete image.
  • Unallocated Space Image File: Allows adding an image that contains only the unallocated space previously extracted from another source. It is used for specific carving or deleted data recovery tasks.

We will follow the wizard to add a “Disk Image or VM File”:

  1. Select Type of Data Source To Add: We will ensure that “Disk Image or VM File” is selected and click “Next”.
  2. Select Data Source:
    • Path: We click on “Browse” and navigate to the location of our forensic image file. We select the primary file (e.g., imagen.dd, imagen.E01, imagen.vmdk). If the image is split (.001, .002), we select the first file in the sequence. Autopsy will automatically detect the other segments if they are in the same folder and follow the standard nomenclature.
    • Time zone setting for analysis: This step is crucial! We select the original time zone of the system the image came from. This will ensure that file timestamps are interpreted and correlated correctly during analysis and timeline creation. If we are unsure, we consult the case documentation or keep it in the local time zone, while remaining aware of potential discrepancies.
    • (Optional) Ignore orphan files in FAT file systems: For FAT file systems (common in older USB drives), checking this option may speed up the initial ingestion, but it could skip fragments of deleted files that do not have a direct reference in the allocation table. For a comprehensive analysis, it is recommended not to check this option.
    • We click “Next”.

Autopsy will begin processing the basic structure of the image (partitions, file systems). Once this preliminary step is completed, the wizard will proceed to the configuration of the Ingest Modules, where we will define which automated analyses we want to perform on the added data source.

Adding other data sources (Local Disk, Logical Files) will follow a similar process, requesting the path to the corresponding disk/partition or folder/files. Once all options are configured, we click “Finish” to complete the ingestion process.