CCFH-202b Questions and Answers

In Detection Analysis , the process w3wp.exe is a critical focal point as it is the IIS (Internet Information Services) Worker Process. Under normal operating conditions, w3wp.exe should be handling web requests and should almost never spawn interactive shells like powershell.exe or cmd.exe. When a process tree shows a web worker process spawning a shell, it is a high-confidence Indicator of Attack (IOA) typically associated with a Web Shell or a successful exploitation of a web application vulnerability.

The subsequent commands—whoami.exe and net1.exe—are classic post-exploitation Reconnaissance tools. whoami is used by an attacker to determine the privileges of the service account they have compromised, while net1 is used to enumerate local or domain users and groups to identify potential targets for lateral movement. The progression from a web process to a shell and then to identity/network discovery is a definitive behavioral pattern of a remote attacker establishing a foothold and performing initial situational awareness. While an administrator might use these tools for troubleshooting (Option B), they would typically do so via a direct login or a remote management session, not through the w3wp.exe parent tree. Recognizing this specific lineage is essential for hunters to differentiate between legitimate administrative maintenance and an active, live-site compromise requiring immediate intervention and containment.

Comprehensive and Detailed 150 to 250 words of Explanation From Falcon Hunter Topics documents:

The best answer is B because it reflects the normal Falcon Investigate workflow: first review the domain’s reputation and associated network connection history to determine whether the observed activity is suspicious or malicious before taking containment actions. CrowdStrike’s official Falcon Hunter training material states that analysts should know how to perform a Bulk Domain search and understand the information it provides as part of proactive investigations , which supports using the dashboard to validate and analyze the domain activity before escalating to blocking or broader scoping actions.

Option A is not the strongest immediate next step because placing a firewall block before validating the domain’s reputation and reviewing the observed history can interrupt legitimate activity and move too quickly into response before investigation is complete. Option C can be a useful follow-up step after initial triage, especially if the domain appears suspicious and you want to understand broader host exposure, but it is secondary to first examining the reputation and connection history already surfaced through the Bulk Domain Investigate workflow. Based on CrowdStrike’s investigative approach, B is the most defensible and methodical answer because it uses the available domain-focused telemetry first and supports evidence-based decision-making.

The Bulk domains (often listed as Bulk Domain Investigate ) dashboard is a specialized tool within the Falcon platform designed for broad infrastructure pivoting. While a standard search might show you a single event, the Bulk Domain Investigate tool allows an analyst to enter one or more domain names to receive a comprehensive, global overview of all activity associated with those domains across the entire managed environment.

When an analyst inputs a suspicious domain into this dashboard, Falcon retrieves a list of every host that has attempted to resolve that domain and, crucially, the specific processes responsible for those DNS lookups or network connections. This provides the hunter with immediate visibility into the "Who" and the "How." For example, it might reveal that while the domain was initially seen on one host, it was actually looked up by powershell.exe on three other hosts that had not yet triggered an alert. This capability is essential for Hunting Methodology , as it allows for the rapid identification of a shared command-and-control (C2) infrastructure. By identifying all processes interacting with the domain, the hunter can determine if the threat is an isolated incident or part of a wider campaign, enabling them to transition quickly from identification to large-scale containment and remediation.

The Falcon platform includes several pre-configured, "built-in" hunting reports designed to surface common adversary techniques without requiring the analyst to write complex queries from scratch. The report Executables running from Recycle Bin is a specialized tool within the Reports and References section that specifically monitors for process execution events where the file path originates from the $Recycle.Bin directory.

From a Hunting Methodology perspective, the Recycle Bin is a frequent "hidden in plain sight" staging area for attackers. Adversaries may move malicious binaries there because it is a directory that standard users and some legacy security tools rarely inspect. Finding a process like explorer.exe or svchost.exe (or a randomly named .exe) launching from this path is a high-confidence indicator of malicious intent, often associated with persistence or manual execution by an intruder. While "Command Line and ASEP Activity" reports on Auto-Start Extension Points, and "Indicator Activity" tracks known bad hashes, the "Executables running from Recycle Bin" report focuses on the anomalous behavioral context of the file location. Utilizing these built-in reports allows a hunter to quickly identify "low-hanging fruit" and prioritize investigations on hosts where these specific, highly suspicious environmental anomalies are detected.

==========

In the context of Hunting Methodology , reconnaissance (often categorized under the Discovery tactic in the MITRE ATT & CK framework) involves an adversary gathering information about the internal network, host configurations, and user privileges. The query in Option D is specifically designed to hunt for this behavior by monitoring the execution of "Living off the Land" (LotL) binaries.

