Skip to content

Disk Forensics Guide Autopsy and KAPE

github-actions[bot] edited this page Nov 19, 2026 · 2 revisions

๐ŸŽฏ Purpose

Disk forensics guide covering evidence acquisition practices, Autopsy (image and logical-source analysis), and KAPE (Kroll Artifact Parser and Extractor - targeted artifact collection and processing). KAPE collection is not a bit-for-bit disk image.

โš™๏ธ Function

Covers: write-protected or otherwise authorized disk-image acquisition, Autopsy case setup and analysis, KAPE targets/modules for artifact collection and processing, timeline analysis, file carving, hash verification, and reporting. Exact coverage depends on the evidence source, selected collection targets, and configured ingest modules.

๐Ÿ† Goal

Enable IR practitioners to acquire disk evidence correctly and efficiently analyze it with Autopsy or KAPE to identify attacker activity, persistence mechanisms, and data access during an incident.

๐Ÿ“‹ When to Use

  • Disk forensics during incident response (compromised workstation or server)
  • Rapid triage with KAPE before full Autopsy analysis
  • Evidence preservation and chain of custody documentation
  • Post-incident artifact collection for legal hold

Disk forensics involves the acquisition, analysis, and reporting of data stored on persistent storage media. This guide covers two essential tools: Autopsy (a full-featured forensic platform) and KAPE (Kroll Artifact Parser and Extractor - a rapid triage collection tool).

Together, these tools support targeted artifact triage and deeper image or logical-source analysis. They serve different roles: KAPE selects and processes artifacts; Autopsy analyzes supported evidence sources. Neither tool choice guarantees complete collection or recovery.


๐ŸŽฏ Autopsy vs KAPE: When to Use Each

Scenario Tool Reason
Disk-image or logical-source examination Autopsy Broad examination; coverage depends on source type and configured ingest modules
Rapid triage collection KAPE Fast artifact extraction
Timeline analysis Autopsy Built-in timeline features
Live artifact triage KAPE Selective collection; method and destinations affect target writes and evidence coverage
Malware investigation Both KAPE collects, Autopsy analyzes
Deleted-file analysis Autopsy Results depend on source image, unallocated data, file system, and selected ingest options
Registry analysis Both Autopsy has viewer, KAPE extracts
Browser forensics Both Both parse browser artifacts

Typical Workflow

Two evidence paths: image acquisition followed by Autopsy image analysis, and selective KAPE artifact collection followed by parsing or Autopsy logical-file analysis

Conceptual workflows. KAPE collects selected artifacts; it does not create a complete disk image. Live collection can change the source depending on how tools, temporary files, and destinations are configured.

Autopsy supports multiple source types, while its selected ingest modules determine which content is analyzed. Logical-file sources do not include unallocated space. See the Autopsy data-source documentation and ingest-module documentation.

Part A: KAPE (Kroll Artifact Parser and Extractor)

๐Ÿ“‹ KAPE Overview

KAPE is a triage tool designed to:

  • Collect forensic artifacts from live systems or mounted images
  • Process collected data using various parsers
  • Output results in analysis-ready formats

Key Concepts

Term Description
Target Defines what files/artifacts to collect
Module Defines how to process collected artifacts
TKAPE Target collection only
MKAPE Module processing only
Compound Target Multiple targets combined

๐Ÿ“ฅ KAPE Installation

Step 1: Download KAPE

KAPE is free for non-commercial use. Download from:

Step 2: Extract and Organize

# Extract to a dedicated folder
Expand-Archive -Path "kape.zip" -DestinationPath "C:\Tools\KAPE"

# Directory structure
# C:\Tools\KAPE\
# โ”œโ”€โ”€ kape.exe
# โ”œโ”€โ”€ Targets\
# โ”œโ”€โ”€ Modules\
# โ””โ”€โ”€ Documentation\

Step 3: Update Targets and Modules

KAPE uses community-maintained targets and modules:

# Clone KapeFiles repository for latest targets/modules
git clone https://github.com/EricZimmerman/KapeFiles.git

# Copy to KAPE directory
Copy-Item -Path "KapeFiles\Targets\*" -Destination "C:\Tools\KAPE\Targets" -Recurse -Force
Copy-Item -Path "KapeFiles\Modules\*" -Destination "C:\Tools\KAPE\Modules" -Recurse -Force

