Resident vs. Non-Resident Attributes
Also called resident data, non-resident data.
Whether a file's data lives inside its MFT record or out in disk clusters.
What it is
In NTFS, every file attribute is either resident (stored entirely inside the 1 KB MFT record) or non-resident (stored in external clusters referenced by data runs). Small files and short data streams stay resident; larger ones spill out.
Why it matters
It changes where evidence physically lives: resident content is recovered straight from the MFT even if its clusters are reallocated, while non-resident content requires following data runs and is subject to cluster overwrite. Knowing which applies guides recovery strategy.
In practice
A tiny dropped script was fully resident, so its source was recovered intact from the MFT record long after the file was deleted.
What to look for
- Small files whose content sits inside the MFT record.
- Resident data surviving after the file is deleted.
- Large files mapped through data runs instead.
Common mistake
Carving unallocated space for small files. Their content may be inside the MFT instead.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Windows Artifact Reader
Read a Prefetch file, a shortcut, a Recycle Bin $I file, or a carved MFT or USN record. It detects which one you dropped.
- Windows Host Case
An alert on a live Windows workstation: read the event logs and the Registry, rebuild the timeline, then decide what to collect.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Autopsy Open source
A graphical forensics platform that parses file systems and common artifacts. Our notes.
-
Eric Zimmerman's tools Free
Command line parsers for Windows artifacts such as the MFT, Prefetch and the Registry. Our notes.
-
Plaso Open source
Builds a super timeline from many artifacts in one image. Our notes.
-
Velociraptor Open source
Collects the same artifacts remotely, without pulling a full disk image. Our notes.
Read next
- MFT Record Slack: Unused tail bytes inside a 1 KB MFT record that can retain old metadata.
- Data Runs: Compact NTFS map of which clusters hold a non-resident file's content.
- File Slack: Leftover space between a file's real end and its last allocated cluster.