CCFH-202b Exam Dumps - CrowdStrike CCFH Questions and Answers

This query is a sophisticated example of using Event Search to visualize potential external threats. The key to identifying the purpose lies in the LogonType=10 filter. In Windows event logging, Logon Type 10 specifically refers to Remote Interactive logons, which are almost exclusively associated with Remote Desktop Protocol (RDP) sessions. By combining this with RemoteAddressIP4=*, the hunter is isolating instances where a user has accessed a system remotely.

The query then utilizes the !cidr function (the exclamation mark denotes a "NOT" operation) to exclude all internal and private IP ranges defined by RFC 1918 (such as 10.x.x.x and 192.168.x.x) as well as loopback and multicast addresses. This ensures that the resulting dataset only contains logons originating from external/public IP addresses . The ipLocation function enriches these external IPs with geographic metadata (city, country, coordinates), and the worldMap function aggregates this data to plot the origin of these RDP connections onto a global map. For a hunter, this is a vital tool for detecting "Impossible Travel" scenarios or identifying unauthorized access attempts from high-risk geographic regions. Visualizing the magnitude of connections per aid (Agent ID) allows the analyst to quickly spot which specific endpoints are being targeted by external RDP brute-force or credential stuffing attacks.

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.

In the MITRE ATT & CK Framework , it is essential to distinguish between Tactics and Techniques . "Credential Access" represents the Tactic—the adversary’s ultimate goal or "Why." However, OS Credential Dumping (T1003) is the specific Technique—the "How"—used to achieve that goal. Within the Falcon Console's Detections page, filtering by Technique allows a hunter to isolate specific behaviors, such as the unauthorized extraction of cleartext passwords or hashes from the LSA Secrets or the SAM database.

When a hunter filters for OS Credential Dumping , the Falcon platform surfaces events associated with processes like lsass.exe being accessed by suspicious tools (e.g., Mimikatz) or through unusual methods like procdump.exe. Utilizing this specific technique as a filter is a key part of Hunting Methodology , as it enables the analyst to identify patterns of behavior across multiple hosts that might otherwise look like isolated incidents. While "Gain Access" might be part of the broader narrative, it is too broad for effective filtering. By focusing on the specific technique of credential dumping, a hunter can prioritize high-severity alerts that directly lead to lateral movement or administrative compromise, ensuring that the response effort is focused on the most critical stages of the attack lifecycle.

In the context of Search and Investigation Tools , tracking the use of unauthorized or unencrypted USB storage devices is a critical component of internal threat hunting and data loss prevention (DLP). The Falcon sensor records these hardware interactions using the specific event name RemovableMediaVolumeMounted . This event is triggered whenever the operating system successfully mounts a removable storage volume, such as a USB flash drive or an external hard disk.

Option A is the correct CrowdStrike Query Language (CQL) syntax because it pairs the appropriate event with fields that provide meaningful forensic context. Fields like VolumeDriveLetter identify which logical drive was assigned (e.g., E: or F:), while VolumeFileSystemDevice and VolumeFileSystemDriver offer technical details about the hardware interface and the driver utilized to facilitate the mount.

Conversely, Option B selects fields that are relevant to process execution and network connectivity (like hashes and IP addresses), which are not typically populated in a volume mount event. Option C focuses on ProcessRollup2 , which tracks the starting of executables rather than hardware mounts. Option D utilizes FsVolumeMounted, which is a broader event that includes internal fixed partitions and network drives, making it less precise for hunting specifically for "removable" media. By utilizing the query in Option A, a hunter can build a timeline of when external devices were connected to the environment, allowing them to correlate these mounts with subsequent file writes or "Exfiltration" behaviors.

The command net user < username > < password > /add /domain is a direct method used by adversaries to perform the Create Account technique (T1136) within the MITRE ATT & CK Matrix. Specifically, this command attempts to create a new domain account, which allows the attacker to establish a foothold that appears legitimate and can be used for subsequent authentication across the network. Unlike Account Manipulation , which involves modifying existing accounts (such as changing a password or adding a user to a group), Create Account focuses on the generation of entirely new credentials to maintain access and bypass certain security triggers.

From a Detection Analysis perspective in Falcon, this activity is highly visible within the ProcessRollup2 events. Analysts look for the net.exe or net1.exe binaries being called with the /add and /domain flags in the CommandLine field. This behavior is a common post-exploitation step following initial access. If an adversary successfully creates a domain account, they can then transition to using Valid Accounts (T1078) for lateral movement, making their actions much harder to distinguish from normal administrative traffic. Hunting for this technique requires a baseline understanding of authorized account creation procedures within the organization; any deviation, such as the use of "hacker" as a username or execution from a non-domain controller host, should be treated as a high-severity incident.

In Event Search , correlating the full scope of a process's activity requires an understanding of the "Process ID Trinity." When the process reallysus.exe is executed, its primary identity is captured in a ProcessRollup2 event under the TargetProcessId . However, searching only for the TargetProcessId would merely return the process start record. To see the actions the process performed—such as connecting to a malicious IP or writing a persistence key—the hunter must also search for the ContextProcessId .

The ContextProcessId is used in all telemetry events generated by that process. Furthermore, for cross-process activity initiated via Remote Procedure Calls, the RpcClientProcessId may be involved. By using the OR operator to combine TargetProcessId, ContextProcessId, and RpcClientProcessId in a single query, the hunter ensures they are capturing the entire lifecycle: the creation of the process, every network/file/registry operation it performed, and its interactions with other system services. This comprehensive search strategy is fundamental to Search and Investigation Tools , as it allows for a seamless reconstruction of the adversary's timeline. Missing any of these identifiers would result in "blind spots" in the investigation, potentially hiding the most critical evidence of data exfiltration or lateral movement.

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.

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.