Step 4: Download Module Binaries

Many modules require external tools (Eric Zimmerman tools, etc.):

# Run KAPE's module binary sync
cd C:\Tools\KAPE
.\kape.exe --sync

Or manually download Eric Zimmerman tools:


๐ŸŽฏ KAPE Targets

Understanding Target Files

Targets are YAML files defining what to collect:

Description: Windows Event Logs
Author: Eric Zimmerman
Version: 1.0
Id: 12345678-1234-1234-1234-123456789abc
RecreateDirectories: true
Targets:
    -
        Name: Event Logs
        Category: EventLogs
        Path: C:\Windows\System32\winevt\Logs\
        FileMask: '*.evtx'
        Recursive: false

Essential Targets for IR

Target What It Collects
!SANS_Triage Comprehensive IR collection
KapeTriage General triage artifacts
EventLogs Windows Event Logs
Registry Registry hives
FileSystem $MFT, $J, $LogFile
Antivirus AV logs (Defender, etc.)
WebBrowsers All browser artifacts
CloudStorage OneDrive, Dropbox, etc.
RemoteAdmin RDP, TeamViewer, etc.
PowerShell PS history, logs
Prefetch Prefetch files
Amcache Amcache.hve
SRUM System Resource Usage
RecycleBin Deleted files info

View Available Targets

# List all targets
.\kape.exe --tlist

# Search for specific targets
.\kape.exe --tlist | Select-String "Registry"

๐Ÿ”ง KAPE Collection Examples

Caution

Account for collection side effects. Some live or remote KAPE workflows can write tool, temporary, or output files to the target, depending on the launch method and destination settings. Before collection, inspect the actual --tdest/--mdest plan and remote-collection procedure, record expected writes, and preserve an appropriate image first when unallocated space or a stable disk state matters. See the KAPE remote collection notes.

Basic Syntax

kape.exe --tsource <source> --tdest <destination> --target <target_name>

Example 1: Comprehensive Triage Collection

# Collect SANS triage artifacts from C: drive
.\kape.exe --tsource C: --tdest E:\Cases\Case001\Collection --target !SANS_Triage

# With volume shadow copy support
.\kape.exe --tsource C: --tdest E:\Cases\Case001\Collection --target !SANS_Triage --vss

Example 2: Event Logs Only

.\kape.exe --tsource C: --tdest E:\Cases\Case001\EventLogs --target EventLogs

Example 3: Registry Hives

.\kape.exe --tsource C: --tdest E:\Cases\Case001\Registry --target RegistryHives

Example 4: Browser Artifacts

.\kape.exe --tsource C: --tdest E:\Cases\Case001\Browsers --target WebBrowsers

Example 5: Multiple Targets

.\kape.exe --tsource C: --tdest E:\Cases\Case001\Collection --target EventLogs,RegistryHives,Prefetch,Amcache

Example 6: Collect from Mounted Image

# Mount forensic image as E:
# Then collect
.\kape.exe --tsource E: --tdest F:\Cases\Case001\Collection --target !SANS_Triage

Example 7: Include Volume Shadow Copies

.\kape.exe --tsource C: --tdest E:\Cases\Case001\Collection --target !SANS_Triage --vss --vhdx Case001_VSS

โš™๏ธ KAPE Modules

Understanding Modules

Modules process collected artifacts:

Description: Parse Windows Event Logs with EvtxECmd
Category: EventLogs
Author: Eric Zimmerman
Version: 1.0
Id: 87654321-4321-4321-4321-cba987654321
BinaryUrl: https://ericzimmerman.github.io/#!index.md
ExportFormat: csv
Processors:
    -
        Executable: EvtxECmd\EvtxECmd.exe
        CommandLine: -d %sourceDirectory% --csv %destinationDirectory%
        ExportFormat: csv

Essential Modules for IR

Module What It Processes
!EZParser Run all EZ tools on artifacts
EvtxECmd Parse Event Logs to CSV
RECmd Parse Registry hives
PECmd Parse Prefetch files
LECmd Parse LNK files
JLECmd Parse Jump Lists
SBECmd Parse ShellBags
MFTECmd Parse $MFT
AmcacheParser Parse Amcache
AppCompatCacheParser Parse Shimcache
SrumECmd Parse SRUM database
SQLECmd Parse SQLite databases

