Ir al contenido
Featured

Autopsy Fundamentals for Digital Forensics

Introductory guide to case management, data source import, and ingest module configuration in Autopsy Forensics.

Technical difficulty:
0views

Autopsy is one of the most powerful and widely used open-source platforms in digital forensic investigation. It acts as the graphical interface for the The Sleuth Kit (TSK) ecosystem and other forensic engines, allowing Blue Team investigators and incident response specialists to analyze disk images, mobile devices, and file systems in a highly intuitive and rigorous manner.


Before opening Autopsy, the integrity of the evidence must be ensured using hardware or software write-blocking devices to preserve the chain of custody. The basic workflow is:

graph TD
Ev["Adquisición de la Evidencia (.E01 / .RAW / .DD)"] -->|Creación del caso| Case["Nuevo Caso en Autopsy"]
Case -->|Definición del destino| Config["Configuración de Módulos de Ingesta"]
Config -->|Análisis de bajo nivel| Analysis["Examen y Búsqueda Forense (Timeline, Hex, Strings)"]
Analysis -->|Correlación de datos| Report["Generación del Informe Forense Certificado"]

  1. Working Directory: Defines a fast working path on a local drive (preferably an SSD) such as /opt/forensics/cases/case-001/ to store the case's SQLite database and indexed text data.
  2. Identifier Assignment: Enter the case number (e.g., CASE-2026-001) and the name of the investigator in charge (admin.forensic).
  3. Data Source Import:
    • Disk Image: Supports formats such as E01 (Expert Witness Format) and raw files (.dd, .imgersions).
    • Local Files: Allows importing directories or loose files (ideal for quick folder triage).

Ingest modules are responsible for automatically analyzing the data source in the background. Enabling only the necessary ones drastically optimizes processing times:

Calculates the MD5 and SHA-256 of all files and compares them with known databases such as the NSRL (National Software Reference Library) to flag known system files (reducing noise) or identify previously cataloged malicious file signatures.

Analyzes the internal headers (magic numbers) of files to categorize them correctly (for example, distinguishing if a file .tmp is actually an executable .exe).

Immediately alerts if a file header does not match its file extension. This is very useful for detecting files that have attempted to masquerade as images (e.g., a binary renamed to imagen.jpg).

Indexes all disk text in a Solr database to perform instant searches for strings such as suspicious IP addresses, email addresses, or case-specific keywords.

Extracts Windows OS artifacts such as:

  • ✔ Browsing history, downloads, and cookies from major browsers.
  • ✔ Recently connected USB devices (from the Windows registry).
  • ✔ Recently opened documents (LNK files and the Recent folder).

Once ingestion is complete, Autopsy offers different evidence viewers:

  • Timeline View: Allows viewing all events in a chronological interface, ideal for correlating the exact timing of a security incident.
  • Hexadecimal / Text Viewer: Allows inspecting the low-level sectors of any file and visualizing embedded text strings.
  • Metadata Viewer: Shows file system details (inodes, creation, modification, access, and change dates - MACB).

Forensic Integrity

The original data image must never be modified. All marking, tagging, and file extraction operations are executed in the Autopsy working unit, ensuring that the original physical evidence remains intact and admissible in court.