ECCouncil 312-49v11 - Computer Hacking Forensic Investigator (CHFIv11)

According to the CHFI v11 syllabus under Malware Forensics and System Behavior Analysis , the Windows Registry is one of the most critical sources of forensic evidence when investigating malware activity. Malware frequently interacts with registry keys to achieve persistence , configure execution parameters, disable security controls, or maintain state information across reboots. By analyzing registry key modifications , forensic investigators can identify how malware embeds itself into the operating system and understand its long-term behavior.

Common persistence mechanisms include modifications to registry locations such as Run, RunOnce, Services, Winlogon, and scheduled task-related keys. Changes in these keys can reveal how and when malware is executed, whether it runs at system startup, and which privileges it attempts to obtain. CHFI v11 emphasizes monitoring registry artifacts using tools like Process Monitor, Registry Editor, and registry diff utilities to detect unauthorized additions, deletions, or value changes.

The other options are incorrect in this context. Monitoring network traffic patterns (Option A) is useful for command-and-control analysis but does not directly reveal registry-based persistence. Browser history logs (Option B) are related to user activity, not system-level malware behavior. Tracking system file executions (Option C) focuses on executable activity but does not expose configuration or persistence logic stored in the registry.

The CHFI Exam Blueprint v4 explicitly highlights registry-based malware persistence mechanisms as a key investigative focus, making analyzing registry key modifications the correct and exam-aligned answer

Option D is the best answer because the computer was seized while the Tor Browser was actively open , meaning the most valuable evidence may still exist in volatile memory . In CHFI methodology, when a live system contains potentially crucial active-session evidence, investigators should follow the order of volatility and collect the most easily lost evidence first. A memory dump may preserve active browser session data, in-memory artifacts, decrypted content, process information, network connections, and traces of recently accessed dark web activity that might never be written clearly to disk.

Shutting down or unplugging the machine would destroy this volatile evidence immediately. Restarting into safe mode would also alter or erase the active session context. Hard drive analysis remains important later, but it would not capture the full live state of the Tor session as effectively as RAM collection.

Because the goal is to obtain as much information as possible from the active session , the strongest CHFI-aligned answer is to leave the system running and collect a memory dump first before taking further acquisition steps.

The best answer is D because the scenario emphasizes matching observed behavior to known adversary tactics and infrastructure. The analysts are using intelligence feeds to recognize beaconing behavior, link it to command-and-control servers, and correlate the intrusion with known attack activity. That is more than just discovering generic indicators of compromise. It is the recognition and correlation of known attack patterns. CHFI v11 includes the role of threat intelligence in computer forensics, and one of its practical benefits is helping investigators relate local evidence to broader adversary tradecraft, campaigns, and infrastructure patterns. Option B is plausible, but it is narrower and does not capture the pattern-matching and campaign-level linkage described. Option A focuses on early identification, which is not the main point here, and option C is too broad. In forensic reasoning, when intelligence is used to connect beacons, tactics, and command infrastructure into a recognizable adversary pattern, the most accurate role is recognizing and correlating known attack patterns. That is the clearest fit for the investigative activity described in the question.

The correct answer is D because preservation is the EDRM stage focused on ensuring that potentially relevant electronically stored information remains intact and is not altered or destroyed once a legal duty to retain it arises. The scenario describes custodians being formally instructed to keep data and prevent deletion or modification, which is the classic preservation step in eDiscovery practice. Information governance is broader and deals with general data management policies before a specific matter arises. Processing and production occur later, after data has already been preserved and collected. CHFI v11 includes the eDiscovery process flow and the Electronic Discovery Reference Model cycle, so candidates are expected to connect legal hold style activities with the correct EDRM phase. In practical forensic and litigation support work, preservation is the stage that protects the evidence population from spoliation and ensures that later collection and review remain defensible. Because the question centers on retaining relevant ESI and freezing changes to it, preservation is the exact stage being applied.

According to the CHFI v11 objectives and the Electronic Discovery Reference Model (EDRM) framework, the activity described in this scenario corresponds to the Information Governance stage. Information governance is the foundational phase of the EDRM cycle and focuses on establishing policies, procedures, controls, and standards to manage electronic information throughout its lifecycle. This includes defining data retention schedules, access control policies, compliance requirements, preservation rules, and audit readiness.

In CHFI v11, information governance is emphasized as a proactive and strategic function that ensures an organization is prepared for future investigations, audits, litigation, or regulatory inquiries. By implementing governance controls after an investigation, organizations strengthen forensic readiness, reduce legal risk, and ensure that electronic data remains reliable, authentic, and admissible as evidence.

The other options do not accurately match the described activity. Disposal (Option A) refers to defensible deletion after legal hold requirements expire. Collection (Option C) involves acquiring data for analysis, while Identification (Option D) focuses on locating potentially relevant data sources. None of these address long-term policy creation or enterprise-wide data control.