View Available Modules

# List all modules
.\kape.exe --mlist

# Search for specific modules
.\kape.exe --mlist | Select-String "Registry"

๐Ÿ”„ KAPE Processing Examples

Basic Module Syntax

kape.exe --msource <source> --mdest <destination> --module <module_name>

Example 1: Process All with EZParser

.\kape.exe --msource E:\Cases\Case001\Collection --mdest E:\Cases\Case001\Parsed --module !EZParser

Example 2: Parse Event Logs

.\kape.exe --msource E:\Cases\Case001\Collection --mdest E:\Cases\Case001\Parsed --module EvtxECmd

Example 3: Parse Registry

.\kape.exe --msource E:\Cases\Case001\Collection --mdest E:\Cases\Case001\Parsed --module RECmd_AllRegExecutablesFoundOrRun

Example 4: Full Collection + Processing

# Collect AND process in one command
.\kape.exe --tsource C: --tdest E:\Cases\Case001\Collection --target !SANS_Triage --mdest E:\Cases\Case001\Parsed --module !EZParser

๐Ÿ“Š KAPE Output Structure

After running KAPE, output is organized:

E:\Cases\Case001\
โ”œโ”€โ”€ Collection\                    # Raw collected artifacts
โ”‚   โ”œโ”€โ”€ C\                         # Source drive letter
โ”‚   โ”‚   โ”œโ”€โ”€ Windows\
โ”‚   โ”‚   โ”‚   โ”œโ”€โ”€ System32\
โ”‚   โ”‚   โ”‚   โ”‚   โ”œโ”€โ”€ config\        # Registry hives
โ”‚   โ”‚   โ”‚   โ”‚   โ””โ”€โ”€ winevt\Logs\   # Event logs
โ”‚   โ”‚   โ”‚   โ””โ”€โ”€ Prefetch\
โ”‚   โ”‚   โ””โ”€โ”€ Users\
โ”‚   โ”‚       โ””โ”€โ”€ <username>\
โ”‚   โ””โ”€โ”€ vss\                       # Volume Shadow Copies
โ”‚       โ”œโ”€โ”€ vss1\
โ”‚       โ””โ”€โ”€ vss2\
โ”‚
โ””โ”€โ”€ Parsed\                        # Processed output
    โ”œโ”€โ”€ EventLogs\                 # CSV event logs
    โ”œโ”€โ”€ Registry\                  # Registry output
    โ”œโ”€โ”€ FileSystem\                # $MFT, etc.
    โ””โ”€โ”€ ProgramExecution\          # Prefetch, Amcache

๐Ÿ–ฅ๏ธ KAPE GUI (gkape)

KAPE includes a GUI for easier use:

# Launch GUI
.\gkape.exe

GUI Features

  1. Target Selection: Browse and select targets visually
  2. Module Selection: Browse and select modules
  3. Options: VSS, VHDX creation, flush settings
  4. Command Preview: See the command before running

Part B: Autopsy

๐Ÿ“‹ Autopsy Overview

Autopsy is an open-source digital forensics platform that provides:

  • Disk image analysis
  • File system forensics
  • Keyword searching
  • Timeline analysis
  • Hash filtering
  • Reporting

๐Ÿ“ฅ Autopsy Installation

Step 1: Download Autopsy

Download from sleuthkit.org/autopsy

Step 2: Install

Run the installer with default settings. Autopsy includes:

  • The Sleuth Kit (forensic tools)
  • Java Runtime (bundled)
  • Various analysis modules

Step 3: Configure Memory (Optional)

For large cases, increase Java heap:

  1. Navigate to Autopsy installation directory
  2. Edit etc\autopsy.conf
  3. Modify: default_options="-J-Xms4g -J-Xmx16g"

๐Ÿ†• Creating a New Case

Step 1: Start Autopsy

Launch Autopsy and select Create New Case

Step 2: Case Information

Field Example
Case Name IR-2024-001
Base Directory E:\Cases\
Case Type Single-user

Step 3: Optional Information

