<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dfirhive on Medium]]></title>
        <description><![CDATA[Stories by Dfirhive on Medium]]></description>
        <link>https://medium.com/@dfirhive?source=rss-64015b635e0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*kuH_qMYujc_PvZWm</url>
            <title>Stories by Dfirhive on Medium</title>
            <link>https://medium.com/@dfirhive?source=rss-64015b635e0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:22:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dfirhive/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From RAM to Evidence (Part 1): Capturing Volatile Memory on Windows]]></title>
            <link>https://medium.com/@dfirhive/from-ram-to-evidence-part-1-capturing-volatile-memory-on-windows-e57940fe47cf?source=rss-64015b635e0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e57940fe47cf</guid>
            <category><![CDATA[memory-forensics]]></category>
            <category><![CDATA[dfir]]></category>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <dc:creator><![CDATA[Dfirhive]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 18:52:10 GMT</pubDate>
            <atom:updated>2025-10-15T18:52:10.811Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Digital illustration showing forensic investigators analyzing volatile memory on a Windows system, symbolized with RAM chips, binary code, and a magnifying glass, representing memory acquisition in digital forensics." src="https://cdn-images-1.medium.com/max/1024/0*hoKqZI_3czm-Bmns.png" /></figure><p><strong><em>“RAM is like a crime scene in motion — if you don’t capture it fast, it’s gone forever.”</em></strong></p><p>*”This is the first article of the Memory Forensics series, where we explore how volatile memory can be acquired and preserved for use in investigations.</p><p>In this part, we focus on <strong>memory acquisition</strong> — the process of capturing live RAM from a Windows machine before it disappears. RAM holds valuable data such as running processes, credentials, injected code, and command-and-control activity. Unlike disk evidence, however, it vanishes once power is lost, making proper acquisition both time-sensitive and critical.</p><p>Here, we’ll walk through the <strong>key decisions to make before hitting ‘capture’</strong>, introduce tools like FTK Imager and procdump64, and outline practical steps to ensure integrity when acquiring memory.”*</p><p><strong>Before diving into tools, let’s first look at what to consider when planning a memory acquisition.</strong></p><h3>Planning Memory Acquisition: Key Considerations</h3><p>Tools like FTK Imager or DumpIt are only the final step in memory acquisition — the real work begins with planning. Before capturing, ask yourself :</p><p><strong>What regions of memory are relevant to my case?</strong> <strong>How will I acquire them</strong>, <strong>what format will my tools accept</strong>, and <strong>how will I prove integrity</strong>?</p><p>(Skipping these questions risks producing incomplete, noisy, or even unusable evidence)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/0*g4ar-qiZ46e4HeuD.png" /></figure><p><em>“The following steps summarize a structured approach to capturing memory effecitvely.”</em></p><h3>Do you really need the whole RAM?</h3><p>A full memory dump captures everything, but it is often bulky and noisy. In many cases, a smaller snapshot is sufficient.</p><p>For instance, if malicious code is injected only into a browser process, capturing the entire RAM may be unnecessary- a targeted <strong>process dump</strong> will save both time and reduce noise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/0*OdZ7u9tvDMgXKV6C.png" /><figcaption><em>“Each dump types serve different purposes. Pick the one that aligns with your case and tools.”</em></figcaption></figure><h3>File Formats That Matter:</h3><p>Memory dumps come in different formats, each serving specific tools and use cases. The key is to choose a format that your analysis stack supports:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/0*rJNim7G8bOt0c8XT.png" /><figcaption><em>“Here are some of the most commonly used memory dump formats in forensics.”</em></figcaption></figure><h3>Approaches to Memory Acquisition</h3><p>Memory can be captured in different ways, and each approach comes with trade-offs.</p><ul><li><strong>Local</strong> <strong>Acquisition</strong>→ Tool runs directly on the target machine, which requires physical access.</li><li><strong>Remote</strong> <strong>Acquisition</strong>→ Captures memory over the network, convenient but increases security risk.</li><li><strong>Hardware</strong> <strong>Acquisition</strong>→ Specialized PCIe or DMA devices pull memory outside the OS, Very clean but often expensive.</li></ul><p>Below are some of the most commonly used tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/913/1*ZIk2xProCMehWrmBiuFtCQ.png" /></figure><pre>&quot;After selecting the right acquisition method and tool, the next step is applying in practice. Let&#39;s walk through how to capture memory on Windows.&quot;</pre><h3>Memory Acquisition on Windows: Practical</h3><p>For this exercise, we will use a <strong>Windows 11 workstation</strong> with <strong>FTK Imager</strong> and <strong>Sysinternals Suite</strong> installed.</p><p>Acquiring volatile memory on a Windows machine is a critical step in incident response. In this walk-through, we will demonstrate:</p><ol><li><strong>Full memory dump using FTK Imager: </strong>Captures entire RAM for comprehensive analysis.</li><li><strong>Process memory dump</strong> with <strong>procdump64.exe</strong> from the Sysinternals Suite- targets a specific process (e.g, explorer.exe)</li><li><strong>Small crash dumps- </strong>Configuring the system to generate dumps automatically during failures.</li></ol><p>Since the dumps will later be analyzed with <strong>Volatility</strong>, it is important to ensure that the formats are compatible. Volatility supports a wide range of dump types, including:</p><ul><li>Raw physical memory (.raw/.mem)</li><li>Windows crash dumps (32/64-bit)</li><li>Windows hibernation files</li><li>VMware (.vmss, .vmsn)</li><li>VirtualBox core dumps</li><li>LiME (Linux Memory Extractor)</li><li>QEMU VM memory dumps</li></ul><p>After each acquisition, always generate a <strong>hash</strong> (MD5 and SHA256) to verify integrity. This ensures that the data you analyze later is identical to what was captured originally.</p><p><strong>Note: SHA256 is preferred in modern practice. MD5 is still used for legacy compatibility.</strong></p><blockquote>I’ve covered a full Volatility walkthrough in a separate post on <a href="https://www.dfirhive.com/post/volatility-forensics-a-beginner-s-guide-to-memory-analysis">DFIR Hive </a>— this article focuses mainly on acquisition, while that one dives into analysis. <a href="https://www.dfirhive.com/post/volatility-forensics-a-beginner-s-guide-to-memory-analysis">Here →</a></blockquote><h3>Full Memory Capture (FTK Imager)</h3><p>To acquire a full memory dump, we’ll use FTK Imager, a widely trusted forensic tool.(GUI-based, Portable option, trusted in court)</p><p>FTK Imager can be downloaded from Exterro’s official website: <a href="https://go.exterro.com/l/43312/2023-05-03/fc4b78?_gl=1*12pm8fd*_gcl_au*Mzk4OTkyNTM0LjE3NTYxMzI2MTcuODY2NTk5ODUuMTc1ODI5OTIyMy4xNzU4Mjk5MjIz">Exterro Website</a></p><h3>Steps to Capture Memory</h3><ol><li><strong>Run FTK Imager as Administrator: </strong>Open FTK Imager with administrative privileges. This ensures the tool can access system memory</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*o_AYvYEiRdQD9ML6.png" /><figcaption><em>“Launching FTK Imager with admin access to prepare for full memory acquisition”</em></figcaption></figure><p><strong>2. Navigate to File → Capture Memory : </strong>In the menu bar, go to File and select Capture Memory</p><p><strong>3. Select the Destination path and the File name: </strong>Choose the memory image path and provide a file name</p><p>(It is a good practice to include date/time in the destination file name for traceability e.g.., CaseID_Hostname_Date_Time.mem)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*GaPFkKu-gzB5_Nth.png" /><figcaption><em>“Configuring FTK Imager to capture memory-selecting destination path and naming the output file”</em></figcaption></figure><p><strong>4. (Optional) Include pagefile: </strong>You may choose to skip including the pagefile to reduce size, as I did in this example.</p><p><strong>5. Start Capture: </strong>Click OK to begin the acquisition. Depending on the system RAM size, this may take several minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/0*c2SBKDq1U7Ny0pLh.png" /><figcaption><em>“FTK Imager in action”</em></figcaption></figure><p><strong>6. Verifying the Hash of the Dump: </strong>After acquisition, generate a hash MD5/SHA256 using PowerShell or any hashing tool (HashCalc, md5deep). This ensures the memory image you analyze is identical to the one captured.</p><blockquote><strong>Note: Always document the generated hash values in your case notes for the chain of custody</strong></blockquote><p>The command:</p><pre>Get-FileHash -Path &quot;Filepath&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*JP3ynuDNtoBBA2dx.png" /></figure><p><strong>Note: </strong>By default, PowerShell uses SHA256 if you don’t explicitly specify an algorithm. You can explicitly choose another hash type using the<strong> -Algorithm </strong>parameter</p><pre>Get-FileHash -Path &quot;Filepath&quot; -Algorithm MD5</pre><h3>Process Memory Dump with procdump64</h3><p>For a targeted dump, we can use Sysinternals ProcDump. In this example, we capture the memory of the explorer.exe process. (explorer.exe is always running under a user session; attackers often inject malicious code into it. <a href="http://it.ca/">Ca</a>pturing this process helps detect injections or persistence mechanisms.)</p><p>Download from the official site: <a href="https://learn.microsoft.com/en-us/sysinternals/downloads/sysinternals-suite">https://learn.microsoft.com/en-us/sysinternals/downloads/sysinternals-suite</a></p><p>Steps to Capture a Process Dump</p><ol><li><strong>Open PowerShell as Administrator.</strong></li><li><strong>Navigate to the Sysinternals folder</strong></li></ol><pre>cd &quot;FilePath&quot;</pre><p><strong>3.Run the Procdump command</strong></p><pre>\procdump64.exe -ma explorer.exe &quot;.memfilepath&quot; -accepteula</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*FsozG5xtAUftbFI_.png" /></figure><p>Have a closer look at the options included in the command:</p><ul><li><strong>-ma</strong>: Captures a full memory dump of the process. (The default option is a minidump (<strong>-mm</strong>), which only contains basic information about the process.)</li><li>Use the <strong>-h </strong>command to view all available flags</li><li><strong>explorer.exe:</strong> The target process whose memory is being dumped.</li><li><strong>-accepteula:</strong> Automatically accepts the sysinternals agreement so the tool can run without prompting the user.</li></ul><p><strong>4. Verifying Hash of Dump</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*dhgRL7fGigrQLIqX.png" /></figure><p>Alternatives for Memory capture on Windows</p><p>While <strong>FTK Imager</strong> and <strong>ProcDump </strong>are widely used, several other tools can be used depending on the use case:</p><p><strong>For Full Memory Dumps:</strong></p><ul><li><strong>Magnet RAM Capture</strong> → Free tool, lightweight, works well on most Windows versions.</li></ul><p>Link: <a href="https://www.magnetforensics.com/resources/magnet-dumpit-for-windows/#resource-bottom-content">https://www.magnetforensics.com/resources/magnet-dumpit-for-windows/#resource-bottom-content</a></p><ul><li><strong>Belkasoft Live RAM Capturer</strong></li></ul><p>Link: <a href="https://belkasoft.com/trial">https://belkasoft.com/trial</a></p><ul><li><strong>WinPmem</strong> → Open-source, supports raw dumps (.raw, .mem), integrates well with Volatility.</li></ul><p>Link: <a href="https://github.com/Velocidex/WinPmem/releases">https://github.com/Velocidex/WinPmem/releases</a></p><p><strong>For Process Dumps (Targeted):</strong></p><ul><li><strong>Task Manager</strong> (Windows 10/11) → Right-click a process → <em>Create Dump File</em>. Simple but limited.</li><li><strong>Process Explorer (Sysinternals)</strong> → GUI alternative to ProcDump, with right-click dump option.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/0*hUSFJSvUBGrTENxG.png" /></figure><ul><li><strong>Process Hacker</strong> → Another GUI tool, useful for capturing process memory, threads, and handles.</li></ul><p><strong>Note: Always test these tools in a lab before using them in the field. Some may cause system instability or be blocked by endpoint security solutions.</strong></p><h3>Configuring Crash Dumps on Windows 11</h3><p>Windows can be configured to automatically create a memory dump file whenever the system crashes. This is not a replacement for full memory capture, but it provides additional coverage and can be helpful.</p><p>Steps to configure crash dumps</p><ol><li>Press Win + R, type sysdm.cpl, and hit Enter.</li><li>Go to Startup and Recovery Settings</li><li>Navigate to:Advanced → Startup and Recovery → Settings</li><li>Choose Memory Dump</li><li>Under <strong>Write debugging information</strong>, which dump to choose will depend on your use case.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*sn9Zm6ar-IyBdEMd.png" /><figcaption><em>“Configuring crash dumps in Windows 11”</em></figcaption></figure><p><strong>Note: Crash dumps only trigger during system failures.</strong></p><h3>From Lab to Field: Practical Notes &amp; Real-World Scenarios:</h3><p>Memory forensics in the lab is straightforward. In the field, it rarely is. Here are some realities to keep in mind when acquiring memory on Windows:</p><ol><li>System State</li></ol><ul><li><strong>Sleep</strong> → You’ll need to wake the system before using tools. Act fast, as RAM changes once active.</li><li><strong>Hibernate</strong> → Collect hiberfil.sys, since it contains RAM contents at power-down.</li><li><strong>Crashed system</strong> → Use configured crash dumps as fallback evidence.</li></ul><p>2. Security Tools</p><ul><li><strong>EDR/AV may block dumps</strong> (e.g., LSASS). If blocked, capture full memory instead of a process dump.</li></ul><p>3. Storage &amp; Size</p><ul><li>Full dumps can be <strong>tens of GBs</strong>. Always dump to <strong>external media</strong> to avoid overwriting host artifacts.</li></ul><p>4. Time Sensitivity</p><ul><li>Malware and ransomware often clean traces in memory. The <strong>sooner you capture</strong>, the better.</li></ul><p>5. Virtual Environments</p><ul><li>If the target is a VM, use <strong>hypervisor snapshots</strong> (.vmsn, .vmss, .vmem) instead of in-guest tools when possible.</li></ul><h3>Tools &amp; Portability</h3><ul><li>Use <strong>portable versions</strong> (e.g., FTK Imager Lite, WinPmem from USB) to avoid altering the system.</li><li>Avoid installing new software on the suspect host unless absolutely necessary.</li></ul><h3>Chain of Custody</h3><ul><li>Document <strong>who, what, when, and how</strong> for each acquisition.</li><li>Always generate and record <strong>hashes (SHA256 preferred)</strong> immediately after capture.</li></ul><blockquote>For those working on Linux systems, I’ve also shared a separate memory capture workflow using LiME and built-in acquisition tools — same approach, different environment. <a href="https://www.dfirhive.com/post/from-ram-to-evidence-part-2-capturing-volatile-memory-on-linux">Here →</a></blockquote><p>HAPPY LEARNING!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e57940fe47cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Guide to KAPE: Streamlining Windows Forensics]]></title>
            <link>https://medium.com/@dfirhive/a-guide-to-kape-streamlining-windows-forensics-0d2dd4a03051?source=rss-64015b635e0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d2dd4a03051</guid>
            <category><![CDATA[dfir]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <category><![CDATA[incident-response]]></category>
            <dc:creator><![CDATA[Dfirhive]]></dc:creator>
            <pubDate>Sun, 12 Oct 2025 12:22:44 GMT</pubDate>
            <atom:updated>2025-10-12T12:22:44.399Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*cPK0NbldLfxu0yofnBcaig.avif" /></figure><p><strong>“In digital forensics, time is the currency,”</strong> and If you ever worked a forensic case on Windows, you know the struggle- event logs, registry hives, prefetch files, shadow copies…they all pile up into a mountain of artifacts.</p><p>Each artifact might hold a clue. But digging manually? That feels endless. Imaging a whole disk is thorough, sure, but who has hours when the pressure is on?</p><p>That’s exactly the gap <strong>KAPE (Kroll Artifact Parser and Extractor)</strong> was built to fill in. Instead of spending hours grabbing artifacts one by one, KAPE helps you triage and pull out what matters in minutes.</p><p>Launched in <strong>2019 by Eric</strong> <strong>Zimmerman</strong>, a name most of us in the forensic world recognize- KAPE has grown into a go-to-tool for incident response, investigations, and even enterprise security audits. It doesn’t replace deep-dive analysis, but it gives you the speed to actually keep up with today’s cases.”</p><h3>From Imaging to Triage: Why KAPE Speeds Up Forensics</h3><h4>Before KAPE, analysts often relied on:</h4><ul><li><strong>Full disk imaging</strong> → thorough but painfully slow.</li><li><strong>Manual artifact extraction</strong> → precise but time-consuming.</li></ul><p>KAPE flips this with a <strong>triage-first model</strong>:</p><ul><li>Collect the <strong>most relevant artifacts first.</strong></li><li>Parse them <strong>instantly</strong> with proven tools.</li><li>Get <strong>structured outputs</strong> (CSV, JSON, TXT) that are ready to dive into.</li></ul><p>It doesn’t replace deep dives, but it gives analysts something just as valuable: speed, clarity, and early leads when time matters most</p><p><strong>To Download KAPE</strong>: <a href="https://www.kroll.com/en/services/cyber/incident-response-recovery/kroll-artifact-parser-and-extractor-kape">https://www.kroll.com/en/services/cyber/incident-response-recovery/kroll-artifact-parser-and-extractor-kape</a></p><h3>How KAPE Works:</h3><p>One of the best thing about KAPE is that it doesn’t need heavy setup-no big installs, you can run it straight from a USB drive, network share, or even a folder on your machine.</p><p>At its core, KAPE works in <strong>two simple phases</strong>:</p><ol><li><strong>Collection (Targets)</strong> → Think of this as deciding what evidence you actually care about.</li></ol><ul><li>KAPE goes after the artifacts you select.</li><li>Files are queued in two passes: unlocked files are copied directly, while locked files are captured using raw disk reads.</li><li>All metadata and timestamps are preserved.</li></ul><p><strong>2. Processing (Modules)</strong> → It defines how to parse collected files.</p><ul><li>Once the files are collected, modules (often powered by Eric Zimmerman’s suite) run automatically to parse them</li><li>Output is saved in investigator-friendly formats like CSV or JSON.</li></ul><p><strong>Targets = what you grab</strong></p><p><strong>Modules = How you read it.</strong></p><p>Together they form a fast triage pipeline: collect first, translate immediately, act faster.</p><p><strong>Targets</strong>: Narrowing the Hunt</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/0*7AtUHfJ4THJyNsfx.png" /><figcaption><em>“Targets in action: instead of imaging everything, pick what matters most”</em></figcaption></figure><p>In practice, investigators don’t need everything from the disk — what matters is knowing where to look first. That’s where <strong>Targets</strong> comes in. Instead of imaging terabytes of data, <strong>.tkape files</strong> let us define exactly what KAPE should extract.</p><p>Some of the usual suspects:</p><ul><li><strong>Prefetch</strong> (*.pf files) → Quick evidence of which program ran</li><li><strong>Registry hives</strong> → Rich content on both user and system activity.</li><li><strong>Event logs</strong> → The go-to for logons, process creation, and persistence.</li></ul><p>When we need speed, we don’t cherry-pick. We use <strong>Compound Targets</strong> like <strong>KapeTriage </strong>bundle together the most common artifacts (AmCache, SysCache, Registry, logs) so we can run one command and start making sense of the activity trail faster.</p><p>Targets aren’t static either. They are organized into folders:</p><ul><li><strong>!Disabled:</strong> Rules you don’t need right now.</li><li><strong>!Local: </strong>Custom, environment-specific Targets that remain untouched during updates.</li></ul><p><strong>Targets define scope. They’re our evidence checklist.</strong></p><p><strong>Module</strong>: The Evidence Translators</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/917/0*F3GTm7fiPX92irKN.png" /><figcaption><em>“Modules: Turning raw data into readable stories”</em></figcaption></figure><p>Raw artifacts by themselves don’t tell us much — they are just noise until we give them structure. That’s where <strong>Modules</strong> steps in.</p><p>“Think of them as translators : each modules tells KAPE exactly what to run, how to process it, and where the results should go.</p><p>A Module (.mkape) basically answers four questions:</p><ul><li><strong>What tool should I use? </strong>(e.g.., PECmd for Prefectch , EvtxECmd for Event Logs)</li><li><strong>What Arguments should I pass? </strong>(commonly export to CSV or JSON)</li><li><strong>Where do I put the Output, which is — Output destination</strong></li><li><strong>In what format</strong> (CSV for spreadsheets, JSON for automation, TXT for logs)</li></ul><p>Here’s a quick Example, the <strong>Prefetch Module</strong> runs PECmd.exe over .pf files and outputs a CSV timeline of executed applications instantly.</p><p>When scale matters, we don’t run tools one by one. <strong>Compound Modules </strong>let KAPE chain multiple parsers in sequence.</p><p>For example:</p><p><strong>!EZParser</strong> → processes Prefetch, Registry, AmCache, Event Logs, and more.</p><p><strong>This reduces repetitive execution and ensures consistency across cases.</strong></p><p><strong>The Bin Directory</strong>: Behind the scene, Modules depend on a Bin directory of third-party executables. To make KAPE portable, these tools live in the bin directory (commonly Zimmerman’s suite).</p><p>No matter where KAPE runs — USB, network share, or local — the tools are always available.</p><p><strong>Modules don’t just parse data-they translate noise into narrative</strong></p><h3>Operating KAPE</h3><p>KAPE can be operated in two ways:</p><ul><li><strong>Graphical interface (gkape.exe) </strong>→ clear and visual, useful for transparency and training.</li><li><strong>Command line (kape.exe) </strong>→ faster, scriptable, and the method of choice for live incidents.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*Dsao02CH38gj8MCQ.png" /><figcaption><em>“KAPE folder structure- everything you need in one place”</em></figcaption></figure><h3>Operating with the GUI (gkape.exe)</h3><p>If you like things visual, KAPE’s GUI (gkape.exe) makes life much easier. Think of it as dashboard where you decide what to collect and how to process it. When you launch the graphical interface, KAPE presents a two-panel view:</p><ul><li><strong>Left panel</strong> → <em>Target configuration</em>: Here you tell KAPE what evidence you want to grab and from where (disk, folder, or mounted images) and where to save it.</li><li><strong>Right panel</strong> → <em>Module configuration</em>: This is where you decide what to do with the evidence once it’s collected — which parsers to run, what output to use, and where results should be saved.</li></ul><p>This design reflects KAPE’s two-phase model: <em>collection first, processing second</em>.</p><p><strong>Step 1: Target Configuration</strong></p><ol><li><strong>Source (Target Source / — tsource)</strong></li></ol><ul><li>The root drive or directory to collect from.</li><li>Can also point to mounted images or alternate directories.</li></ul><p><strong>2. Destination (Target Destination / — tdest)</strong></p><ul><li>Path where collected artifacts are stored.</li><li>KAPE creates the directory if it does not exist.</li></ul><p><strong>3. Target Selection ( — target)</strong></p><ul><li>Choose individual Targets (e.g., Prefetch) or Compound Targets (e.g., KapeTriage).</li></ul><p><strong>4. Flush Option ( — tflush)</strong></p><ul><li>Determines whether KAPE clears the destination folder before each run.</li><li>Useful to prevent mixing old and new evidence, but risky if not intentional.</li></ul><p><strong>5. Additional Options</strong></p><ul><li><strong>Deduplication ( — tdd)</strong> → prevents duplicate copies, especially useful when collecting from Volume Shadow Copies.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*2RTMQUkme5Y-D85z.png" /><figcaption><em>“The GUI view: configure, select, and execute with clicks”</em></figcaption></figure><p><strong>Step 2: Module Configuration</strong></p><ol><li><strong>Module Source ( — msource)</strong></li></ol><ul><li>Defines the folder KAPE should process.</li><li>By default, if left empty, this points to the same folder used for Target Destination ( — tdest)</li></ul><p><strong>2. Module Destination ( — mdest)</strong></p><ul><li>Directory where parsed results will be stored.</li><li>Keeping this separate from — tdest ensures raw artifacts stays untouched while processed output remain clen and organized remain distinct.</li></ul><p><strong>3. Module Selection ( — module)</strong></p><ul><li>Choose one or multiple modules, or compound sets like !EZParser.</li><li>!EZParser is frequently used in the field because it automatically runs parsers against Prefetch, Registry, AmCache, and Event Logs.</li></ul><p><strong>4. Module Flush ( — mflush)</strong></p><ul><li>Same as — tflush but applies to the module output directory.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/0*wrU20P823h4wsuyI.png" /></figure><p><strong>Step 3: Additional Options</strong></p><p>KAPE’s GUI exposes advanced features:</p><p><strong>a. Packaging</strong></p><ul><li>— zip, — vhd, — vhdx: Package all results into a container for easy transfer.</li><li>— zpw: Apply a password to ZIP files.</li></ul><p><strong>b. Volume Shadow Copies ( — vss)</strong></p><ul><li>Instructs KAPE to collect from shadow copies.</li></ul><p><strong>c. Cloud/Remote Transfer</strong></p><ul><li>Upload processed output to S3 or SFTP directly from KAPE.</li><li>Often used in enterprise incident response, where evidence must be centralized securely.</li></ul><p><strong>Step 4: Execution</strong></p><p>Clicking <strong>Execute</strong> builds the equivalent command-line instruction and runs it. The console window shows live progress logs — every artifact collected, every parser run, every error encountered.</p><p>The result: a structured output directory containing both raw artifacts (from Targets) and parsed intelligence (from Modules).</p><h3>Operating with the CLI (kape.exe)</h3><p>While KAPE provides a GUI, its true power lies in the <strong>command line (kape.exe)</strong>. In live investigations, the CLI is faster, more flexible, and far easier to automate across multiple systems.</p><ol><li><strong>Basic Collection</strong></li></ol><p>The simplest way to run KAPE is to collect artifacts from a source drive into a destination folder:</p><pre>kape.exe --tsource C: --target KapeTriage --tdest D:\test</pre><ul><li>— tsource C: → Defines the source (usually the system drive).</li><li>— target KapeTriage → Runs the compound target KapeTriage, which includes a broad set of artifacts such as Prefetch, AmCache, Registry, and event logs.</li><li>— tdest D:\test → Saves all collected files into the specified folder.</li></ul><p>This command is ideal for fast triage collection during incident response.</p><p><strong>2. Collection and Processing Together</strong></p><p>KAPE becomes more powerful when <strong>Modules </strong>are added. Instead of just copying files, it can parse them immediately using forensic tools.</p><pre>kape.exe --tsource C: --target KapeTriage --tdest D:\test<br>         --mdest E:\KAPE-OUTPUT --module !EZParser</pre><ul><li>— mdest → Location where parsed results are stored.</li><li>— module !EZParser → Runs the compound module !EZParser, which automatically processes key artifacts with tools like PECmd, EvtxECmd, and AmCacheParser.</li></ul><p>In practice, the command gives both raw artifacts and structured CSV reports ready for review</p><p><strong>3. Advanced CLI Options</strong></p><p>When operating in the field, we often combine core commands with advanced flags for precision and efficiency:</p><ul><li><strong>Volume Shadow Copies ( — vss):</strong></li></ul><p>Collects historical and deleted artifacts. Useful in cases where attackers attempted to wipe traces.</p><pre>kape.exe --tsource C: --target KapeTriage --tdest D:\test --vss</pre><ul><li><strong>Packaging Results ( — zip / — vhdx):</strong></li></ul><p>Automatically compresses output into a single archive for transfer.</p><pre>kape.exe --tsource C: --target KapeTriage --tdest D:\test --zip</pre><p><strong>4. Batch Automation</strong></p><p>For repeatable investigations, KAPE supports batch execution with _kape.cli files. Create a text file in the same directory as kape.exe and define your preferred workflow:</p><pre>--tsource C: --target KapeTriage --tdest D:\test<br>--mdest E:\KAPE-OUTPUT --module !EZParser</pre><p>Then run:</p><pre>kape.exe</pre><p>KAPE automatically reads _kape.cli and executes the sequence.</p><p>This is especially useful in enterprise response, where the same triage process must be repeated across multiple endpoints.</p><h3>KAPE in the Investigation Workflow</h3><p>KAPE is not a standalone tool — it is part of a larger forensic workflow. The data it collects and parses is often just the beginning. Structured outputs like CSV and JSON can be imported into:</p><ul><li>Timeline Explorer for timeline reconstruction.</li><li>Excel or Power BI for pivoting and visualization.</li><li>SIEM platforms (Splunk, ELK) for cross-system correlation.</li><li>Other forensic tools for deep dives into specific artifacts.</li></ul><p>This integration makes KAPE an accelerator. It gives investigators early leads while traditional full imaging and deep analysis continue in parallel.</p><h3>Final Notes</h3><p>KAPE doesn’t replace full forensic analysis, but it gives investigators what they need most: <strong>speed and clarity</strong>. It bridges the gap between evidence collection and actionable leads, making it a go-to tool for DFIR.</p><p>In my next post, I’ll share how KAPE fits into wider <strong>incident response workflows</strong> and works alongside other forensic utilities.</p><h3>About DFIRHive</h3><blockquote>This guide is part of my broader project — <a href="https://www.dfirhive.com/"><strong>DFIRHive.com</strong> </a>— where I post <strong>digital forensics and incident response (DFIR)</strong> walkthroughs, memory analysis tutorials, investigation case studies, and hands-on tool guides.</blockquote><blockquote>If you found this useful, you’ll probably enjoy the rest of the content there too:<br> Visit<a href="https://www.dfirhive.com/"> DFIRHive.com</a> for more deep-dive blogs and technical analysis.</blockquote><p><em>Originally published → </em><a href="https://www.dfirhive.com/post/a-guide-to-kape-streamlining-windows-forensics"><em>Here</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d2dd4a03051" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>