Study guide
11.1 Windows Endpoint Forensics and Volatile Artifact Analysis
EC-Council Certified Incident Handler ECIH
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction to Incident Handling and Response
1.1 Information Security Fundamentals, Threat Landscapes, and Attack Vectors 1.2 Incident Management Principles, CSIRT Team Structures, and SOAR Automation 1.3 Cyber Defense Frameworks: NIST SP 800-61, ISO 27035, MITRE ATT&CK, and Cyber Kill Chain 1.4 Risk Management, Security Policies, and Security Auditing
2 Chapter 2: Incident Handling Process: Preparation, Detection, and Triage
2.1 Incident Response Preparation, Policies, and Playbook Design 2.2 Incident Recording, Categorization, and Triage Methodologies 2.3 Incident Notification, Escalation Paths, and Stakeholder Communication
3 Chapter 3: Incident Handling Process: Containment, Eradication, and Post-Incident
3.1 Incident Containment Strategies, Isolation, and Evidence Protection 3.2 Eradication Procedures, Remediation, and Secure System Recovery 3.3 Post-Incident Review, Lessons Learned, and Threat Intelligence Sharing
4 Chapter 4: Forensic Readiness and First Response
4.1 Forensic Readiness Planning, Legal Mandates, and Regulatory Compliance 4.2 First Response Principles, Scene Securing, and Order of Volatility 4.3 Digital Evidence Collection, Packaging, and Chain of Custody 4.4 Anti-Forensics Detection, Evidence Gaps, and Countermeasures
5 Chapter 5: Handling and Responding to Malware Incidents
5.1 Malware Classification, Attack Vectors, and Modern Threat Profiles 5.2 Static Analysis, Dynamic Analysis, and Sandboxing Workflows 5.3 Malware Detection, Memory Forensics, and Eradication Strategies
6 Chapter 6: Handling and Responding to Email Security Incidents
6.1 Email Attack Vectors: Phishing, Spear Phishing, BEC, and Spoofing 6.2 Email Header Forensics, Link Triage, and Malicious Attachment Analysis 6.3 Email Authentication Protocols (SPF, DKIM, DMARC) and Incident Containment
7 Chapter 7: Handling and Responding to Network Security Incidents
7.1 Network Reconnaissance, Unauthorized Access, and Port Scanning 7.2 Denial of Service (DoS/DDoS) Attack Mechanisms and Traffic Mitigation 7.3 Wireless Network Incidents, Session Hijacking, and Packet Analysis 7.4 Inappropriate Usage Incidents: Validation, Evidence, and Response
8 Chapter 8: Handling and Responding to Web Application Security Incidents
8.1 Web Application Threat Vectors: Injection, XSS, and CSRF Incidents 8.2 Web Server and Application Log Analysis (Apache, Nginx, IIS) 8.3 Web Application Incident Containment, Patching, and Defense-in-Depth
9 Chapter 9: Handling and Responding to Cloud Security Incidents
9.1 Cloud Shared Responsibility, Threat Landscape, and IAM Attacks 9.2 Cloud Telemetry and Audit Logging (AWS CloudTrail, Azure Activity, GCP Audit) 9.3 Cloud Incident Containment, Snapshot Forensics, and Container Security
10 Chapter 10: Handling and Responding to Insider Threats
10.1 Insider Threat Typologies, Behavioral Indicators, and Risk Profiles 10.2 Insider Threat Detection: UEBA, Data Loss Prevention, and Audit Trails 10.3 Insider Incident Investigation, Evidence Handling, and Legal Reporting
11 Chapter 11: Handling and Responding to Endpoint, IoT, and OT Incidents
11.1 Windows Endpoint Forensics and Volatile Artifact Analysis 11.2 Linux and macOS Endpoint Incident Investigation 11.3 Mobile Device Isolation, Acquisition, and Incident Handling 11.4 IoT Incident Handling and Firmware Investigation 11.5 OT and ICS Incident Handling: Safety, Visibility, and Recovery
11.1 Windows Endpoint Forensics and Volatile Artifact Analysis
Key Takeaways Explain This Topic AI
NTFS metadata structures—specifically the $MFT, $LogFile, and $UsnJrnl—provide complementary, retention-limited records of file activity; discrepancies between $STANDARD_INFORMATION and $FILE_NAME attributes.
Windows execution analysis must triangulate artifacts: Prefetch can record run counts and timestamps, BAM/DAM can indicate recent per-user execution, and Shimcache generally supports file-presence or compatibility evidence but alone does not prove execution.
Shellbags, LNK files, Jump Lists, and RecentDocs can support inferences about folder navigation and file interaction, including removable media, but should be correlated before attributing deliberate user action.
Windows event auditing provides high-value telemetry through Event IDs 4624, 4625, 4688 when enabled, 7045, and PowerShell 4104 when configured; retention, policy, and tampering affect completeness.
Targeted collection with KAPE or Velociraptor can acquire selected high-value artifacts faster than full-disk imaging; acquisition time and volatile coverage depend on the target, tool, permissions, and collection plan.
Last updated: October 2026
Windows Endpoint Forensics and Volatile Artifact Analysis
Incident handling on Windows endpoints requires deep knowledge of file system metadata, execution tracking, and event auditing. Because Windows hosts represent primary targets for initial access, privilege escalation, and lateral movement, responders must extract and correlate high-fidelity artifacts under crisis conditions. Intruders frequently leverage living-off-the-land binaries, in-memory execution, and timestomping to conceal activity. Handlers must triangulate forensic evidence across file systems, registry hives, and event logs to establish proof of presence, execution, and user interaction.
Low-Level NTFS File System Artifacts
The New Technology File System (NTFS) maintains low-level metadata tracking file lifecycle events:
Master File Table ($MFT): Structural core of NTFS allocating a 1024-byte record per file and folder. Key attributes include:
$STANDARD_INFORMATION ($SI): Stores DOS permissions and MACB (Modified, Accessed, Created/Born, Entry Modified) timestamps. Because user-mode APIs like SetFileTime can modify $SI, adversaries and tools like Cobalt Strike or timestomp alter it to blend into system directories.
$FILE_NAME ($FN): Stores file name, namespace, parent directory reference, and independent MACB timestamps. The $FN attribute is updated only by the NT kernel during file operations (renaming, creating, moving). Handlers detect timestomping by identifying discrepancies where $SI timestamps are backdated while $FN timestamps record true creation times.
$LogFile: Circular transaction log in the volume root recording metadata changes (cluster allocation, index updates) to ensure consistency during crashes. Handlers inspect it to track immediate pre-incident file transactions.
$UsnJrnl (Update Sequence Number Journal): Stored in $Extend as the $J alternate data stream, $UsnJrnl logs file and directory modifications, deletions, renames, and attribute shifts. Because records persist after file deletion and $MFT record reuse, it provides vital evidence of deleted staging archives, scripts, or malware droppers.
Volume Shadow Copies (VSS): Differential block-level snapshots created by the Volume Snapshot Service. Handlers query snapshots using vssadmin list shadows to recover pre-attack file states, deleted tools, and registry hives prior to ransomware encryption.
Program Execution Artifacts and Triangulation
Proving an executable was present on disk does not prove execution. Handlers triangulate evidence across multiple execution artifacts:
Prefetch (.pf files): Windows Cache Manager creates Prefetch files in C:\Windows\Prefetch\ to optimize launch performance. Named after the executable plus an 8-character path hash (e.g., CMD.EXE-A1B2C3D4.pf), Prefetch records run count, last launch time, and—in Windows 10/11—up to seven prior execution timestamps (eight runs total). It also lists loaded DLLs and dependencies from the first 10 seconds of runtime.
Shimcache (AppCompatCache): Located in the SYSTEM hive under CurrentControlSet\Control\Session Manager\AppCompatCache , Shimcache tracks application compatibility. Written to disk upon shutdown or restart, it records full paths, file sizes, last modified timestamps, and compatibility flags. In modern Windows, a Shimcache entry supports that a path and file metadata were observed by the compatibility mechanism, but it does not by itself prove execution or current file presence. Handlers must corroborate Shimcache with execution artifacts.
Amcache.hve: A dedicated hive at C:\Windows\appcompat\Programs\Amcache.hve recording installed applications and portable executables (PEs). It captures SHA-1 hashes, compile timestamps, file sizes, PE header details, and installation times, enabling hash recovery of deleted binaries.
UserAssist Registry Keys: Stored in NTUSER.DAT under Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{GUID}\Count . Tracking GUI-launched programs via Windows Explorer, value names are ROT13-encoded. Decoded entries reveal executable paths, run counts, and the last execution FILETIME timestamp per user.
BAM and DAM (Background / Desktop Activity Moderator): Located in SYSTEM\CurrentControlSet\Services\bam\State\UserSettings\{SID} , this service manages application power consumption, recording the full path and 64-bit FILETIME of last execution per user SID.
File Opening, Access, and Folder Browsing Artifacts
Reconstructing file access and interactive directory traversal relies on specific access artifacts:
LNK Shortcut Files: Stored in %APPDATA%\Microsoft\Windows\Recent\ , LNK files generate automatically when documents are opened. They record target paths, file sizes, volume serial numbers, target MACB timestamps, and host NetBIOS names, proving file access even if stored on detached USB drives.
Shellbags: Stored in UsrClass.dat under Local Settings\Software\Microsoft\Windows\Shell\Bags and BagsMRU, Shellbags retain folder view preferences and namespace artifacts from Windows Explorer. They can indicate that a folder was represented or browsed in an Explorer context, supporting reconstruction of directory traversal across local drives, network shares, and removable media, even after folders are deleted.
Jump Lists: Located in %APPDATA%\Microsoft\Windows\Recent\AutomaticDestinations\ and CustomDestinations\ , Jump Lists store application-specific Most Recently Used (MRU) records in MS-SHLLINK compound format, documenting recent documents opened within specific programs.
RecentDocs: Registry key in NTUSER.DAT tracking recently opened files grouped by extension in MRU order.
Windows Event Log Analysis
The Windows Event Log repository ( C:\Windows\System32\winevt\Logs\ ) provides high-fidelity auditing:
Security Log Event IDs:
4624 (Successful Logon): Evaluates logon mechanisms via LogonType: Type 2 (Interactive console), Type 3 (Network logon—SMB, RPC, PsExec), Type 4 (Batch), Type 5 (Service), Type 7 (Unlock), Type 9 (NewCredentials), Type 10 (RemoteInteractive—RDP), and Type 11 (CachedInteractive).
4625 (Failed Logon): Detects brute-force attacks via failure codes: 0xC000006A (bad password), 0xC0000064 (invalid user), and 0xC0000234 (account locked).
4672 (Special Privileges Assigned): Documents administrative logons assigning high-privilege tokens (e.g., SeDebugPrivilege).
4688 (Process Creation): Documents process execution. With Command Line Auditing enabled, it records process names, parent processes, and exact CLI arguments.
4720 (User Created) & 4726 (User Deleted): Detects unauthorized account creation or deletion for persistence.
7045 (System Log: New Service Installed) & 4697 (Security Log): Detects service persistence and remote execution utilities (e.g., PsExec PSEXESVC).
1102 (The Audit Log Was Cleared): High-severity indicator of adversary anti-forensics.
PowerShell Auditing: When enabled, Script Block Logging (Event ID 4104) records PowerShell script blocks and often captures content after PowerShell has decoded or assembled it; it is not guaranteed to be complete or immune to evasion and tampering. Module Logging (Event ID 4103) and Transcription logging record pipeline executions and terminal sessions.
Live Triage Frameworks and Rapid Acquisition
Dead-box forensic imaging introduces intolerable latency during active breaches. Responders deploy live triage tools:
KAPE (Kroll Artifact Parser and Extractor): Employs Targets (.tkape) to extract high-value artifacts (MFT, registries, logs, Prefetch) in minutes, and Modules (.mkape) to run parsers.
Velociraptor: An endpoint visibility and forensics platform using Velociraptor Query Language (VQL) to hunt IoCs, query registries, dump memory, and extract artifacts at enterprise scale.
FTK Imager: Standard tool for acquiring forensically sound physical and logical images, memory dumps, and generating SHA-256 evidence hashes.