Remote WMI Command Attempt

Try in Splunk Security Cloud

Description

The following analytic identifies usage of wmic.exe spawning a local or remote process, identified by the node switch. During triage, review parallel processes for additional commands executed. Look for any file modifications before and after wmic.exe execution. In addition, identify the remote endpoint and confirm execution or file modifications. Contain and isolate the endpoint as needed.

• Type: TTP
• Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
• Datamodel: Endpoint
• Last Updated: 2023-06-13
• Author: Rico Valdez, Michael Haag, Splunk
• ID: 272df6de-61f1-4784-877c-1fbc3e2d0838

Annotations

ATT&CK

ATT&CK

ID	Technique	Tactic
T1047	Windows Management Instrumentation	Execution

Kill Chain Phase

• Installation

NIST

• DE.CM

CIS20

• CIS 10

CVE

Search

| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where `process_wmic` Processes.process=*node* 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)` 
| `remote_wmi_command_attempt_filter`

Macros

The SPL above uses the following Macros:

• security_content_summariesonly
• security_content_ctime
• process_wmic

remote_wmi_command_attempt_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

• _time
• Processes.user
• Processes.process_name
• Processes.parent_process_name
• Processes.dest
• Processes.parent_process
• Processes.parent_process_id
• Processes.process_id

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 may use this legitimately to gather info from remote systems. Filter as needed.

Associated Analytic Story

• Volt Typhoon
• Graceful Wipe Out Attack
• IcedID
• Suspicious WMI Use
• Living Off The Land

RBA

Risk Score	Impact	Confidence	Message
36.0	60	60	A wmic.exe process $process$ contain node commandline $process$ in host $dest$

The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Reference

• https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1047/T1047.yaml
• https://www.microsoft.com/en-us/security/blog/2023/05/24/volt-typhoon-targets-us-critical-infrastructure-with-living-off-the-land-techniques/
• https://thedfirreport.com/2023/05/22/icedid-macro-ends-in-nokoyawa-ransomware/

Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 4