Partition Scheme (MBR / GPT)
Also called MBR, GPT, partition table.
Disk layout metadata defining where volumes begin, end, and what type they are.
What it is
The on-disk structures that describe how a drive is divided into volumes: the legacy Master Boot Record with its four-entry partition table at sector zero, and the newer GUID Partition Table with a header and array of partition entries plus backups.
Why it matters
Correctly reading the partition scheme is the first step in any disk exam, and tampering here (a deleted or altered partition entry, or data tucked into inter-partition gaps) can hide entire volumes or boot-level malware that a naive examiner would overlook.
In practice
A wiped MBR partition entry concealed a second NTFS volume that, once re-located, held the attacker's entire toolkit.
What to look for
- Partition table entries and the space between partitions.
- Hidden or deleted partitions.
- Mismatches between the table and the volume headers.
Common mistake
Imaging only a partition. You lose the table, gaps and any hidden volumes.
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
- Bit-for-Bit Imaging: An exact sector-level duplicate of storage media for examination.
- Slack-Space Hiding: Concealing data in slack, unused, or non-standard disk areas to evade detection.
- File Signatures: Header/footer byte patterns that identify a file's true type regardless of name.