--- name: performing-windows-artifact-analysis-with-eric-zimm-ef68a4f93f17 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: Krishna Kumar (xalgord) 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 ## Detection Gaps & Validation EZ Tools parse what is present in the artifact; they do not tell you what was rolled, disabled, or never recorded. Account for these: - **Artifacts are finite and get pruned.** Prefetch holds only the last ~1024 executions (and is off by default on Servers/SSDs in some configs), so PECmd showing no entry for a binary is not proof it never ran. Amcache/`SOFTWARE`, ShimCache (AppCompatCache), and BAM/DAM give independent execution evidence — correlate all of them rather than trusting one. EVTX channels roll by size; the incident may predate the oldest `.evtx`. - **Timestomping defeats the easy timestamps.** MFTECmd surfaces `$STANDARD_INFORMATION` times that malware backdates; always compare `Created0x10` vs `Created0x30` ($SI vs $FN) — when $SI predates $FN, suspect manipulation. $FN times resist user-mode stomping but aren't immutable. Corroborate file creation with the USN Journal ($J), which records the rename/create operations themselves. - **Deleted and overwritten records.** A deleted EVTX, a cleared log (Event ID 1102/104), or an `InUse=false` MFT record means EvtxECmd/MFTECmd will show gaps, not activity. Recover from Volume Shadow Copies and carve unallocated space before scoping; flag clears explicitly as anti-forensics. - **Validate by cross-referencing tools.** A real execution should line up across PECmd (Prefetch), Amcache (hash + path via RECmd), MFT ($MFT creation), and Security 4688/Sysmon 1. A claim supported by only one artifact is a lead, not a conclusion. Hash-match suspect binaries before labeling them malicious. - **Interpretation false positives.** Prefetch/ShimCache prove a program existed/was referenced — ShimCache entries in particular do NOT prove execution, only presence. LNK and JumpList entries can be created by automated/recent-docs activity, not deliberate opens. Shellbags show a folder was browsed at some point, not when or by whom. Confirm operator intent with surrounding artifacts and timezone-normalized timelines. ## 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:** ```powershell # 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:** ```powershell # 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. ```powershell # 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. ```powershell # 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. ```powershell # 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. ```powershell # 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 ```powershell # 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 ```powershell # 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. ```powershell # 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 ```powershell # 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 ```powershell # 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 ```powershell # 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 --- Source attribution: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/digital-forensics/performing-windows-artifact-analysis-with-eric-zimmerman-tools/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2026 xalgord Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/digital-forensics/performing-windows-artifact-analysis-with-eric-zimmerman-tools/SKILL.md Attribution basis: Source repository record Fields of work: Data & Analytics Roles: Data Analyst Specialties: Specialty not specified Tools: Eric Zimmerman Tools, Kape Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 5538737e924d77aa01ea21f19d59f0e80e081c0095da27a6a83a08c3488e931d