Field Example
Case Number IR-2024-001
Examiner John Smith
Organization PNWC

๐Ÿ“€ Adding Data Sources

Supported Data Sources

Type Description
Disk Image E01, raw (dd), VHD, VMDK
Local Disk Physical drive
Logical Files Folder of files (like KAPE output)
Unallocated Space Raw unallocated space image
XRY Text Export Mobile device export

Add Disk Image

  1. Select Data Source Type: Disk Image or VM File
  2. Browse to image file (E01, raw, etc.)
  3. Configure Time Zone (important for timeline accuracy)
  4. Select Ingest Modules (see below)

Add KAPE Collection (Logical Files)

  1. Select Data Source Type: Logical Files
  2. Browse to KAPE collection folder
  3. This allows Autopsy to analyze KAPE-collected artifacts

๐Ÿ”Œ Ingest Modules

Ingest modules automatically analyze data as it's added.

Essential Modules for IR

Module Purpose Enable?
Recent Activity Browser, registry, recent docs โœ…
Hash Lookup Compare against known hash sets โœ…
File Type Identification Identify by signature, not extension โœ…
Extension Mismatch Find disguised files โœ…
Embedded File Extractor Extract from archives/docs โœ…
Keyword Search Index for searching โœ…
Email Parser Parse email files โœ…
Encryption Detection Find encrypted files โœ…
Interesting Files Flag suspicious files โœ…
PhotoRec Carver Recover deleted files Optional
Virtual Machine Extractor Extract VM disk images Optional
Data Source Integrity Verify image hash โœ…

Configure Hash Sets

  1. Tools โ†’ Options โ†’ Hash Sets
  2. Add NSRL (known good) hash set
  3. Add known malware hash sets

Hash Set Sources:

Configure Keyword Lists

  1. Tools โ†’ Options โ†’ Keyword Lists
  2. Add custom lists for:
    • IP addresses
    • Domain names
    • Email addresses
    • Malware indicators
    • Sensitive data patterns

๐Ÿ—‚๏ธ Navigating Autopsy

Main Interface Areas

Area Purpose
Tree View (Left) Navigate data sources, results
Result Viewer (Top Right) List of files/items
Content Viewer (Bottom Right) View selected item

Tree View Sections

Data Sources
โ”œโ”€โ”€ [Disk Image Name]
โ”‚   โ”œโ”€โ”€ File Views
โ”‚   โ”‚   โ”œโ”€โ”€ File Types (by extension)
โ”‚   โ”‚   โ”œโ”€โ”€ Deleted Files
โ”‚   โ”‚   โ””โ”€โ”€ File Size
โ”‚   โ””โ”€โ”€ Data Artifacts
โ”‚       โ”œโ”€โ”€ Web History
โ”‚       โ”œโ”€โ”€ Web Downloads
โ”‚       โ”œโ”€โ”€ Recent Documents
โ”‚       โ””โ”€โ”€ Installed Programs
โ”‚
โ”œโ”€โ”€ Views
โ”‚   โ”œโ”€โ”€ File Types
โ”‚   โ””โ”€โ”€ Deleted Files
โ”‚
โ”œโ”€โ”€ Results
โ”‚   โ”œโ”€โ”€ Extracted Content
โ”‚   โ”‚   โ”œโ”€โ”€ Web History
โ”‚   โ”‚   โ”œโ”€โ”€ Web Bookmarks
โ”‚   โ”‚   โ”œโ”€โ”€ Web Cookies
โ”‚   โ”‚   โ”œโ”€โ”€ Web Downloads
โ”‚   โ”‚   โ””โ”€โ”€ Recent Documents
โ”‚   โ”œโ”€โ”€ Keyword Hits
โ”‚   โ”œโ”€โ”€ Hashset Hits
โ”‚   โ”œโ”€โ”€ Email Messages
โ”‚   โ””โ”€โ”€ Interesting Items
โ”‚
โ””โ”€โ”€ Tags
    โ”œโ”€โ”€ Follow Up
    โ”œโ”€โ”€ Notable Item
    โ””โ”€โ”€ [Custom Tags]

๐Ÿ” Analysis Techniques

File System Analysis