These built-in Windows utilities, while legitimate for administrative use, are the primary tools used by attackers to "get the lay of the land." Commands like whoami are used for System Owner/User Discovery (T1033), ipconfig and netstat for System Network Configuration Discovery (T1016), and tasklist for Process Discovery (T1057). By filtering for these specific filenames—net, ipconfig, whoami, quser, ping, netstat, tasklist, hostname, and at—on a specific host (aid), a hunter can identify a burst of discovery activity. While individual executions might be common, a series of these commands run in rapid succession by a non-administrative user is a high-confidence indicator of a compromise. This proactive search allows analysts to catch an adversary in the early stages of an attack, before they have successfully identified their next target for lateral movement or privilege escalation.

This command is a textbook example of a multi-stage, fileless attack using "Living off the Land" (LotL) techniques. In Detection Analysis , the presence of WmiPrvSE.exe (WMI Provider Host) as the parent process is a significant indicator of Lateral Movement (T1021.006), suggesting the command was triggered remotely via WMI. The command-line arguments use Net.WebClient to perform a "DownloadString" operation, which pulls the Invoke-Shellcode.ps1 script directly from a GitHub repository into memory without ever writing the file to disk.

The IEX (Invoke-Expression) cmdlet then executes that script in memory. The final part of the string, Invoke-Shellcode -Payload windows/meterpreter/reverse_http, specifically instructs the script to deploy a Meterpreter payload—a common component of the Metasploit Framework. This payload is configured to establish a reverse shell back to the attacker-controlled IP address (172.17.0.21) on port 8080. The use of -Windowstyle Hidden and -noprofile ensures the activity is invisible to the end-user and bypasses local profile configurations. For a Falcon Hunter, this represents a critical, high-severity detection. The investigation must focus on how the attacker gained the credentials necessary to trigger WMI and identifying which other hosts in the environment have had similar "DownloadString" events associated with the same internal IP.

In the context of the MITRE ATT & CK Framework , the creation of a scheduled task is a quintessential technique within the Persistence tactic (specifically T1053). Persistence consists of techniques that adversaries use to keep access to systems across restarts, changed credentials, and other interruptions that could cut off their flow. By scheduling a task to execute a remote management application, the attacker ensures that their connection to the compromised host is maintained automatically without requiring manual re-exploitation.

Within the Falcon platform, hunters monitor for this behavior by analyzing events such as ScheduledTaskRegistered or process executions originating from taskeng.exe or schtasks.exe. While scheduled tasks can occasionally be used for Privilege Escalation (if the task runs with SYSTEM privileges) or Execution , the primary goal of creating a permanent task for a management application is to ensure long-term, stable access to the environment. Effective hunting methodology involves pivoting from the detection of a new scheduled task to identifying the source process that created it. This allows the analyst to determine if the task was part of a legitimate administrative action or an unauthorized persistence mechanism designed to facilitate further malicious activity, such as data exfiltration or internal reconnaissance.

==========

In the context of Detection Analysis , identifying the "root cause" or the source of an infection requires tracing the process lineage back to the point of entry. In the provided execution chain—Unknown Process - > chrome.exe - > wscript.exe - > powershell.exe—each node represents a stage of the attack. While powershell.exe is the execution engine for the malicious script and wscript.exe is the intermediate handler (likely executing a downloaded .vbs or .js file), chrome.exe represents the ingress point.

By investigating chrome.exe , an analyst can uncover critical forensic artifacts such as the specific URL the user visited, the domain from which the malicious file was downloaded, or a potentially compromised website that initiated a drive-by download. In the Falcon platform, looking at the ParentProcessId and the CommandLine of chrome.exe (or using the Bulk Domain Investigate tool for associated network connections) provides the "Who" and "How" of the initial access. Although the "Unknown Process" sits at the top of the tree—typically representing a process that started before the Falcon sensor—the activity relevant to the script's delivery is contained within the Chrome session. Mastering this "parent-ancestor" relationship is fundamental to effective hunting, as it allows responders to move beyond simple remediation of the script execution and address the underlying delivery mechanism to prevent future re-infection.

==========

When conducting an Event Search using the CrowdStrike Query Language (CQL) , precision in naming event types is paramount. The Falcon sensor records the creation and modification of scheduled tasks under the specific event name ScheduledTaskRegistered . This event is highly valuable for hunters investigating Persistence (MITRE T1053), as it captures the specific details of the task, including the command to be executed, the frequency of the trigger, and the identity of the user who created it.

Option B is the correct query because it directly targets the administrative action of task registration and filters the results by the UserName field to isolate actions taken by "Doris." Option A is incorrect as it looks for files with a specific extension, and Option C focuses on the Task Manager GUI process (taskmgr.exe), which is not the process responsible for the actual background registration of tasks (that is typically handled by svchost.exe or schtasks.exe). Option D uses a non-existent event name. By using the ScheduledTaskRegistered event, a hunter can immediately see if an account—potentially a compromised one—is being used to establish a long-term foothold in the environment. This search is a core component of a "Persistence Hunt," where the goal is to find unauthorized automation that allows an attacker's code to survive system reboots and credential rotations.

