Welcome to the interactive digital forensics simulation. You will analyze a forensic image, evaluate the available evidence, and apply standardized investigative procedures to answer the CHFI examination question on Windows artifacts.

CHFI (312-49) Digital Forensics Simulation

Investigation Scenario

A digital-forensics investigation team in Portland, Oregon is examining a forensic image (E01 format) of a Windows 10 workstation. The system was seized from an employee suspected of corporate espionage and unauthorized data exfiltration.

The investigator needs to establish a timeline of files the suspect recently interacted with, specifically looking for evidence of proprietary schematics being opened or staged for exfiltration prior to the system being powered down. The analyst mounts the file system to parse user profile and system execution artifacts.

Evidence Collected (Forensic Image Analysis)

[ANALYSIS LOG - FORENSIC WORKSTATION 02] > Target Image: WIN10_DESKTOP_001.E01 > File System: NTFS > Artifact Paths Queued for Parsing: - C:\Users\JSmith\AppData\Roaming\Microsoft\Windows\Recent\ - C:\Windows\Prefetch\ - C:\Users\JSmith\AppData\Roaming\Microsoft\Windows\Recent\AutomaticDestinations\ - C:\Users\JSmith\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\ > Processing LNK files... [Completed] > Processing PF files... [Completed] > Processing Jump Lists... [Completed]

Question

During a digital-forensics investigation in Portland, Oregon, an analyst is searching for evidence of files that were recently accessed by a user on a Windows system. Which artifact should the analyst examine to find a list of recently opened files?

Forensic Hint: Think about Windows OS behavior. Does the system only track file access in one location? Consider what happens when you open a document (creates a LNK), launch a program to read it (creates a PF), and look at the taskbar icon for that program (updates Jump Lists).

Expert Analysis

MINI LESSON: Windows File Access Artifacts
  • Recent Items (.lnk): Created automatically by Windows when a user opens a file. Contains the target path, MAC times of the target file, volume serial number, and network share details if applicable.
  • Prefetch (.pf): Primarily used to speed up application load times. However, parsing a Prefetch file reveals the executable's path, run count, last run times, and a list of files/directories referenced by the executable during startup.
  • Jump Lists: Found in AutomaticDestinations and CustomDestinations. They provide a history of files accessed by specific applications (e.g., documents opened in Word, or files viewed in Notepad), heavily reliant on LNK streams embedded within them.

Ready to test your Forensic Investigation skills further?

Enhance your CHFI preparation with more scenario-based simulations.

Explore more CHFI simulations