Windows Mshta Execution In Registry
- Type: TTP
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Datamodel: Endpoint
- Last Updated: 2022-10-14
- Author: Teoderick Contreras, Splunk
- ID: e13ceade-b673-4d34-adc4-4d9c01729753
Kill Chain Phase
- CIS 3
- CIS 5
- CIS 16
The SPL above uses the following Macros:
windows_mshta_execution_in_registry_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
To successfully implement this search, you must be ingesting data that records registry activity from your hosts to populate the endpoint data model in the registry node. This is typically populated via endpoint detection-and-response product, such as Carbon Black or 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.
Known False Positives
Associated Analytic Story
|72.0||80||90||a registry $registry_path$ contains mshta $registry_value_data$ in $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.
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: 1