The Falcon platform includes a dedicated category of built-in dashboards and visualizations known as Hunt reports . These reports are specifically engineered to surface high-confidence behavioral anomalies that do not necessarily trigger a standard malware detection but are statistically or contextually suspicious. They serve as a "proactive starting point" for analysts within the Reports and References section of the console.

Examples of Hunt reports include dashboards that identify executables running from the Recycle Bin, unusual parent-child process relationships (like cmd.exe spawned from sqlservr.exe), or suspicious usage of dual-use tools like psexec.exe or wmic.exe. Unlike standard "Detection Activity" reports, which show what the sensor has already caught, Hunt reports are designed to help the analyst find the "undiscovered" threats. Utilizing these reports is a core part of an advanced Hunting Methodology , allowing a team to move from reactive response to proactive threat discovery. By regularly reviewing these reports, a hunter can identify low-frequency, high-impact events that might represent an advanced adversary's initial reconnaissance or persistence efforts that have managed to stay below the threshold of an automated alert.

Identifying an enterprise-wide file infection requires a hunter to look past simple file names, which adversaries often randomize or mask to evade basic detection. The most effective Hunting Methodology for this scenario is to focus on the file's unique cryptographic hash (MD5, SHA256). Even if an attacker renames a malicious binary (e.g., from malware.exe to svchost.exe) to blend into different environments, the hash remains identical.

By utilizing CrowdStrike Query Language (CQL) in the Event Search or LogScale environments, a hunter can search for a known malicious hash across all ProcessRollup2 and ImageHash events. This allows the analyst to see every instance where that specific file has appeared, regardless of the local file name or path. This technique is particularly powerful for identifying "Polymorphic" behavior where the filename changes but the core payload stays the same. While monitoring alerts (Option A) is reactive and host dashboards (Option B) are localized, hash-based hunting provides a global, enterprise-wide perspective. This ensures that the hunter can identify every single "infected" host, including those where the malware may be dormant or where a local detection has not yet been triggered, enabling a comprehensive and simultaneous remediation effort across the entire organization.

In the event of a widespread ransomware outbreak, the primary objective of the Hunting Methodology shifts toward identifying "Patient Zero"—the first system compromised in the environment. While reverse engineering (Option D) and vulnerability management (Option C) provide long-term value, they do not offer the immediate forensic clarity needed to stop an active spread or identify the entry point. By utilizing Advanced Event Search to create a chronological timeline of file encryption events (typically identified by high-frequency fswrite operations or specific ransom note creation), a hunter can pinpoint the exact timestamp and host where the activity originated.

This process involves searching for the earliest instances of the ransomware's execution or the first signs of large-scale file modifications across the entire fleet. Once the first system is identified, the analyst can then pivot to look for the activity that occurred prior to the encryption, such as a suspicious email attachment execution, a web-based exploit, or a compromised RDP session. This "backwards-looking" investigation is essential for determining the initial delivery mechanism. Identifying the source host allows the security team to isolate the breach at its root, invalidate compromised credentials used for the initial access, and ensure that remediation efforts are not just treating the symptoms (the encrypted files) but addressing the actual cause of the enterprise-wide infection.

To effectively hunt for a malicious file like evil.exe across multiple hosts with "varying filepaths," a hunter must utilize the power of CrowdStrike Query Language (CQL) to aggregate execution telemetry. The inclusion of both ProcessRollup2 and SyntheticProcessRollup2 is vital in this scenario; while ProcessRollup2 captures new executions, SyntheticProcessRollup2 identifies processes that were already active when the Falcon sensor started. This provides critical visibility into files that "existed" and were already operational on the system prior to the detection of a new execution attempt.

The query in Option D is the most effective for a "proactive hunt" because it uses a regular expression—| ImageFileName=/([\/\\])(? < FileName > \w*\.?\w*)$/—to dynamically extract the actual filename into a new field (FileName) from the full path (ImageFileName). This allows the analyst to filter specifically for evil.exe while simultaneously seeing the "varying filepaths" where it resides. By outputting the results into a table containing the aid, hostname, and ImageFileName, the hunter generates a clear list of every unique location and host where the file is present. Unlike a stats count which only provides numerical volume, the table function provides the specific forensic artifacts (the paths) needed to begin remediation or host containment across the entire enterprise. This methodology allows the security team to identify the "blast radius" of the infection and uncover hidden instances of the malware that haven't yet triggered a primary detection.