Individual skill
analyzing-disk-images
Perform dead-disk forensics on an acquired disk image using The Sleuth Kit, Plaso, and bulk_extractor — verify integrity and mount read-only, map partitions, recover deleted files, build a file-system and super-timeline, carve unallocated space, mine registry hives and OS artifacts, and detect anti-forensics. Use when handed a .E01/.dd/.raw/.vmdk/.vhdx disk image or forensic acquisition to examine, recovering deleted files, building a file-system timeline, or carving artifacts from unallocated space.
secskills-defense/skills/analyzing-disk-images/SKILL.md
Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84
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 6, 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)
- 188
- Repository last updated
- Sep 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- security Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytesSKILL.mdcore · 18,320 bytes
Read excerpt
# Analyzing Disk Images
A disk image is a frozen crime scene, and the whole discipline is preserving
that. Work only from a verified, read-only copy, prove nothing changed with
hashes at every step, and remember that the deleted and the unallocated often
say more than the live file system — because that is exactly what someone tried
to remove.
## When to Use
- You have an acquired disk image (`.E01`, `.dd`/`.raw`, `.aff4`, `.vmdk`, `.vhdx`) to examine
- Recovering deleted files, or reconstructing what was on a wiped or reformatted volume
- Building a file-system timeline or a full super-timeline across the whole image
- Carving files and artifacts out of unallocated space, slack, and free clusters