name: Script Execution via WMI id: aa73f80d-d728-4077-b226-81ea0c8be589 version: 4 date: '2020-03-16' author: Rico Valdez, Michael Haag, Splunk type: TTP datamodel: - Endpoint description: This search looks for scripts launched via WMI. search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name=scrcons.exe by Processes.dest Processes.user Processes.parent_process Processes.process_name Processes.process Processes.process_id Processes.parent_process_id | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `script_execution_via_wmi_filter` ' how_to_implement: You must be ingesting endpoint data that tracks process activity, including parent-child relationships from your endpoints to populate the Endpoint data model in the Processes node. The command-line arguments are mapped to the "process" field in the Endpoint data model. known_false_positives: Although unlikely, administrators may use wmi to launch scripts for legitimate purposes. Filter as needed. references: - https://redcanary.com/blog/child-processes/ tags: analytic_story: - Suspicious WMI Use asset_type: Endpoint cis20: - CIS 3 - CIS 5 confidence: 60 context: - Source:Endpoint - Stage:Execution dataset: - https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1047/execution_scrcons/windows-sysmon.log impact: 60 kill_chain_phases: - Actions on Objectives message: A wmic.exe process $process_name$ taht execute script in host $dest$ mitre_attack_id: - T1047 nist: - PR.PT - PR.AT - PR.AC - PR.IP observable: - name: dest type: Hostname role: - Victim - name: user type: User role: - Victim product: - Splunk Enterprise - Splunk Enterprise Security - Splunk Cloud required_fields: - _time - Processes.process_name - Processes.user - Processes.dest risk_score: 36 security_domain: endpoint supported_tas: - Splunk_TA_microsoft_sysmon