View All Files:

  1. Expand Data Sources โ†’ [Image] โ†’ File Views
  2. Browse by file type, size, or path

Find Deleted Files:

  1. Navigate to File Views โ†’ Deleted Files
  2. Or use Views โ†’ Deleted Files

File Metadata:

  1. Select a file
  2. View File Metadata tab in Content Viewer
  3. Check: Created, Modified, Accessed, Changed times

Keyword Searching

Create Search:

  1. Click Keyword Search (magnifying glass icon)
  2. Enter search term or regex
  3. Select Exact Match, Substring, or Regex
  4. Click Search

Useful Keywords for IR:

  • password, credential, secret
  • base64, powershell -enc
  • mimikatz, procdump, psexec
  • IP addresses: \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}
  • Email: [a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}

Timeline Analysis

Generate Timeline:

  1. Tools โ†’ Timeline
  2. Select time range
  3. Choose event types to include

Timeline Features:

  • Filter by file type, path, event type
  • Zoom to specific time periods
  • Export events for external analysis

What to Look For:

  • Cluster of activity around suspected compromise time
  • File creations in unusual locations
  • Execution artifacts (prefetch) timing
  • Gaps in activity (potential log clearing)

Web Artifact Analysis

Browser History:

  1. Results โ†’ Extracted Content โ†’ Web History
  2. Review URLs, visit times, visit counts

Downloads:

  1. Results โ†’ Extracted Content โ†’ Web Downloads
  2. Look for suspicious downloads

Cookies:

  1. Results โ†’ Extracted Content โ†’ Web Cookies
  2. Identify sites visited, session information

Registry Analysis

View Registry:

  1. Data Artifacts โ†’ Operating System Information
  2. Or navigate to registry files in file system
  3. Use Application โ†’ Registry Viewer in Content Viewer

Key Registry Locations:

Location Information
SAM User accounts
SECURITY Security settings
SOFTWARE Installed software, settings
SYSTEM System configuration, services
NTUSER.DAT User-specific settings
UsrClass.dat User shell settings

Hash Analysis

View Hash Hits:

  1. Results โ†’ Hashset Hits
  2. Review files matching known bad hashes

Calculate Hash:

  1. Right-click file โ†’ View File in Directory
  2. Check MD5/SHA1/SHA256 in File Metadata

Search VirusTotal:

  1. Right-click file โ†’ Search Online
  2. Opens VirusTotal search for hash

๐Ÿท๏ธ Tagging and Bookmarking

Create Tags

  1. Right-click item โ†’ Add Tag
  2. Select existing tag or create new
  3. Common tags:
    • Follow Up - Needs more investigation
    • Notable Item - Important finding
    • Malware - Confirmed malicious
    • Exfiltration - Data theft indicator
    • Persistence - Persistence mechanism

Add Comments

  1. Right-click item โ†’ Add Comment
  2. Enter notes about the item
  3. Comments appear in reports

๐Ÿ“Š Reporting

Generate Report

  1. Tools โ†’ Generate Report
  2. Select report type:
    • HTML Report - Best for sharing
    • Excel Report - For data analysis
    • KML Report - For geolocation data
    • Portable Case - Share case with another analyst

Report Options

Option Description
Tagged Results Only tagged items
All Results Everything found
Specific Data Types Select what to include

Export Artifacts

Export Files:

  1. Right-click file โ†’ Extract File(s)
  2. Choose destination

Export Timeline:

  1. Tools โ†’ Timeline
  2. File โ†’ Export โ†’ CSV

๐Ÿ”ฌ Advanced Autopsy Features

Data Source Processors

Add Custom Ingest Module:

  1. Tools โ†’ Options โ†’ Ingest
  2. Modules can be added via plugins

Python Plugins

Autopsy supports Python plugins for custom analysis:

# Example: Custom file analyzer
from org.sleuthkit.autopsy.ingest import IngestModule

class CustomAnalyzer(IngestModule):
    def process(self, file):
        # Custom analysis logic
        pass

Central Repository

For multi-case correlation:

  1. Tools โ†’ Options โ†’ Central Repository
  2. Enable and configure database
  3. Correlates artifacts across cases

Communication Visualization

  1. Tools โ†’ Communications
  2. Visualize email, call, message relationships
  3. Useful for understanding connections

