Try in Splunk Security Cloud


This search looks for registry activity associated with application compatibility shims, which can be leveraged by attackers for various nefarious purposes.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel:
  • Last Updated: 2020-11-26
  • Author: Bhavin Patel, Patrick Bareiss, Splunk
  • ID: f5f6af30-7aa7-4295-bfe9-07fe87c01bbb


ID Technique Tactic
T1546.011 Application Shimming Privilege Escalation, Persistence
T1546 Event Triggered Execution Privilege Escalation, Persistence

| tstats `security_content_summariesonly` count values(Registry.registry_key_name) as registry_key_name min(_time) as firstTime max(_time) as lastTime FROM datamodel=Endpoint.Registry where Registry.registry_path=*CurrentVersion\\AppCompatFlags\\Custom* OR Registry.registry_path=*CurrentVersion\\AppCompatFlags\\InstalledSDB* by Registry.dest Registry.user 
| `security_content_ctime(lastTime)` 
| `security_content_ctime(firstTime)` 
| `drop_dm_object_name(Registry)` 
| `registry_keys_for_creating_shim_databases_filter`

Associated Analytic Story

How To Implement

To successfully implement this search, you must populate the Change_Analysis data model. This is typically populated via endpoint detection and response product, such as Carbon Black or other endpoint data sources such as Sysmon. The data used for this search is typically generated via logs that report reads and writes to the registry.

Required field

  • _time
  • Registry.registry_key_name
  • Registry.registry_path
  • Registry.dest
  • Registry.user

Kill Chain Phase

  • Actions on Objectives

Known False Positives

There are many legitimate applications that leverage shim databases for compatibility purposes for legacy applications


Risk Score Impact Confidence Message
56.0 70 80 A registry activity in $registry_path$ related to shim modication in host $dest$


Test Dataset

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

source | version: 3