This search is to detect modification of registry to bypass UAC windows feature. This technique is to add a payload dll path on .NET COR file path that will be loaded by mmc.exe as soon it was executed. This detection rely on monitoring the registry key and values in the detection area. It may happened that windows update some dll related to mmc.exe and add dll path in this registry. In this case filtering is needed.
- Type: TTP
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint
- Last Updated: 2021-07-12
- Author: Teoderick Contreras, Splunk
- ID: 0252ca80-e30d-11eb-8aa3-acde48001122
|T1548.002||Bypass User Account Control||Privilege Escalation, Defense Evasion|
| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Registry where Registry.registry_path= "*\\Environment\\COR_PROFILER_PATH" Registry.registry_value_name = "*.dll" by Registry.registry_path Registry.registry_key_name Registry.registry_value_name Registry.dest | `drop_dm_object_name(Registry)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `net_profiler_uac_bypass_filter`
Associated Analytic Story
How To Implement
To successfully implement this search you need to be ingesting information on process that include the name of the process responsible for the changes from your endpoints into the
Endpoint datamodel in the
Registry node. Also make sure that this registry was included in your config files ex. sysmon config to be monitored.
Kill Chain Phase
Known False Positives
limited false positive. It may trigger by some windows update that will modify this registry.
|63.0||70||90||Suspicious modification of registry $registry_path$ with possible payload path $registry_value_name$ in $dest$|
source | version: 1