Study guide
15.3 Specialized DFIR Utilities: Eric Zimmerman Tools (EZ Tools) & Sysinternals Forensic Suite
Computer Hacking Forensic Investigator CHFI 312-49
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Foundations of Digital Forensics & Cybercrime Investigation
1.1 Cybercrime Classifications, Forensic Science Principles & Legal Admissibility 1.2 RFC 3227 Order of Volatility, Live vs. Dead Acquisition & Forensic Readiness 1.3 Indicators of Compromise (IoCs), Cyber Attribution & Threat Intelligence 1.4 AI-Assisted Forensics, GitOps, Automation/Orchestration & Forensics-as-a-Service (FaaS)
2 Chapter 2: Modern Forensic Environments & Emerging Threats
2.1 Fileless Malware, In-Memory Execution & Living-off-the-Land (LotL) 2.2 IoT & Operational Technology (OT/SCADA) Forensic Fundamentals 2.3 Dark Web, Tor Network, Onion Routing & Hidden Services Forensics 2.4 Blockchain Transactions, Cryptocurrency Tracing & Digital Asset Investigations
3 Chapter 3: Legal Frameworks, Search Warrants & Evidence Rules
3.1 Federal Rules of Evidence (FRE 702, 901, 902, 1001-1003) & Daubert/Frye Standards 3.2 Fourth Amendment, Warrant Exceptions, Workplace Search & Consent Protocols 3.3 International Standards: ISO/IEC 27037, ACPO Principles & ENFSI Guidelines 3.4 Cybercrime Statutes, Privacy Compliance, CAN-SPAM & International Cooperation
4 Chapter 4: eDiscovery, Chain of Custody & Professional Ethics
4.1 Electronic Discovery Reference Model (EDRM) & Legal Spoliation Holds 4.2 Chain of Custody Documentation, Evidence Packaging & Tamper-Evident Handling 4.3 Expert Witness Testimony, Report Writing Standards & EC-Council Code of Ethics
5 Chapter 5: Storage Architecture, Boot Sequences & Media Forensics
5.1 Storage Media Architecture: Sectors, Clusters, RAM/File Slack & Unallocated Space 5.2 Partition Tables & Boot Structures: MBR, GPT, VBR, BIOS vs. UEFI Secure Boot 5.3 RAID Reconstruction (RAID 0, 1, 5, 6, 10) & SSD Forensic Challenges (TRIM, Wear Leveling)
6 Chapter 6: Windows File Systems: NTFS & FAT
6.1 NTFS Architecture: Master File Table ($MFT) Record Structure & Attribute Headers 6.2 NTFS Artifacts: Alternate Data Streams (ADS), Volume Shadow Copies (VSS) & $LogFile 6.3 FAT12/16/32 and exFAT Architecture, Directory Entries & File Deletion Mechanics
7 Chapter 7: Non-Windows File Systems & File Signatures
7.1 Linux File Systems: ext2/ext3/ext4 Inode Architecture, Superblocks & Journaling Forensics 7.2 macOS File Systems: HFS+ and Apple File System (APFS) Architecture & Snapshots 7.3 File Signatures, Magic Bytes, Hex Headers/Footers & File Carving Techniques
8 Chapter 8: Investigation Lifecycle, Lab Setup & First Response
8.1 Forensic Laboratory Accreditation: ISO/IEC 17025 Standards & Hardware/Software Controls 8.2 First Responder Duties: Crime Scene Containment, Electronic Triage & Volatile Triage 8.3 Physical Evidence Packaging, Anti-Static/Faraday Protection & Transport Security
9 Chapter 9: Forensic Acquisition & Verification Methodology
9.1 Hardware and Software Write-Blockers: Operational Validation & Bridge Verification 9.2 Bit-Stream Disk Imaging, Physical vs. Logical vs. Targeted Acquisition Methodology 9.3 Forensic Image Formats (RAW/DD, E01, AFF) & Cryptographic Hashing Verification (MD5, SHA-256)
10 Chapter 10: Anti-Forensics Techniques & Countermeasures
10.1 Steganography Detection: Spatial/Frequency Domain Steganalysis & Hidden Carrier Extraction 10.2 Timestomping Countermeasures: Comparing $STANDARD_INFORMATION vs $FILE_NAME Timestamps 10.3 Secure Wiping, Degaussing, File Shredding Countermeasures & Residual Artifact Recovery
11 Chapter 11: Windows Operating System Forensics
11.1 Windows Registry Forensics: SYSTEM, SOFTWARE, SAM & NTUSER.DAT Hive Analysis 11.2 Execution Artifacts: Prefetch (.pf), Shimcache (AppCompatCache), Amcache.hve & UserAssist 11.3 User Activity Artifacts: ShellBags, LNK Shortcut Files, Jump Lists & Recycle Bin ($I/$R) 11.4 Windows Event Log Forensics: Security Audit IDs (4624, 4625, 4688, 4720, 7045) & EVTX Parsing
12 Chapter 12: Memory Forensics & Malware Analysis
12.1 Volatile Memory Acquisition: RAM Capture, Crash Dumps, Hiberfil.sys & Pagefile.sys 12.2 Memory Analysis with Volatility 3: pslist, pstree, malfind, netscan & Vadinfo 12.3 Static Malware Triage: Strings, PE Headers, Import Tables, Hashes & YARA Rule Matching 12.4 Dynamic Malware Analysis: Sandboxing, Process Monitor (Procmon), Regshot & Network Callouts 12.5 .NET Managed Malware Analysis & the GOOTLOADER Fileless Infection Chain
13 Chapter 13: Network, Web Application & Email Forensics
13.1 Network Forensics: PCAP Analysis, Protocol Dissection, Snort/Suricata & Flow Analysis 13.2 Web Server Forensics: Apache/IIS Access Logs, SQL Injection, XSS & Web Shell Detection 13.3 Email Forensics: RFC 5322 Headers, Authentication (SPF, DKIM, DMARC) & Mbox/PST Extraction 13.4 SIEM Event Correlation, Cross-Source Timeline Analysis & Super-Timeline Construction 13.5 Investigating Directory Traversal, Command Injection, Parameter Tampering, XXE, Cookie Poisoning & Brute Force 13.6 Network Device & Service Log Forensics: Firewall, IDS, Honeypot, Router, DHCP, Switch, VPN, DNS & SSH 13.7 Wireless Network Forensics: Rogue APs, Evil Twins, MAC Spoofing, Deauthentication & Jamming
14 Chapter 14: Mobile, Cloud & IoT Forensics
14.1 Mobile Device Forensics: Manual, Logical, File System & Physical Extraction (Android/iOS) 14.2 Mobile Artifact Analysis: Call Logs, SMS/Chat SQLite Databases, Location Data & Plists 14.3 Cloud Forensics: AWS CloudTrail, Azure Activity Logs & Multi-Tenant Evidence Collection 14.4 IoT Forensics: UART/JTAG Physical Interfaces, Firmware Extraction & Sensor Telemetry
15 Chapter 15: Commercial & Open-Source Forensic Suites
15.1 Commercial Forensic Platforms: EnCase Forensic, FTK (Forensic Toolkit) & FTK Imager 15.2 Open-Source Forensic Platforms: Autopsy, The Sleuth Kit (TSK) & SIFT/CAINE Workstations 15.3 Specialized DFIR Utilities: Eric Zimmerman Tools (EZ Tools) & Sysinternals Forensic Suite
16 Chapter 16: Analysis Toolkits, Python Scripting & Tool Validation
16.1 Reverse Engineering & Password Cracking: Ghidra, IDA Pro, Hashcat & John the Ripper 16.2 Python for Digital Forensics: Parsing Raw Artifacts, Custom Scapy Scripts & Evidence Automation 16.3 Forensic Tool Testing & Validation: NIST CFTT Methodology, ISO/IEC 17025 Standards & Daubert Compliance
17 Chapter 17: Database Forensics & Web Application Firewalls
17.1 MySQL Forensics: Internal Architecture, Data Directory, Information Schema & Utility Programs 17.2 SQL Server Forensics: SSMS, ApexSQL, SQLCMD Transaction-Log Collection, Plan Cache & Trace Files 17.3 Web Application Firewall (WAF) Architecture, Audit Logs, Benefits & Limitations
18 Chapter 18: Social, Virtualized, Multimedia & Browser Investigations
18.1 Social Media, Social Engineering, Insider Threat & Identity Theft Forensics 18.2 Virtualization, Container & Microservices Forensics, Bluetooth and Electron Chat Applications 18.3 Multimedia Forensics: Image, Audio & Video Authentication, EXIF, PRNU and Deepfake Detection 18.4 Browser Artifact Recovery, Private Browsing, USB Enumeration, Partition Recovery & Packer Unpacking Tools
15.3 Specialized DFIR Utilities: Eric Zimmerman Tools (EZ Tools) & Sysinternals Forensic Suite
Key Takeaways Explain This Topic AI
Eric Zimmerman's DFIR Tools (EZ Tools) provide open-source, high-performance .NET CLI and GUI parsers specifically engineered to extract forensic metadata from proprietary Windows structures.
MFTECmd parses NTFS metadata structures including $MFT, $LogFile, $J (USN Journal), and $Boot, correlating standard information and file name attributes while resolving resident and non-resident data streams.
KAPE (Kroll Artifact Parser and Extractor) orchestrates targeted forensic triage by coupling Targets (.tkape file collection definitions) with Modules (.mkape CLI tool execution rules) to collect and parse vital artifacts in minutes.
Microsoft Sysinternals Autoruns (autorunsc.exe) provides comprehensive Autostart Extensibility Point (ASEP) audits with digital signature verification and VirusTotal API hash correlation.
Process Monitor (Procmon) captures granular file system, registry, and network activity with backing-file support, while Process Explorer (Procexp) exposes parent-child process anomalies and DLL/handle telemetry.
Last updated: September 2026
15.3 Specialized DFIR Utilities: Eric Zimmerman Tools & Sysinternals Suite
Quick Answer: Modern digital forensics and incident response (DFIR) relies heavily on agile, specialized command-line utilities for rapid artifact parsing and live system analysis. Eric Zimmerman's Tools (EZ Tools) are high-performance, open-source .NET utilities designed to parse proprietary Windows forensic artifacts, including registry transaction logs ( Registry Explorer / RECmd ), NTFS metadata ( MFTECmd for $MFT , $LogFile , and $J ), folder navigation ( ShellBags Explorer / SBECmd ), and execution artifacts ( PECmd , AppCompatCacheParser , AmcacheParser , LECmd , JLECmd , and EvtxECmd ). These tools are orchestrated by KAPE (Kroll Artifact Parser and Extractor) , which automates triage by pairing Targets ( .tkape ) for file collection with Modules ( .mkape ) for tool execution. For live endpoint triage, the Microsoft Sysinternals Suite —including Autoruns ( autorunsc.exe ) , Process Monitor ( Procmon ) , Process Explorer ( Procexp ) , and PsTools —provides deep visibility into autostart persistence, process parentage, active network sockets, and kernel activity.
Eric Zimmerman's DFIR Tools (EZ Tools)
Authored by former FBI Special Agent Eric Zimmerman, EZ Tools represent the gold standard for Windows artifact analysis. Developed in C#/.NET, these utilities provide both rich graphical interfaces and command-line variants optimized for automated incident response pipelines.
1. Registry Forensics: Registry Explorer & RECmd
Registry Explorer (GUI): Offline hive viewer supporting transaction log replay ( .LOG1 / .LOG2 ). When a system crashes or is abruptly imaged, registry hives remain in a "dirty" state. Registry Explorer reconciles uncommitted transactions, recovers deleted registry keys, and provides built-in bookmarks for critical forensic paths.
RECmd (Registry Explorer Command Line): Designed for headless automation. Supports batch files ( .reb ) to query hundreds of forensic registry locations across multiple hives simultaneously, exporting structured CSV/JSON results. :: Running RECmd in batch mode against seized registry hives
RECmd.exe -d "C:\Cases\Evidence\RegistryHives" --bn "BatchExamples\Kroll_Batch.reb" --csv "C:\Cases\Output\Registry"
2. File System Parsers: MFTECmd & ShellBags Explorer
MFTECmd (MFT, LogFile, USN Journal, and Boot Parser):
Parses NTFS Master File Table ( $MFT ) records, extracting record numbers, sequence numbers, parent directory references, file sizes, and flags (directory vs. file; allocated vs. unallocated).
Timestomp Detection: Compares timestamps in $STANDARD_INFORMATION (modifiable by user-mode APIs) against $FILE_NAME (modified only by the Windows kernel), immediately highlighting timestomping anomalies.
Analyzes the USN Change Journal ( $J ) , documenting file creation, renaming, deletion, and extension modification events alongside reason codes ( USN_REASON_FILE_CREATE , USN_REASON_FILE_DELETE ).
Analyzes $LogFile (NTFS transaction journal) and $Boot (Volume Boot Record parameters). :: Parsing $MFT and $J to CSV format using MFTECmd
- MFTECmd.exe -f "C:\Evidence\$MFT" --csv "C:\Output\MFT" --csvf mft_parsed.csv
- MFTECmd.exe -f "C:\Evidence\$Extend\$UsnJrnl:$J" --csv "C:\Output\USN" --csvf usn_parsed.csv
ShellBags Explorer & SBECmd:
Parses BagMRU and Bags keys from NTUSER.DAT and UsrClass.dat .
Forensic Utility: Proves user folder browsing activity. Reconstructs folder navigation histories, identifying when a suspect opened local folders, mounted network shares, browsed removable media, or explored ZIP archives—even if those directories have been permanently deleted.
3. Execution and User Activity Parsers
Tool Name Target Artifact & Location Forensic Intelligence Extracted
PECmd Windows Prefetch ( C:\Windows\Prefetch\*.pf ) Executable name, run count, last 8 execution timestamps (Win 10/11), referenced volume serial numbers, and loaded DLLs/files.
AppCompatCacheParser SYSTEM hive ( ControlSet001\Control\Session Manager\AppCompatCache ) Application file path, file size, last modified date, and execution flag (Shimcache).
AmcacheParser Amcache hive ( C:\Windows\appcompat\Programs\Amcache.hve ) Binary SHA-1 hashes , full file paths, PE header compilation timestamps, installation timestamps, and associated application metadata.
LECmd Windows Shortcut LNK files ( *.lnk ) Target file path, target MACB timestamps, volume serial number, volume label, target file size, and MAC address of creator machine.
JLECmd Jump Lists ( AutomaticDestinations & CustomDestinations ) Application Identifiers (AppIDs), recently and frequently accessed documents per application, interaction counts.
RBCmd Windows Recycle Bin ( $I... and $R... files) Pairs $I metadata files (original file path, original size, deletion timestamp) with $R data payloads to prove deliberate file deletion.
EvtxECmd Windows Event Logs ( C:\Windows\System32\winevt\Logs\*.evtx ) Parses binary XML logs using message map files to resolve localized string templates without requiring host DLLs; outputs normalized CSV/JSON.
KAPE (Kroll Artifact Parser and Extractor)
Developed by Eric Zimmerman while at Kroll, KAPE revolutionized digital forensics incident response by automating targeted forensic triage.
The Triage-First Philosophy
Traditional bit-stream disk imaging of modern multi-terabyte drives can take 4 to 8 hours per endpoint. However, in 95% of cyber incident response cases, critical evidentiary artifacts reside within a tiny fraction of the disk (less than 5 GB). KAPE enables investigators to acquire and process this critical evidence in 3 to 5 minutes . [Live Host / Mounted Evidence Image]
- │
- ▼
- ┌───────────────────────────┐
- │ KAPE Targets │ ──> Reads Target Files (.tkape)
- │ (Evidence Collector) │ ──> Extracts MFT, Registry, Event Logs,
- └───────────────────────────┘ Prefetch, LNK, Browsers via VSS
- │
- ▼ (Raw Targeted Artifacts)
- ┌───────────────────────────┐
- │ KAPE Modules │ ──> Reads Module Files (.mkape)
- │ (Automated Parsers) │ ──> Executes MFTECmd, PECmd, EvtxECmd,
- └───────────────────────────┘ RECmd, Eric Zimmerman CLI Suite
- │
- ▼
- ┌───────────────────────────┐
- │ Parsed Structured Output │ ──> Structured CSV, JSON, Timeline
- │ (CSV / JSON / Storage) │ ──> Optional SFTP / AWS S3 Exfiltration
- └───────────────────────────┘
- Targets (.tkape) vs. Modules (.mkape)
Targets ( .tkape ): Plain-text YAML configuration files that specify what files and directories to collect . Targets define file paths, recursive directory masks, and file extensions. Compound targets (e.g., KapeTriage.tkape ) group multiple sub-targets including Registry hives, Event Logs, LNK files, Prefetch, Jump Lists, and browser histories.
Modules ( .mkape ): Plain-text YAML configuration files that specify what command-line tools to execute against the collected files . Modules define the executable path, command-line arguments, output format, and output directory. Examples include MFTECmd.mkape , PECmd.mkape , and EvtxECmd.mkape .
Advanced KAPE Features
Volume Shadow Copy Service ( --vss ): When executed against a live Windows endpoint with administrator privileges, KAPE automatically mounts and enumerates all historical Volume Shadow Copies, extracting historical versions of registry hives and event logs from past snapshots.
Direct Cloud Exfiltration: KAPE can automatically package parsed triage output into a password-protected zip file and transfer it to an SFTP server, AWS S3 bucket, or Azure Blob container for remote incident response. :: High-speed live triage acquisition and processing using KAPE
- kape.exe --tsource C: --tdest D:\Triage\Targets --target KapeTriage \
- -msource D:\Triage\Targets --mdest D:\Triage\Parsed --module ZimmermanTools \
- -vss --gui
- Microsoft Sysinternals Suite in DFIR
Originally created by Mark Russinovich and Bryce Cogswell (Winternals, later acquired by Microsoft), the Windows Sysinternals Suite is a collection of advanced system utilities used extensively by forensic examiners and incident responders for live system analysis.
1. Autoruns & autorunsc.exe (Persistence Auditing)
Threat actors maintain persistence on Windows hosts using Autostart Extensibility Points (ASEPs) . Autoruns is the most comprehensive ASEP inspector available for Windows.
Scope of Coverage: Inspects standard Run/RunOnce registry keys, Startup folders, Scheduled Tasks, Windows Services, Drivers, Winlogon extensions, AppInit_DLLs, Image File Execution Options (IFEO debugger hijacks), WMI Event Consumers, Print Monitors, and Explorer Shell Extensions.
Forensic Verification Flags:
-v : Verifies digital signatures against trusted root certificates.
-vt : Computes cryptographic file hashes and submits them automatically to the VirusTotal API , displaying detection ratios.
-c : Outputs results as comma-separated values (CSV) for scripting.
-a * : Evaluates all ASEP categories. :: Automated baseline audit of all autostart mechanisms with VirusTotal checks
- autorunsc.exe -a * -c -h -v -vt > C:\Forensics\autoruns_audit.csv
- 2. Process Monitor (Procmon)
Process Monitor is an advanced monitoring tool for Windows that captures real-time file system, registry, process, thread, and network activity.
Core Operations Captured: RegSetValue , RegDeleteKey , CreateFile , WriteFile , ProcessCreate , and TCP Connect .
Forensic Capture Strategies: In intensive environments, capturing all events can rapidly consume gigabytes of RAM. Examiners configure Drop Filtered Events to discard benign operations in memory and use Backing Files ( /BackingFile <path.pml> ) to write capture logs directly to secondary storage. :: Starting headless Process Monitor capture with backing file
procmon64.exe /BackingFile D:\IncidentCapture.pml /Quiet /AcceptEula
- :: Terminating active capture and converting PML to CSV
- procmon64.exe /Terminate
- procmon64.exe /OpenLog D:\IncidentCapture.pml /SaveAs D:\IncidentCapture.csv
- 3. Process Explorer (Procexp)
Process Explorer functions as an advanced task manager, displaying a real-time hierarchical tree of active processes.
Parent-Child Process Trees: Instantly exposes anomalous process hierarchies (e.g., cmd.exe or powershell.exe spawned as a child of Microsoft Word ( winword.exe ) or IIS Worker Process ( w3wp.exe )).
Handle and DLL Inspection: Displays all active file handles, named pipes, mutexes, and loaded dynamic link libraries (DLLs) mapped into a process's virtual address space.
Process Hollowing & Injection Detection: Compares strings resident within the executable on disk against strings present in physical RAM. Discrepancies strongly indicate process hollowing or in-memory code injection.
VirusTotal Integration: Enables instant hashing and VirusTotal reputation scoring of all running processes.
4. TCPView
TCPView monitors active network sockets on the endpoint, displaying detailed listings of all TCP and UDP endpoints, local addresses, remote addresses, port numbers, connection state ( LISTENING , ESTABLISHED , TIME_WAIT ), and the owning process name and PID. It highlights active state transitions using color coding (green for new connections, red for terminated sockets, yellow for state changes).
5. PsTools Suite
PsExec: Remote execution utility allowing administrators—and incident responders—to spawn command shells or execute triage scripts on remote systems without installing a full agent.
Forensic Footprint: Creates PSEXESVC.exe in %SystemRoot% , generates Windows System Event Log ID 7045 ( A service was installed in the system ), and creates named pipes ( \pipe\psexec* ).
PsList: Displays detailed process lists, thread counts, memory usage, and execution times locally or remotely.
PsLoggedOn: Queries the local registry and network resource shares to identify active interactive users and remote session connections.
6. Strings (strings.exe)
Extracts printable characters from binary files, memory dumps, or unallocated space: :: Extracting ASCII and Unicode strings with minimum length of 8 characters
- strings.exe -a -u -n 8 suspect_memory.dmp > memory_strings.txt
- 7. SDelete (sdelete.exe)
Developed as a secure file deletion and free-space sanitization utility compliant with DoD 5220.22-M standards. In forensic investigations, threat actors frequently employ sdelete.exe as an anti-forensics tool.
Forensic Detection: When sdelete.exe deletes a file, it renames the file entry in the Master File Table to a sequence of repeating characters (such as AAA...AAA ) prior to zeroing out cluster runs and unlinking the MFT record. Identifying these repeating character patterns in MFT records or USN Journal entries provides definitive proof of deliberate evidence destruction.