๐Ÿ“š Common Investigation Workflows

Workflow 1: Malware Investigation

1. Create case, add disk image
2. Enable ingest modules (especially hash lookup, interesting files)
3. Check Results โ†’ Hashset Hits for known malware
4. Search keywords: malware names, C2 domains
5. Review Extracted Content โ†’ Web Downloads
6. Check File Views โ†’ Deleted Files for removed malware
7. Timeline analysis around infection time
8. Export malicious files for further analysis

Workflow 2: Data Theft Investigation

1. Create case, add disk image
2. Enable Recent Activity module
3. Review Web History and Downloads
4. Search keywords: competitor names, project names
5. Check for cloud storage usage (OneDrive, Dropbox)
6. Review USB device history (registry)
7. Check email artifacts
8. Timeline analysis for data access patterns

Workflow 3: KAPE + Autopsy Combined

1. Collect artifacts with KAPE (!SANS_Triage)
2. Process with KAPE modules (!EZParser)
3. Create Autopsy case
4. Add KAPE collection as Logical Files data source
5. Run relevant ingest modules
6. Cross-reference KAPE CSV output with Autopsy findings
7. Generate comprehensive report

โ— Troubleshooting

Autopsy Won't Start

# Check Java version
java -version

# Clear cache (Windows)
Remove-Item -Recurse "$env:USERPROFILE\.autopsy"

Slow Performance

  1. Increase Java heap in autopsy.conf
  2. Disable unnecessary ingest modules
  3. Use SSD for case storage
  4. Process large images overnight

Image Won't Load

  1. Verify image integrity (hash)
  2. Try different image format
  3. Check disk space
  4. Mount image externally and add as logical files

Missing Artifacts

  1. Verify ingest modules completed (check progress)
  2. Re-run specific ingest modules
  3. Check if artifact type is supported
  4. Manual navigation to known locations

๐Ÿ“š Additional Resources

Documentation

Training

Tools


๐Ÿ—‚๏ธ Quick Reference

KAPE Commands

Command Purpose
kape.exe --tlist List targets
kape.exe --mlist List modules
kape.exe --sync Download module binaries
kape.exe --tsource C: --tdest E:\Out --target !SANS_Triage Collect triage
kape.exe --msource E:\Out --mdest E:\Parsed --module !EZParser Process artifacts

KAPE Essential Targets

Target Description
!SANS_Triage Comprehensive collection
!BasicCollection Minimal triage
EventLogs Windows Event Logs
RegistryHives Registry files
WebBrowsers All browsers
FileSystem $MFT, $J, etc.

Autopsy Keyboard Shortcuts

Shortcut Action
Ctrl+F Find in current view
Ctrl+Shift+F Keyword search
Ctrl+T Add tag
Ctrl+G Generate report

Key File Locations (Windows)

Artifact Path
Event Logs C:\Windows\System32\winevt\Logs\
Registry (System) C:\Windows\System32\config\
Registry (User) C:\Users\<user>\NTUSER.DAT
Prefetch C:\Windows\Prefetch\
Amcache C:\Windows\AppCompat\Programs\Amcache.hve
SRUM C:\Windows\System32\sru\SRUDB.dat
Browser (Chrome) C:\Users\<user>\AppData\Local\Google\Chrome\User Data\
Recent Files C:\Users\<user>\AppData\Roaming\Microsoft\Windows\Recent\

Part of the Incident Response & Log Aggregation Branch

Adjacent PNWC recovery workflow โ€” separate from forensics

PNWC Fix-DriveAccess helps technicians assess and rescue customer data from Windows volumes with orphaned file-owner SIDs and inaccessible ACLs. Its read-only assessment and copy-to-another-volume approach are useful for a consented repair/recovery job, but this is not forensic acquisition: ownership/permission repair writes metadata to the source and can alter evidence. For investigations, acquire and verify a protected image before applying any ACL changes, follow chain-of-custody procedures and never mistake NTFS permissions for BitLocker decryption.

Related Files


Section Index | Master Index | Legal Notice


๐Ÿ“„ Source: IncidentResponse/Digital-Forensics/Disks/autopsy_kape.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to Incident Response

Clone this wiki locally