Eric Zimmerman Tools for Windows Artifact Analysis

VerifiedSafe

Learn to analyze Windows artifacts using Eric Zimmerman's open-source tools (KAPE, MFTECmd, PECmd) to examine registry hives, prefetch files, and event logs.

Sby Skills Guide Bot
SecurityAdvanced
8/6/2026
Claude CodeCursorCodex
#windows-forensics#dfir#artifact-analysis#kape#registry-forensics

Recommended for

Automated summary

This skill guides forensic analysis of Windows artifacts using Eric Zimmerman's open-source EZ Tools suite (KAPE, MFTECmd, PECmd, LECmd, JLECmd, Timeline Explorer) to parse registry hives, prefetch files, event logs, and file system metadata.

Strengths

  • Covers automated collection and processing orchestration through KAPE targets and modules
  • Provides concrete PowerShell command examples for MFTECmd and the other suite parsers
  • Builds on tools widely regarded as the de facto standard for Windows forensics
  • Produces CSV output that feeds directly into Timeline Explorer for visual analysis

Limitations

  • Assumes NTFS and Windows internals familiarity plus a Windows analysis workstation with .NET 6
  • Limited to Windows artifacts; does not address Linux or macOS evidence
  • Live-system triage collection requires administrative privileges on the target
When to use it

Use it during a DFIR investigation or incident response on a Windows machine where execution artifacts and file system activity must be examined.

When not to use it

Avoid it for non-Windows hosts or when no prepared analysis environment with the EZ Tools binaries and required .NET runtime is available.

Security analysis

Safe
Quality score92/100

