$Bitmap (NTFS)
Also called cluster allocation bitmap.
NTFS map of which clusters are allocated; defines what counts as unallocated.
What it is
A metadata file ($Bitmap) in which each bit tracks whether a corresponding cluster on the volume is allocated or free. NTFS consults it to decide where to place new data.
Where it lives
$Bitmap, in the root directory of an NTFS volume
Why it matters
It is the authority on which clusters are free versus in use, so it defines the boundary of unallocated space that carving and deleted-file recovery target. Discrepancies between the bitmap and the MFT can indicate corruption or anti-forensic tampering.
In practice
Comparing $Bitmap against the MFT revealed clusters marked free that still held a deleted database, guiding a successful carve.
What to look for
- Clusters marked free that still hold data.
- Inconsistencies between the bitmap and the MFT.
- Signs of tampering where data hides in clusters marked allocated.
Common mistake
Treating free clusters as empty. Free only means the file system can reuse them.
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
- Unallocated Space: Disk areas not currently assigned to a file but often holding recoverable data.
- Data Runs: Compact NTFS map of which clusters hold a non-resident file's content.
- File Signatures: Header/footer byte patterns that identify a file's true type regardless of name.