The following analytic identifies
WmiPrvSE.exe spawning a process. This typically occurs when a process is instantiated from a local or remote process using
wmic.exe. During triage, review parallel processes for suspicious behavior or commands executed. Review the process and command-line spawning from
wmiprvse.exe. Contain and remediate the endpoint as necessary.
- Type: TTP
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint
- Last Updated: 2020-03-16
- Author: Rico Valdez, Michael Haag, Splunk
- ID: 24869767-8579-485d-9a4f-d9ddfd8f0cac
|T1047||Windows Management Instrumentation||Execution|
| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.parent_process_name=WmiPrvSE.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)` | `process_execution_via_wmi_filter`
Associated Analytic Story
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.
Kill Chain Phase
- Actions on Objectives
Known False Positives
Although unlikely, administrators may use wmi to execute commands for legitimate purposes.
|49.0||70||70||A remote instance execution of wmic.exe that will spawn $parent_process_name$ in host $dest$|
source | version: 4