The skill provides instructions for using standard, well-known forensic analysis tools (Eric Zimmerman's EZ Tools suite) for legitimate digital forensics and incident response. All commands are non-destructive, operate on evidence files or mounted images, and do not involve any exfiltration, obfuscation, or disabling of security controls. Administrative privileges are required only for live system triage, which is typical for forensic acquisition. No risky patterns such as curl|sh, rm -rf, or base64-decoded payloads are present.

No concerns found

How this analysis is made

Examples

Full KAPE triage on a mounted image
Run KAPE against the mounted forensic image on drive E:, collect the KapeTriage targets into C:\Cases\Case001\Collection and process them with the !EZParser module into C:\Cases\Case001\Processed, then show me the resulting CSVs.
Parse $MFT and USN Journal
Use MFTECmd to parse the $MFT file from my evidence folder into MFT_output.csv and the $J USN Journal into USNJournal_output.csv, both in C:\Cases\Output.
Build an activity timeline
Load the prefetch, LNK, and jump list CSVs produced by PECmd, LECmd, and JLECmd into Timeline Explorer and identify what executables were run during the incident window.

name: performing-windows-artifact-analysis-with-eric-zimmerman-tools description: Perform comprehensive Windows forensic artifact analysis using Eric Zimmerman's open-source EZ Tools suite including KAPE, MFTECmd, PECmd, LECmd, JLECmd, and Timeline Explorer for parsing registry hives, prefetch files, event logs, and file system metadata. domain: cybersecurity subdomain: digital-forensics tags:

  • eric-zimmerman
  • ez-tools
  • kape
  • mftecmd
  • pecmd
  • lecmd
  • jlecmd
  • registry-forensics
  • windows-forensics
  • timeline-explorer
  • dfir
  • artifact-analysis version: '1.0' author: mahipal license: Apache-2.0 nist_csf:
  • RS.AN-01
  • RS.AN-03
  • DE.AE-02
  • RS.MA-01

Performing Windows Artifact Analysis with Eric Zimmerman Tools

Overview

Eric Zimmerman's EZ Tools suite is a collection of open-source forensic utilities that have become the global standard for Windows digital forensics investigations. Originally developed by a former FBI agent and current SANS instructor, these tools parse and analyze critical Windows artifacts including the Master File Table ($MFT), registry hives, prefetch files, event logs, shortcut (LNK) files, and jump lists. The suite integrates with KAPE (Kroll Artifact Parser and Extractor) for automated artifact collection and processing, producing structured CSV output that can be ingested into Timeline Explorer for visual analysis. EZ Tools are widely used by law enforcement, corporate incident responders, and forensic consultants worldwide.

When to Use

  • When conducting security assessments that involve performing windows artifact analysis with eric zimmerman tools
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • Windows 10/11 or Windows Server 2016+ analysis workstation
  • .NET 6 Runtime installed (required for EZ Tools v2.x+)
  • Administrative privileges on the analysis workstation
  • Forensic disk image or triage collection from target system
  • At least 8 GB RAM (16 GB recommended for large datasets)
  • Familiarity with NTFS file system structures and Windows internals

Tool Suite Components

KAPE (Kroll Artifact Parser and Extractor)

KAPE is the primary orchestration tool that automates artifact collection (Targets) and processing (Modules). It uses configuration files (.tkape and .mkape) to define what artifacts to collect and which EZ Tools to run against them.

Installation and Setup:

# Download KAPE from https://www.kroll.com/en/services/cyber-risk/incident-response-litigation-support/kroll-artifact-parser-extractor-kape
# Extract to C:\Tools\KAPE

# Update KAPE targets and modules
C:\Tools\KAPE\gkape.exe  # GUI version
C:\Tools\KAPE\kape.exe   # CLI version

# Sync latest EZ Tools binaries
C:\Tools\KAPE\Get-KAPEUpdate.ps1

Running KAPE Collection and Processing:

# Collect artifacts from E: drive (mounted forensic image) and process with EZ Tools
kape.exe --tsource E: --tdest C:\Cases\Case001\Collection --target KapeTriage --mdest C:\Cases\Case001\Processed --module !EZParser

# Collect specific artifact categories
kape.exe --tsource E: --tdest C:\Cases\Case001\Collection --target FileSystem,RegistryHives,EventLogs --mdest C:\Cases\Case001\Processed --module MFTECmd,RECmd,EvtxECmd

# Live system triage collection (run as administrator)
kape.exe --tsource C: --tdest D:\LiveTriage\Collection --target KapeTriage --mdest D:\LiveTriage\Processed --module !EZParser --vhdx LiveTriageImage

MFTECmd - Master File Table Parser

MFTECmd parses the NTFS $MFT, $J (USN Journal), $Boot, $SDS, and $LogFile into human-readable CSV format.

# Parse the $MFT file
MFTECmd.exe -f "C:\Cases\Evidence\$MFT" --csv C:\Cases\Output --csvf MFT_output.csv

# Parse the USN Journal ($J)
MFTECmd.exe -f "C:\Cases\Evidence\$J" --csv C:\Cases\Output --csvf USNJournal_output.csv

# Parse $Boot for volume information
MFTECmd.exe -f "C:\Cases\Evidence\$Boot" --csv C:\Cases\Output --csvf Boot_output.csv

# Parse $SDS for security descriptors
MFTECmd.exe -f "C:\Cases\Evidence\$SDS" --csv C:\Cases\Output --csvf SDS_output.csv

Key Fields in MFT Output:

| Field | Description | |-------|-------------| | EntryNumber | MFT record number | | ParentEntryNumber | Parent directory MFT record | | InUse | Whether the record is active or deleted | | FileName | Name of the file or directory | | Created0x10 | $STANDARD_INFORMATION creation timestamp | | Created0x30 | $FILE_NAME creation timestamp | | LastModified0x10 | $STANDARD_INFORMATION modification timestamp | | IsDirectory | Boolean indicating directory or file | | FileSize | Logical file size in bytes | | Extension | File extension |

PECmd - Prefetch File Parser

PECmd parses Windows Prefetch files (.pf) to provide evidence of program execution, including run counts and timestamps.

# Parse all prefetch files from a directory
PECmd.exe -d "C:\Cases\Evidence\Windows\Prefetch" --csv C:\Cases\Output --csvf Prefetch_output.csv

# Parse a single prefetch file with verbose output
PECmd.exe -f "C:\Cases\Evidence\Windows\Prefetch\CMD.EXE-4A81B364.pf" --json C:\Cases\Output

# Parse prefetch with keyword filtering
PECmd.exe -d "C:\Cases\Evidence\Windows\Prefetch" -k "powershell,cmd,wscript,cscript,mshta" --csv C:\Cases\Output --csvf SuspiciousExec.csv

RECmd - Registry Explorer Command Line

RECmd processes Windows registry hives using batch files that define which keys and values to extract.

# Process all registry hives with the default batch file
RECmd.exe --bn C:\Tools\KAPE\Modules\bin\RECmd\BatchExamples\RECmd_Batch_MC.reb -d "C:\Cases\Evidence\Registry" --csv C:\Cases\Output --csvf Registry_output.csv

# Process a single NTUSER.DAT hive
RECmd.exe -f "C:\Cases\Evidence\Users\suspect\NTUSER.DAT" --bn C:\Tools\KAPE\Modules\bin\RECmd\BatchExamples\RECmd_Batch_MC.reb --csv C:\Cases\Output

# Process SYSTEM hive for USB device history
RECmd.exe -f "C:\Cases\Evidence\Registry\SYSTEM" --bn C:\Tools\KAPE\Modules\bin\RECmd\BatchExamples\RECmd_Batch_MC.reb --csv C:\Cases\Output

EvtxECmd - Windows Event Log Parser

EvtxECmd parses Windows Event Log (.evtx) files into structured CSV format with customizable event ID maps.

# Parse all event logs from a directory
EvtxECmd.exe -d "C:\Cases\Evidence\Windows\System32\winevt\Logs" --csv C:\Cases\Output --csvf EventLogs_output.csv

# Parse a single event log
EvtxECmd.exe -f "C:\Cases\Evidence\Security.evtx" --csv C:\Cases\Output --csvf Security_output.csv

# Parse with custom maps for enhanced field extraction
EvtxECmd.exe -d "C:\Cases\Evidence\Logs" --csv C:\Cases\Output --maps C:\Tools\KAPE\Modules\bin\EvtxECmd\Maps

LECmd and JLECmd - Shortcut and Jump List Parsers

# Parse LNK files from Recent directory
LECmd.exe -d "C:\Cases\Evidence\Users\suspect\AppData\Roaming\Microsoft\Windows\Recent" --csv C:\Cases\Output --csvf LNK_output.csv

# Parse Jump Lists (automatic destinations)
JLECmd.exe -d "C:\Cases\Evidence\Users\suspect\AppData\Roaming\Microsoft\Windows\Recent\AutomaticDestinations" --csv C:\Cases\Output --csvf JumpLists_auto.csv

# Parse Jump Lists (custom destinations)
JLECmd.exe -d "C:\Cases\Evidence\Users\suspect\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations" --csv C:\Cases\Output --csvf JumpLists_custom.csv

SBECmd - Shellbag Explorer Command Line

# Parse shellbags from a directory of registry hives
SBECmd.exe -d "C:\Cases\Evidence\Registry" --csv C:\Cases\Output --csvf Shellbags_output.csv

# Parse shellbags from a live system (requires admin)
SBECmd.exe --live --csv C:\Cases\Output --csvf LiveShellbags_output.csv

Timeline Explorer - Visual Analysis

Timeline Explorer is the GUI tool for analyzing CSV output from all EZ Tools. It supports filtering, sorting, column grouping, and conditional formatting.

# Launch Timeline Explorer and open CSV output
TimelineExplorer.exe "C:\Cases\Output\MFT_output.csv"

Key Timeline Explorer Features:

  • Column-level filtering with regular expressions
  • Conditional formatting for timestamp anomalies
  • Multi-column sorting for chronological analysis
  • Export filtered results to new CSV files
  • Bookmarking rows of interest

Investigation Workflow

Step 1: Artifact Collection with KAPE

# Full triage collection from forensic image mounted at E:
kape.exe --tsource E: --tdest C:\Cases\Case001\Collected --target KapeTriage --vhdx TriageImage --zv false

Step 2: Artifact Processing with EZ Tools

# Process all collected artifacts
kape.exe --msource C:\Cases\Case001\Collected --mdest C:\Cases\Case001\Processed --module !EZParser

Step 3: Timeline Analysis

  1. Open processed CSV files in Timeline Explorer
  2. Sort by timestamp columns to establish chronological order
  3. Filter for specific file extensions, paths, or event IDs
  4. Cross-reference MFT timestamps with event log entries
  5. Identify timestomping by comparing $SI and $FN timestamps
  6. Document findings with bookmarks and exported filtered views

Step 4: Timestomping Detection

# In Timeline Explorer, compare these columns:
# Created0x10 ($STANDARD_INFORMATION) vs Created0x30 ($FILE_NAME)
# If Created0x10 < Created0x30, timestomping is indicated
# $FILE_NAME timestamps are harder to manipulate than $STANDARD_INFORMATION

Forensic Artifacts Reference

| Tool | Artifact | Location | |------|----------|----------| | MFTECmd | $MFT | Root of NTFS volume | | MFTECmd | $J (USN Journal) | $Extend$UsnJrnl:$J | | PECmd | Prefetch files | C:\Windows\Prefetch*.pf | | RECmd | NTUSER.DAT | C:\Users{user}\NTUSER.DAT | | RECmd | SYSTEM hive | C:\Windows\System32\config\SYSTEM | | RECmd | SAM hive | C:\Windows\System32\config\SAM | | RECmd | SOFTWARE hive | C:\Windows\System32\config\SOFTWARE | | EvtxECmd | Event logs | C:\Windows\System32\winevt\Logs*.evtx | | LECmd | LNK files | C:\Users{user}\AppData\Roaming\Microsoft\Windows\Recent\ | | JLECmd | Jump lists | C:\Users{user}\AppData\Roaming\Microsoft\Windows\Recent\AutomaticDestinations\ | | SBECmd | Shellbags | NTUSER.DAT and UsrClass.dat registry hives |

Common Investigation Scenarios

Malware Execution Evidence

  1. Parse Prefetch with PECmd to identify executed binaries
  2. Cross-reference with MFT for file creation timestamps
  3. Check Amcache.hve with RECmd for SHA1 hashes of executables
  4. Correlate with Event Log entries for process creation (Event ID 4688)

Data Exfiltration Investigation

  1. Parse USN Journal with MFTECmd for file rename/delete operations
  2. Analyze LNK files with LECmd for recently accessed documents
  3. Review Shellbags with SBECmd for directory browsing activity
  4. Check for USB device connections in SYSTEM registry with RECmd

Lateral Movement Detection

  1. Parse Security.evtx with EvtxECmd for logon events (4624, 4625)
  2. Analyze RDP-related event logs (Microsoft-Windows-TerminalServices)
  3. Cross-reference with network share access from SMB logs
  4. Review scheduled tasks and services for persistence mechanisms

Output Format and Integration

All EZ Tools produce CSV output that can be:

  • Analyzed in Timeline Explorer for visual investigation
  • Imported into Splunk, Elastic, or other SIEM platforms
  • Processed by Python/PowerShell scripts for automated analysis
  • Combined into super timelines using log2timeline/Plaso

References

  • Eric Zimmerman's Tools: https://ericzimmerman.github.io/
  • KAPE Documentation: https://ericzimmerman.github.io/KapeDocs/
  • SANS EZ Tools Training: https://www.sans.org/tools/ez-tools
  • SANS FOR508: Advanced Incident Response and Threat Hunting
  • SANS FOR498: Battlefield Forensics & Data Acquisition

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/download' --output '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md.part' && mv '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md.part' '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Prerequisites
  • Windows 10/11 or Windows Server 2016+ analysis workstation
  • .NET 6 Runtime installed (required for EZ Tools v2.x+)
  • Administrative privileges on the analysis workstation
  • Forensic disk image or triage collection from target system
  • At least 8 GB RAM (16 GB recommended for large datasets)
  • Familiarity with NTFS file system structures and Windows internals

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md' && test -s '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/performing-windows-artifact-analysis-with-eric-zimmerman-tools' && cp -R '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs' '.claude/skills/performing-windows-artifact-analysis-with-eric-zimmerman-tools'

Cursor
test -f '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md' && test -s '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/performing-windows-artifact-analysis-with-eric-zimmerman-tools' && cp -R '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs' '.cursor/skills/performing-windows-artifact-analysis-with-eric-zimmerman-tools'

Codex
test -f '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md' && test -s '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/performing-windows-artifact-analysis-with-eric-zimmerman-tools' && cp -R '.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs' '.agents/skills/performing-windows-artifact-analysis-with-eric-zimmerman-tools'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs'

openskills read 'eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/eric-zimmerman-tools-for-windows-artifact-analysis-msh3uugs/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills