Ir al contenido

Timeline Inspection and Diagnosis with pinfo.py

Internal audit of Plaso database files, case metadata analysis, and operational summary extraction before filtering.

0views

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.


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.py will 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.

Its invocation is very straightforward; it only requires specifying the file path of the .plaso you wish to examine:

Ventana de terminal
pinfo.py <archivo.plaso>
Ventana de terminal
pinfo.py /opt/forensics/cases/case-001/my_timeline.plaso

Without adding any additional parameters, the tool provides a compact diagnostic of the processing performed:

Ventana de terminal
pinfo.py /opt/forensics/cases/case-001/my_timeline.plaso
Plaso Storage File Information
================================
Storage file: my_timeline.plaso
Format version: ...
Serialization format: ...
Processing information
======================
Status: completed
Processing time: 01:32:15
Source processed: /opt/forensics/cases/case-001/image.E01
Command: log2timeline.py -z "Europe/Madrid" ...
Events
======
Total number of events: 15234890
  • Key Check: Verify that the Status field reports completed. If it reflects state aborted or failed, the database is truncated and is not valid for the next phase.
  • Total Event Validation: If the list shows 0 events, 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:

Ventana de terminal
pinfo.py --sections errors /opt/forensics/cases/case-001/my_timeline.plaso
Errors
======
Parser: winevt
Path specification: /Windows/System32/winevt/Logs/Security.evtx
Error: Unable to parse EVTX file.
  • Failure Interpretation: The winevt log 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.

Allows listing which analyzer modules have found valid events and in what relative quantity:

Ventana de terminal
pinfo.py --sections parsers /opt/forensics/cases/case-001/my_timeline.plaso
Parsers
=======
Parser: Total number of events
-------------------------------------------------
chrome_cache: 15230
chrome_history: 5890
...
fs: 8901234
...
prefetch: 450
windows_registry: 250120
winevt: 120450
-------------------------------------------------
Total: 15234890
  • Interpretation: If your investigation objective was to determine file execution, and the prefetch parser shows 450 entries, 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:

Ventana de terminal
pinfo.py --sections "info,analysis" /opt/forensics/cases/case-001/my_timeline.plaso
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:

Ventana de terminal
pinfo.py --sections stores /opt/forensics/cases/case-001/my_timeline.plaso
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.

The most commonly used approach by investigators. It dumps all structured metadata analytical sections at once into a case report text file:

Ventana de terminal
pinfo.py -v /opt/forensics/cases/case-001/my_timeline.plaso > /opt/forensics/cases/case-001/analysis_report.txt

5. Summary of the Forensic Methodological Flow

Sección titulada «5. Resumen del Flujo Metodológico Forense»
  1. Creation Phase: You run log2timeline.py to build the my_timeline.plaso database (long-running task).
  2. 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
  3. Audit Phase: You open the analysis_report.txt file and confirm:
    • ✔ The Status status must be completed.
    • ✔ The errors section must not list vital log file losses.
    • ✔ The time zone fully matches that of the investigated system.
  4. 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.