Individual skill

analyzing-disk-image-with-autopsy

Perform comprehensive forensic analysis of disk images using Autopsy to recover files, examine artifacts, and build investigation timelines.

internal/tools/skills/data/digital-forensics/analyzing-disk-image-with-autopsy/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,313
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Analyzing Disk Image with Autopsy

## When to Use
- When you have a forensic disk image and need structured analysis of its contents
- During investigations requiring file recovery, keyword searching, and timeline analysis
- When non-technical stakeholders need visual reports from forensic evidence
- For examining file system metadata, deleted files, and embedded artifacts
- When building a comprehensive case from multiple disk images

## Detection Gaps & Validation

- **Coverage gaps in default ingest:** Autopsy only surfaces what its modules parse. Volume Shadow Copies, `$UsnJrnl`, `$LogFile`, and Recycle Bin `$I` records are not fully timelined unless you enable the relevant modules and add each VSS snapshot as a data source - a file "absent" from the live volume often survives in a shadow copy.
- **Unallocated/slack not searched by default:** keyword search and hash lookup skip unallocated space unless carving is enabled. Run `blkls` + `bulk_extractor`/PhotoRec over unallocated to recover artifacts the tree view never shows.
- **NSRL "Known" can hide evidence:** marking NSRL as Known filters files from view, so `mimikatz.exe` renamed to a system filename or a trojanized signed binary slips past. Validate with the Extension-Mismatch module and a YARA/content-hash check, not the filename.