The CHFI v11 Exam Blueprint explicitly includes Information Governance within the eDiscovery process, highlighting its role in compliance, risk mitigation, and evidence integrity management, making Option B the correct and exam-aligned answer

Option D. Security phase is the best answer because the scenario describes cryptographic verification , checking the bootloader integrity , and enforcing policies so that only trusted software is loaded. CHFI v11 includes the booting process and specifically covers the Windows boot process: BIOS-MBR method and UEFI-GPT , which means exam candidates are expected to understand the major phases and security controls associated with modern system startup.

In UEFI-based systems, the phase concerned with validating trust and enforcing secure boot behavior is the security phase . That phase is responsible for ensuring that firmware policy is applied before control is handed to later boot components. This aligns precisely with the description in the question, where the system is not merely selecting a boot device or initializing drivers, but actively verifying trust and compliance.

The other answers are less suitable. Boot device selection focuses on choosing the device to boot from. Pre-EFI initialization prepares early hardware and platform state. Driver execution environment deals more with loading drivers and services in the UEFI environment. Because the emphasis is on trusted boot and cryptographic validation , the correct answer is the security phase .

The correct answer is B because Google Transfer Appliance is specifically designed for large-scale offline data movement into Google Cloud when network bandwidth is limited or impractical. Google documents it as a high-capacity storage appliance that customers load on-premises and then securely ship to a Google upload facility, where the data is transferred into Cloud Storage. That matches the scenario exactly: the site is isolated, the bandwidth is constrained, and the volume is extremely large at 600 TB. In CHFI v11, cloud forensics includes understanding cloud platforms and evidence acquisition approaches, so recognizing the difference between online transfer services and offline shipping methods is important. Data Transfer Services generally rely on network-based transfers and are not the best choice when direct connectivity is a bottleneck. Cloud Storage for Firebase is unrelated to bulk evidence migration, and Backup and DR is intended for protection and recovery workflows rather than secure offline ingestion. When the exam scenario stresses secure shipment of very large datasets into Google Cloud without relying on available bandwidth, Transfer Appliance is the only option that cleanly fits the operational requirement.

Option A. ExifTool is the best answer because the task is specifically to analyze file metadata . CHFI v11 includes Metadata Investigation , Understanding EXIF data , and identifies categories of tools used to examine files and metadata during forensic analysis.

ExifTool is purpose-built for extracting and examining metadata from many file types, including images, documents, and other digital artifacts. That makes it especially appropriate when the primary investigative requirement is to inspect metadata fields such as creation time, modification details, embedded properties, author information, device information, and other hidden descriptive attributes.

The other tools are broader forensic platforms or imaging utilities. FTK Imager is primarily associated with evidence preview and imaging. OSForensics supports multiple investigative functions, but it is not the most targeted answer when the question asks specifically about metadata analysis. EnCase is also a broad forensic suite rather than the most direct metadata-focused tool in the options. Therefore, based on CHFI’s emphasis on metadata investigation and file-type analysis, ExifTool is the most precise and suitable choice for Mike’s stated need.

The correct answer is B because com.apple.recentitems.plist is the user-level preference artifact associated with recently used items and application-related recent activity in macOS. Community and forensic references identify this plist in the user’s Preferences directory as storing recent-items information that can support timeline reconstruction of user activity. This makes it the best fit when the investigator wants a user-specific plist that reflects application usage around a suspicious time window. Application Support is a directory rather than the specific plist artifact being asked for. com.apple.desktop.plist and com.apple.dock.plist may contain useful configuration or interface state, but they are not the most directly relevant source for recent-item style application usage. CHFI v11 includes macOS forensic data, log files, and directories, so candidates are expected to know where user-activity artifacts reside inside the home profile. Since the question explicitly points to ~/Library/Preferences and asks for the plist that records usage relevant to recent activity, com.apple.recentitems.plist is the most appropriate answer.

Option C is the correct answer because modern Windows Sticky Notes data is stored in a SQLite database named plum.sqlite within the application’s package-specific LocalState path under the user profile. CHFI v11 supports this type of analysis by explicitly including Windows and Linux forensics using Python , SQLite Database Extraction , Windows File Analysis , and examination of Windows artifacts as part of operating system forensics and Python-based digital forensics.

The question specifically mentions using Python to extract application data, which aligns neatly with CHFI’s objective of using Python in digital forensics and with analyzing application-stored databases. Since Sticky Notes persists user note content in a SQLite file rather than in System32, Program Files, or a generic Documents folder, the package-local path is the most accurate location.

The other options are not consistent with how modern Windows Store-style applications usually store their per-user state. Therefore, for CHFI-style Windows artifact analysis and SQLite extraction, the correct path is the user’s Packages...\LocalState\plum.sqlite location.