Name:Domain Account Discovery with Dsquery id:b1a8ce04-04c2-11ec-bea7-acde48001122 version:4 date:2024-10-17 author:Teoderick Contreras, Mauricio Velazco, Splunk status:production type:Hunting Description:The following analytic identifies the execution of `dsquery.exe` with command-line arguments used to discover domain users. It leverages data from Endpoint Detection and Response (EDR) agents, focusing on process names and command-line executions. This activity is significant as it indicates potential reconnaissance efforts by adversaries to map out domain users, which is a common precursor to further attacks. If confirmed malicious, this behavior could allow attackers to gain insights into user accounts, facilitating subsequent actions like privilege escalation or lateral movement within the network. Data_source:
-Sysmon EventID 1
-Windows Event Log Security 4688
-CrowdStrike ProcessRollup2
search:| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name="dsquery.exe" AND Processes.process = "*user*" by Processes.dest Processes.user Processes.parent_process Processes.process_name Processes.process Processes.process_id Processes.parent_process_id Processes.parent_process_name | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `domain_account_discovery_with_dsquery_filter`
how_to_implement:The detection is based on data that originates from Endpoint Detection and Response (EDR) agents. These agents are designed to provide security-related telemetry from the endpoints where the agent is installed. To implement this search, you must ingest logs that contain the process GUID, process name, and parent process. Additionally, you must ingest complete command-line executions. These logs must be processed using the appropriate Splunk Technology Add-ons that are specific to the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint` data model. Use the Splunk Common Information Model (CIM) to normalize the field names and speed up the data modeling process. known_false_positives:Administrators or power users may use this command for troubleshooting. References: -https://jpcertcc.github.io/ToolAnalysisResultSheet/details/dsquery.htm -https://attack.mitre.org/techniques/T1087/002/ drilldown_searches:
: tags: analytic_story: - 'Active Directory Discovery' asset_type:Endpoint confidence:50 impact:50 message:an instance of process $process_name$ with commandline $process$ in $dest$ mitre_attack_id: - 'T1087.002' - 'T1087' observable: name:'user' type:'User' - role: - 'Victim' name:'dest' type:'Hostname' - role: - 'Victim' name:'parent_process_name' type:'Process' - role: - 'Attacker' product: - 'Splunk Enterprise' - 'Splunk Enterprise Security' - 'Splunk Cloud' required_fields: - '_time' - 'Processes.dest' - 'Processes.user' - 'Processes.parent_process' - 'Processes.process_name' - 'Processes.process' - 'Processes.process_id' - 'Processes.parent_process_id' - 'Processes.parent_process_name' risk_score:25 security_domain:endpoint
