mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
root
72 lines
2.7 KiB
YAML
72 lines
2.7 KiB
YAML
name: Screensaver Event Trigger Execution
|
|
id: 58cea3ec-1f6d-11ec-8560-acde48001122
|
|
version: 1
|
|
date: '2021-09-27'
|
|
author: Teoderick Contreras, Splunk
|
|
type: TTP
|
|
datamodel:
|
|
- Endpoint
|
|
description: This analytic is developed to detect possible event trigger execution
|
|
through screensaver registry entry modification for persistence or privilege escalation.
|
|
This technique was seen in several APT and malware where they put the malicious
|
|
payload path to the SCRNSAVE.EXE registry key to redirect the execution to their
|
|
malicious payload path. This TTP is a good indicator that some attacker may modify
|
|
this entry for their persistence and privilege escalation.
|
|
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime
|
|
max(_time) as lastTime FROM datamodel=Endpoint.Registry where (Registry.registry_path="*\\Control
|
|
Panel\\Desktop\\SCRNSAVE.EXE*") 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)` | `screensaver_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/T1546/002/
|
|
- https://dmcxblue.gitbook.io/red-team-notes-2-0/red-team-techniques/privilege-escalation/untitled-3/screensaver
|
|
tags:
|
|
analytic_story:
|
|
- Windows Persistence Techniques
|
|
- Windows Privilege Escalation
|
|
- Windows Registry Abuse
|
|
- Hermetic Wiper
|
|
confidence: 90
|
|
context:
|
|
- Source:Endpoint
|
|
- Stage:Privilege Escalation
|
|
dataset:
|
|
- https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1546.002/scrnsave_reg/sysmon.log
|
|
impact: 80
|
|
kill_chain_phases:
|
|
- Exploitation
|
|
message: modified/added/deleted registry entry $Registry.registry_path$ in $dest$
|
|
mitre_attack_id:
|
|
- T1546
|
|
- T1546.002
|
|
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: 72
|
|
security_domain: endpoint
|
|
asset_type: Endpoint
|