Try in Splunk Security Cloud

Description

The following analytic identifies the usage of msiexec.exe using the /y switch parameter, which grants the ability for msiexec to load DLLRegisterServer. Upon triage, review parent process and capture any artifacts for further review.

  • Type: TTP

  • Product: Splunk Behavioral Analytics

  • Last Updated: 2022-08-31
  • Author: Michael Haag, Splunk
  • ID: 8d1d5570-722c-49a3-996c-2e2cceef5163

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1218.007 Msiexec Defense Evasion
Kill Chain Phase
  • Exploitation
NIST
  • DE.CM
CIS20
  • CIS 10
CVE 


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17



 $main = from source  
| eval timestamp = time  
| eval metadata_uid = metadata.uid  
| eval process_pid = process.pid 
| eval process_file = process.file 
| eval process_file_path = process_file.path 
| eval process_file_name = lower(process_file.name) 
| eval process_cmd_line = process.cmd_line 
| eval actor_user = actor.user 
| eval actor_user_name = actor_user.name 
| eval actor_process = actor.process 
| eval actor_process_pid = actor_process.pid 
| eval actor_process_file = actor_process.file 
| eval actor_process_file_path = actor_process_file.path 
| eval actor_process_file_name = actor_process_file.name 
| eval device_hostname = device.hostname 
| where (process_cmd_line LIKE "%-y %" OR process_cmd_line LIKE "%/y %") AND process_file_name="msiexec.exe" --finding_report--

Macros

The SPL above uses the following Macros:

:information_source: windows_system_binary_proxy_execution_msiexec_dllregisterserver_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.

  • process.pid
  • process.file.path
  • process.file.name
  • process.cmd_line
  • actor.user.name
  • actor.process.pid
  • actor.process.file.path
  • actor.process.file.name
  • device.hostname

How To Implement

To successfully implement this search, you need to be ingesting logs with the process name, parent process, and command-line executions from your endpoints. If you are using Sysmon, you must have at least version 6.0.4 of the Sysmon TA.

Known False Positives

This analytic will need to be tuned for your environment based on legitimate usage of msiexec.exe. Filter as needed.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
35.0 70 50 An instance of spawning $process_name$ was identified on endpoint $dest_device_id$ by user $dest_user_id$ attempting to register a file.

:information_source: 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

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