Individual skill

analyzing-slack-space-and-file-system-artifacts

Examine file system slack space, MFT entries, USN journal, and alternate data streams to recover hidden data and reconstruct file activity on NTFS volumes.

internal/tools/skills/data/digital-forensics/analyzing-slack-space-and-file-system-artifacts/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 9, 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,329
Repository last updated
Nov 9, 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 Slack Space and File System Artifacts

## When to Use
- When searching for hidden or residual data in file system slack space
- For analyzing NTFS Master File Table (MFT) entries for deleted file metadata
- When reconstructing file operations from the USN Change Journal
- For detecting Alternate Data Streams (ADS) used to hide data or malware
- During deep forensic analysis requiring examination beyond standard file recovery

## Detection Gaps & Validation

- **Most-missed artifacts:** beyond file slack, examine MFT record slack (prior-file remnants in the 1024-byte entry), resident `$DATA` of small deleted files, `$LogFile` transactions (which survive after the USN wraps), `$Bitmap` to test cluster reallocation, and non-Zone.Identifier ADS. `fls`/Explorer hide ADS - enumerate them explicitly and carve unallocated with `bulk_extractor`/`foremost`.
- **USN wrap and slack overwrite:** `$UsnJrnl:$J` is sparse and circular, so older events vanish on wrap - absence is not proof. Slack/unallocated is volatile too: any new write can overwrite the residual data, so a clean slack region does not mean nothing was hidden. Corroborate with `$LogFile` and Volume Shadow Copies.
- **Timestomping detection ($SI vs $FN):** `$STANDARD_INFORMATION` times are user-settable; `$FILE_NAME` times are kernel-only. Flag $SI predating $FN, identical/zeroed sub-second values, or $SI inconsistent with MFT entry-number ordering, then confirm against `$LogFile`/USN before calling it deliberate.
Back to top