The following analytic identifies the Microsoft Software Licensing User Interface Tool,
slui.exe, elevating access using the
-verb runas function. This particular bypass utilizes a registry key/value. Identified by two sources, the registry keys are
HKCU\Software\Classes\launcher.Systemsettings\Shell\open\command. To simulate this behavior, multiple POC are available. The analytic identifies the use of
- Type: TTP
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint
- Last Updated: 2021-05-13
- Author: Michael Haag, Splunk
- ID: 8d124810-b3e4-11eb-96c7-acde48001122
Kill Chain Phase
- CIS 10
1 2 3 4 5 6 | tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name=slui.exe (Processes.process=*-verb* Processes.process=*runas*) 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)` | `slui_runas_elevated_filter`
The SPL above uses the following Macros:
slui_runas_elevated_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
List of fields required to use this analytic.
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
Limited false positives should be present as this is not commonly used by legitimate applications.
Associated Analytic Story
|63.0||70||90||A slui process $process_name$ with elevated 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.
source | version: 1