Timeline Inspection and Diagnosis with pinfo.py
Internal audit of Plaso database files, case metadata analysis, and operational summary extraction before filtering.
Your Plaso File Control Dashboard
Sección titulada «El Tablero de Control de tu Archivo Plaso»1. What is pinfo.py?
Sección titulada «1. ¿Qué es pinfo.py?»pinfo.py (Plaso Info) is a diagnostic and structural review tool. Its sole mission is to read a previously extracted .plaso database file and display a summary of the metadata it contains on the screen.
This is the absolute and mandatory first step that every forensic analyst must execute immediately after having generated a timeline using log2timeline.py. Before beginning to apply complex filtering rules or massive exports that consume high CPU with psort.py, you must rigorously verify the status and quality of the data capture performed.
2. Why is it fundamental to use it?
Sección titulada «2. ¿Por qué es fundamental utilizarlo?»pinfo.py saves dozens of hours of failed processing or analysis on missing data. It allows you to instantly audit the following research health parameters:
- ✔ Processing Errors: Explicitly list if any parser has thrown catastrophic failures (e.g., due to corrupt files or illegible signatures).
- ✔ Active Parser Summary: Confirm which analyzers have successfully collected data. If you are looking for Chrome history,
pinfo.pywill immediately tell you if the parser has collected any events or returned zero. - ✔ Target Environment Metadata: Validate the interpreted operating system version, the injected time zone, and general time ranges.
- ✔ Snapshot Verification (VSS): Confirm exactly how many hidden volume copies have been correctly analyzed.
- ✔ Total Event Volume: Evaluate the number of events forming the database to estimate response times for future queries.
3. Operational Syntax
Sección titulada «3. Sintaxis de Funcionamiento»Its invocation is very straightforward; it only requires specifying the file path of the .plaso you wish to examine:
pinfo.py <archivo.plaso>Basic diagnostic example:
Sección titulada «Ejemplo básico de diagnóstico:»pinfo.py /opt/forensics/cases/case-001/my_timeline.plaso4. Use Cases and Diagnostic Sections
Sección titulada «4. Casos de Uso y Secciones de Diagnóstico»Case Study A: Case Status Overview (Default Summary)
Sección titulada «Casuística A: Visión General del Estado del Caso (Resumen por Defecto)»Without adding any additional parameters, the tool provides a compact diagnostic of the processing performed:
pinfo.py /opt/forensics/cases/case-001/my_timeline.plasoExample Report Trace in the Console:
Sección titulada «Traza del Reporte de Ejemplo en la Consola:»Plaso Storage File Information================================Storage file: my_timeline.plasoFormat version: ...Serialization format: ...
Processing information======================Status: completedProcessing time: 01:32:15Source processed: /opt/forensics/cases/case-001/image.E01Command: log2timeline.py -z "Europe/Madrid" ...
Events======Total number of events: 15234890- Key Check: Verify that the
Statusfield reportscompleted. If it reflects stateabortedorfailed, the database is truncated and is not valid for the next phase. - Total Event Validation: If the list shows
0events, the ingestion was performed incorrectly (e.g., due to permission issues on the forensic image or incorrectly referenced paths).
Case Study B: Auditing Internal Forensic Errors (--sections errors)
Sección titulada «Casuística B: Auditar Errores Forenses Internos (--sections errors)»This is the most important quality audit step for the Blue Team. log2timeline.py does not stop its execution if it encounters corrupt or broken log files; it simply records the failure in the file metadata for subsequent inspection:
pinfo.py --sections errors /opt/forensics/cases/case-001/my_timeline.plasoExample Error Report Trace:
Sección titulada «Traza del Informe de Errores de Ejemplo:»Errors======Parser: winevtPath specification: /Windows/System32/winevt/Logs/Security.evtxError: Unable to parse EVTX file.- Failure Interpretation: The
winevtlog parser has failed to process the main Security log file (Security.evtx). Because of this, the investigator knows that login events are missing. An attempt should be made to extract the artifact from the image in isolation and use Security file recovery tools to repair it.
Case Study C: Parser Load Detail (--sections parsers)
Sección titulada «Casuística C: Detalle de Carga de los Parsers (--sections parsers)»Allows listing which analyzer modules have found valid events and in what relative quantity:
pinfo.py --sections parsers /opt/forensics/cases/case-001/my_timeline.plasoExample Event Summary Trace:
Sección titulada «Traza de Resumen de Eventos de Ejemplo:»Parsers=======Parser: Total number of events-------------------------------------------------chrome_cache: 15230chrome_history: 5890...fs: 8901234...prefetch: 450windows_registry: 250120winevt: 120450-------------------------------------------------Total: 15234890- Interpretation: If your investigation objective was to determine file execution, and the
prefetchparser shows450entries, you confirm that you will have abundant evidence in file.plaso.
Case Study D: Operating System and Time Zone Identification (--sections info,analysis)
Sección titulada «Casuística D: Identificación del Sistema Operativo y Zona Horaria (--sections info,analysis)»Ensures that Plaso has correctly identified the operating system signature and the time zone used in the investigation:
pinfo.py --sections "info,analysis" /opt/forensics/cases/case-001/my_timeline.plasoExample Analysis Summary Trace:
Sección titulada «Traza del Resumen de Análisis de Ejemplo:»Analysis Reports================Report: Operating System---------------------------------------Version: Windows 10 Pro
Report: Timezone--------------------------------System Timezone: Europe/Madrid- Interpretation: If the analyzed system's time zone does not correspond to the time detected by the database, any subsequent temporal correlation plotted on the timeline will be incorrect.
Case Study E: Summary of Processed Hidden Copies (--sections stores)
Sección titulada «Casuística E: Resumen de Copias Ocultas Procesadas (--sections stores)»Verifies that the --vss-stores directive has completed the snapshot analysis:
pinfo.py --sections stores /opt/forensics/cases/case-001/my_timeline.plasoExample Snapshot Summary Trace:
Sección titulada «Traza del Resumen de Instantáneas de Ejemplo:»Storage Files=============Index Path specification----------------------------0 /opt/forensics/cases/case-001/image.E01 (Partition 2)1 VSS Store 1 (Created: 2026-03-10 ...)2 VSS Store 2 (Created: 2026-03-15 ...)- Interpretation: Confirms that Plaso has successfully processed the primary active partition (index 0) and two past snapshots.
Case Study F: Full Audit Dump (Verbose Mode)
Sección titulada «Casuística F: Volcado Completo de Auditoría (Modo Verbose)»The most commonly used approach by investigators. It dumps all structured metadata analytical sections at once into a case report text file:
pinfo.py -v /opt/forensics/cases/case-001/my_timeline.plaso > /opt/forensics/cases/case-001/analysis_report.txt5. Summary of the Forensic Methodological Flow
Sección titulada «5. Resumen del Flujo Metodológico Forense»- Creation Phase: You run
log2timeline.pyto build themy_timeline.plasodatabase (long-running task). - Immediate Diagnosis Phase: You generate the global verbose report:
Ventana de terminal pinfo.py -v /opt/forensics/cases/case-001/my_timeline.plaso > /opt/forensics/cases/case-001/analysis_report.txt - Audit Phase: You open the
analysis_report.txtfile and confirm:- ✔ The
Statusstatus must becompleted. - ✔ The
errorssection must not list vital log file losses. - ✔ The time zone fully matches that of the investigated system.
- ✔ The
- Processing Phase: If the audit is satisfactory, you immediately proceed to process the data with
psort.py. Otherwise, the ingestion parameters are corrected and step 1 is repeated.

