CyberKit

Data Runs

Also called run list, cluster runs.

Compact NTFS map of which clusters hold a non-resident file's content.

What it is

The encoded list in an MFT record that describes where a non-resident attribute's data physically resides, expressed as a series of (length, offset) pairs pointing to runs of contiguous clusters on the volume.

Why it matters

Reconstructing a fragmented or partially overwritten file requires correctly decoding its data runs; a corrupted or attacker-truncated run list can hide or mislead about where evidence lives on disk.

In practice

Decoding the data runs let the examiner reassemble a fragmented archive whose clusters were scattered across the volume.

What to look for

  • Fragmented files spread across many runs.
  • Runs pointing at clusters now used by other files.
  • Sparse or compressed files with special run entries.

Common mistake

Carving a fragmented file in one piece. Data runs tell you where each fragment lives.

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

Sources