CAP-2140 · Data Forensics I · Module 6

Working with Microsoft File Systems and the Windows Registry

Read disk layouts, examine file system and Windows artifacts, and use them to reconstruct activity.

Read the disk layout

Older systems estimated disk capacity from geometry by multiplying cylinders × heads × sectors per track × bytes per sector. On modern drives, use the reported number of addressable logical blocks multiplied by the logical block size. Logical block addresses (LBAs) start at 0. A block can be 512 or 4,096 bytes, so confirm the logical size before converting an LBA to a byte offset. A 512e drive, for example, exposes 512-byte logical blocks on 4,096-byte physical sectors.

Master Boot Record (MBR)
Stores partition entries in the first logical block. Entries have legacy CHS fields and LBA fields. Modern tools use the LBA start and sector count to map partitions.
GUID Partition Table (GPT)
Uses LBAs and stores primary and backup partition metadata. A protective MBR helps prevent older utilities from treating the disk as empty. Firmware boot requirements are separate from the ability of an operating system or forensic tool to read a GPT data disk.

Compare partition boundaries with the full image and inspect unexpected gaps or space beyond the last partition. A gap may reflect alignment or contain remnants of a previous layout. Use a forensic tool or read-only hex viewer on a working copy to check for signatures and structures before identifying a hidden or deleted partition.

UEFI specification · GUID Partition Table (PDF) · Microsoft · UEFI/GPT-based disk partitions

Examine FAT, NTFS, and unused space

FAT directory entries and cluster chains

FAT12 is associated with floppy disks and other small volumes. FAT16 was common on older DOS and Windows systems, where a 2 GiB limit was typical under common configurations. FAT32 supports larger volumes. The usable cluster counts depend on the FAT variant and its reserved values. FAT32 entries use 28 bits for cluster values. VFAT long filenames are stored in extra directory entries alongside a short 8.3 name.

A cluster contains one or more sectors. The FAT tracks the chain of clusters assigned to a file. In a deleted short-name directory entry, the first byte is marked 0xE5. The starting cluster and file size may remain, but freeing the allocation chain and later reusing clusters can make recovery incomplete, especially for fragmented files.

NTFS records, attributes, and streams

The Master File Table (MFT) records each file or directory as a set of attributes. These can store names, timestamps, and file contents. A small data attribute can be resident, with its contents in the MFT record. Available record space determines whether the data fits. A nonresident data attribute stores the contents outside the record and uses run information to locate them. Check for named alternate data streams that may contain relevant bytes alongside the default stream.

Unallocated space and slack

Unallocated clusters may contain remnants of deleted or moved data until they are overwritten or discarded. Recovery depends on allocation history, fragmentation, and device behavior. On SSDs, TRIM and controller behavior can make deleted blocks inaccessible. File slack is the unused portion of a file’s final allocated cluster. Older terminology separates RAM slack, between the end of the file and the end of its last sector, from drive slack, the rest of the cluster. Treat any recovered bytes as fragments until you can establish their source.

Microsoft · FAT specification (PDF) · Microsoft · Master File Table · Microsoft · File Streams · NIST · Digital Investigation Techniques

Account for compression, encryption, and ReFS

NTFS supports file and folder compression. Applying compression at the volume level can set compression on eligible files and directories. Older DOS and Windows disk-compression utilities could present a compressed volume backed by FAT. The compression came from the utility.

Encrypting File System (EFS) protects individual files on supported NTFS volumes. Decryption requires an authorized private key, such as the user’s key or an applicable recovery agent’s key. BitLocker protects volumes. Recovery can use an authorized protector such as a 48-digit recovery password or a recovery key file. Before using a third-party decryption tool, identify the product and version, check its behavior on test data, and preserve the original encrypted image.

Resilient File System (ReFS) is designed for scalability and data integrity. Support varies with Windows version, edition, and configuration. Confirm that your forensic tools can read the ReFS version and features present in the image.

Microsoft · EFS overview · Microsoft · BitLocker recovery overview · Microsoft · ReFS overview

Correlate Windows and browser artifacts

A hex viewer can reveal file signatures and other on-disk structures. Use it to check parser output or investigate a misleading extension. Confirm a suspected file type by examining additional structure where possible.

Microsoft · Registry Hives · Windows Forensic Artifacts · Recycle Bin records · Microsoft · Browser Forensics Guide (PDF)

Practice case

A downloaded file disappears. On a verified Windows disk image, a browser profile records a download of budget.xlsx to the user’s Downloads folder at 14:05 UTC. An MFT record lists a file of the same name and path. In that account’s Recycle Bin folder, a $I record shows the same original path and a deletion time of 14:22 UTC. A corresponding $R item is present.

How would you test whether these artifacts refer to the same file? What can you report about the timeline and who performed the actions?

Review a possible approach

Confirm the browser download status and target path, normalize timestamps, and pair the Recycle Bin entries by their generated names. Compare the recovered item’s size and contents with any available reference copy, using a SHA-256 hash if you have comparable bytes. The records support a download followed by recycling of an item at that path. The profile and SID identify account context. Identifying the person who performed the actions requires further corroboration.

Read and watch