Digital Forensics
Exterro INFORM

Collection of Essential Files for DFIR Investigations

Learn how to implement a strategy of high-speed, defensible data collection as part of your digital forensics and incident response workflows with Matt Petersen of Rockwell Automation in this session from Exterro INFORM 2026.

Collection of Essential Files for DFIR Investigations

This session is critical for DFIR and Legal Tech professionals who must balance the technical need for evidence with the executive demand for speed. Matt Petersen frames forensic collection not just as a technical task, but as a leadership capability—demonstrating how to maintain defensibility while operating under the intense pressure of active litigation or a breach. He shifts the conversation from the "how" of full-disk imaging to the "why" of targeted, high-velocity data acquisition.

Executive demands drive quick, targeted data collection.
"The CSO or somebody else in the corporation... they want the information fast and they want you to get that information back to them. That’s why maybe the first initial talk is, 'Hey, you know what, let's grab these system files. Let's get those quick.'"

"Law enforcement has a different burden of proof versus a corporation... however, that doesn't stop it from being litigated. You’ve got to remember the old stuff because it may come into play."
Matt Petersen
Supervisor of Cybersecurity and Forensics, Rockwell Automation
Actionable Takeaways for Digital Forensics Professionals
Takeaway #1
Velocity over Volume: The Targeted Collection Strategy

Traditional full-disk imaging is time-prohibitive in an era of multi-terabyte drives and encrypted cloud environments, leading to unacceptable delays in incident triage.

Prioritize Registry and Log Artifacts
Immediately target the SAM, System, Security, and Software hives to reconstruct system state without the overhead of a full image.
Engage Litigation Early
As soon as data is identified leaving the corporate e-mail or cloud server, pivot from a technical investigation to a legal hold to preserve external evidence.
Analyze Browser Forensic Artifacts
Focus on SQL Lite files within Chromium-based and Firefox browsers to identify unauthorized cloud uploads or web-based chat history.
Takeaway #2
Bridging the Silo: CSIRT and DFIR Integration

Incident Response (CSIRT) and Forensic (DFIR) teams often operate in silos, resulting in "forensic suicide" where containment actions, like wiping a machine, accidentally destroy the evidence needed for legal defensibility.

Synchronize Containment Tools
Ensure your forensic agents can function through the "quarantine" state imposed by EDR tools like CrowdStrike to allow for remote collection during a lockdown.
Establish a Communication Lead
Assign a dedicated manager to coordinate the flow of network logs from the SIEM engineer to the forensic analyst for real-time correlation.
Document the "Delta"
Maintain rigorous notes on any changes made to the system during the investigation to satisfy the high burden of proof required in corporate espionage or criminal cases.
Takeaway #3
Mitigating the Shadow Data Exit: Cloud and Personal Artifacts

Proprietary data frequently migrates to personal cloud drives (OneDrive, Google Drive) or encrypted chat apps, leaving the organization blind to the true scope of data exfiltration.

Track Cloud IDs
Use File IDs to trace proprietary documents across different users; these IDs often remain constant even when files are shared to external, personal accounts.
Automate Artifact Extraction
Develop or deploy scripts specifically to pull Prefetch files and NTUSER.DAT to quickly identify program execution and user activity.
Audit the Windows Timeline
Utilize the ActivitiesCache database to recover historical snapshots of user actions that are often overlooked in standard collections.