CyberKit

MFT Record Slack

Also called MFT slack, FILE record slack.

Unused tail bytes inside a 1 KB MFT record that can retain old metadata.

What it is

Each NTFS MFT entry is a fixed 1 KB record, but the active attributes rarely fill it. The leftover space between the end of the in-use attributes and the record boundary is MFT record slack.

Why it matters

When a record is reused for a new file, prior attribute data and old filenames can remain in the slack, letting an examiner recover traces of a previously deleted file that occupied that same record number.

In practice

MFT record slack preserved a $FILE_NAME attribute from an earlier deleted executable that had reused the same record index.

What to look for

  • Old attribute data left at the end of reused MFT records.
  • Fragments of earlier file names or timestamps.
  • Leftover content in records for small resident files.

Common mistake

Assuming a reused record holds only the current file. Older bytes can remain past its end.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

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

  • Resident vs. Non-Resident Attributes: Whether a file's data lives inside its MFT record or out in disk clusters.
  • File Slack: Leftover space between a file's real end and its last allocated cluster.
  • Data Runs: Compact NTFS map of which clusters hold a non-resident file's content.

Sources