Files
splunk-security_content/detections/endpoint/slui_spawning_a_process.yml
2024-06-26 14:41:53 +00:00

82 lines
3.4 KiB
YAML

name: SLUI Spawning a Process
id: 879c4330-b3e0-11eb-b1b1-acde48001122
version: 2
date: '2024-05-18'
author: Michael Haag, Splunk
status: production
type: TTP
description: The following analytic detects the Microsoft Software Licensing User
Interface Tool (`slui.exe`) spawning a child process. This behavior is identified
using Endpoint Detection and Response (EDR) telemetry, focusing on process creation
events where `slui.exe` is the parent process. This activity is significant because
`slui.exe` should not typically spawn child processes, and doing so may indicate
a UAC bypass attempt, leading to elevated privileges. If confirmed malicious, an
attacker could leverage this to execute code with elevated privileges, potentially
compromising the system's security and gaining unauthorized access.
data_source:
- Sysmon EventID 1
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
as lastTime from datamodel=Endpoint.Processes where Processes.parent_process_name=slui.exe
by Processes.dest Processes.user Processes.parent_process_name 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)`
| `slui_spawning_a_process_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: Certain applications may spawn from `slui.exe` that are legitimate.
Filtering will be needed to ensure proper monitoring.
references:
- https://www.exploit-db.com/exploits/46998
- https://www.rapid7.com/db/modules/exploit/windows/local/bypassuac_sluihijack/
- https://www.mandiant.com/resources/shining-a-light-on-darkside-ransomware-operations
tags:
analytic_story:
- DarkSide Ransomware
- Windows Defense Evasion Tactics
asset_type: Endpoint
confidence: 90
impact: 70
message: A slui process $parent_process_name$ spawning child process $process_name$
in host $dest$
mitre_attack_id:
- T1548.002
- T1548
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.dest
- Processes.user
- Processes.parent_process
- Processes.process_name
- Processes.process
- Processes.process_id
- Processes.parent_process_id
risk_score: 63
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data:
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1548.002/slui/windows-sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog