CHFI (312-49) Digital Forensics Simulation

Master Windows Registry forensics. You will learn to identify exact registry artifacts used to trace removable media connections and establish hardware attribution during data exfiltration investigations.

Investigation Scenario

A biomedical research facility in San Diego, California, suspects a terminated employee of stealing proprietary formulation data. Network forensics confirmed no unauthorized outbound transmissions. However, physical access logs indicate the subject accessed their workstation off-hours prior to termination.

A forensic investigator arrives on-site and acquires a bit-stream physical image (E01) of the subject's Windows 10 workstation. The investigator hypothesizes that data was exfiltrated via removable media and begins analyzing the extracted registry hives to prove a USB mass storage device was connected to the system.

Evidence Collected

[+] EVIDENCE ACQUISITION RECORD
Image File: Workstation-042-Physical.E01
Verification: MD5: 9a3c2b1e... [MATCHED]

[+] EXTRACTED ARTIFACTS
\Windows\System32\config\SYSTEM
\Windows\System32\config\SOFTWARE
\Users\JDoe\NTUSER.DAT

[+] FORENSIC GOAL
Identify Vendor ID, Product ID, and Unique Serial Number of any attached removable storage media.

Question

In a digital-forensics investigation in San Diego, California, an analyst is searching for evidence of data exfiltration via a USB flash drive. Which Windows Registry key should the analyst examine to identify the USB devices that have been connected to the system?

Investigator's Hint: You are looking for the "ENUMeration" of hardware, specifically "USB STORage" devices. Which hive controls system-wide hardware configurations rather than user-specific software preferences?

Expert Analysis

1. What the Evidence Shows

To prove exfiltration, we must establish that a specific physical device was introduced to the environment. The SYSTEM registry hive acts as the authoritative record of hardware configuration. Locating the serial number maps the digital footprint directly to physical evidence (the suspect's flash drive).

2. Identify Forensic Stage

Examination and Analysis. The investigator has already collected the E01 image and extracted the hives. They are now actively examining the data structures to extract relevant artifacts and analyzing their meaning.

3. Why the Correct Answer is Correct

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USBSTOR is the Windows Plug and Play (PnP) subsystem's registry path for enumerating USB Mass Storage devices. When a USB drive is inserted, Windows creates a subkey here format as: Disk&Ven_[Vendor]&Prod_[Product]&Rev_[Revision]. Inside this subkey resides another key named with the device's Serial Number (or a generated instance ID if a unique serial isn't available, indicated by a leading &).

4. Why Others Are Wrong

5. Real-World Forensic Action

As an investigator, you would export the SYSTEM hive, load it into a tool like Registry Explorer or RegRipper, and extract the USBSTOR entries. You would then correlate the extracted Serial Number against the setupapi.dev.log to determine the exact timestamp of the first insertion, and check SYSTEM\CurrentControlSet\Enum\USB to find the timestamp of the last connection.

MINI LESSON: The USB Forensics Trifecta

Proving data exfiltration via USB requires connecting three dots:

  1. Hardware Proof: SYSTEM hive (USBSTOR) proves the physical device was attached.
  2. User Attribution: NTUSER.DAT (MountPoints2) proves which user account mounted the drive.
  3. File Interaction: Windows Shortcut (LNK) files and Jump Lists prove that specific files were opened/copied from or to that specific USB drive volume.

Ready for the next investigation?

Enhance your digital forensics skills with more scenario-based challenges.

Explore more CHFI simulations