mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
Bhavin Patel
74 lines
2.8 KiB
YAML
74 lines
2.8 KiB
YAML
name: Logon Script Event Trigger Execution
|
|
id: 4c38c264-1f74-11ec-b5fa-acde48001122
|
|
version: 2
|
|
date: '2024-05-10'
|
|
author: Teoderick Contreras, Splunk
|
|
status: production
|
|
type: TTP
|
|
description: The following analytic detects the modification of the UserInitMprLogonScript
|
|
registry entry, which is often used by attackers to establish persistence and gain
|
|
privilege escalation upon system boot. It leverages data from the Endpoint.Registry
|
|
data model, focusing on changes to the specified registry path. This activity is
|
|
significant because it is a common technique used by APT groups and malware to ensure
|
|
their payloads execute automatically when the system starts. If confirmed malicious,
|
|
this could allow attackers to maintain persistent access and potentially escalate
|
|
their privileges on the compromised host.
|
|
data_source:
|
|
- Sysmon EventID 13
|
|
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime
|
|
max(_time) as lastTime FROM datamodel=Endpoint.Registry where Registry.registry_path
|
|
IN ("*\\Environment\\UserInitMprLogonScript") by Registry.dest Registry.user Registry.registry_path
|
|
Registry.registry_key_name Registry.registry_value_name | `security_content_ctime(lastTime)`
|
|
| `security_content_ctime(firstTime)` | `drop_dm_object_name(Registry)` | `logon_script_event_trigger_execution_filter`'
|
|
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: unknown
|
|
references:
|
|
- https://attack.mitre.org/techniques/T1037/001/
|
|
tags:
|
|
analytic_story:
|
|
- Data Destruction
|
|
- Windows Privilege Escalation
|
|
- Hermetic Wiper
|
|
- Windows Persistence Techniques
|
|
asset_type: Endpoint
|
|
confidence: 100
|
|
impact: 80
|
|
message: Registry path $registry_path$ was modified, added, or deleted on $dest$.
|
|
mitre_attack_id:
|
|
- T1037
|
|
- T1037.001
|
|
observable:
|
|
- name: dest
|
|
type: Hostname
|
|
role:
|
|
- Victim
|
|
- name: user
|
|
type: User
|
|
role:
|
|
- Victim
|
|
product:
|
|
- Splunk Enterprise
|
|
- Splunk Enterprise Security
|
|
- Splunk Cloud
|
|
required_fields:
|
|
- _time
|
|
- Registry.dest
|
|
- Registry.user
|
|
- Registry.registry_path
|
|
- Registry.registry_key_name
|
|
- Registry.registry_value_name
|
|
risk_score: 80
|
|
security_domain: endpoint
|
|
tests:
|
|
- name: True Positive Test
|
|
attack_data:
|
|
- data:
|
|
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1037.001/logonscript_reg/sysmon.log
|
|
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
|
|
sourcetype: xmlwineventlog
|