mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
tccontre
89 lines
3.6 KiB
YAML
89 lines
3.6 KiB
YAML
name: Windows Service Creation Using Registry Entry
|
|
id: 25212358-948e-11ec-ad47-acde48001122
|
|
version: 1
|
|
date: '2022-02-23'
|
|
author: Teoderick Contreras, Splunk
|
|
type: TTP
|
|
datamodel:
|
|
- Endpoint
|
|
description: This analytic is to look for suspicious modification or creation of registry
|
|
to have service entry. This technique is abused by adversaries or threat actor to
|
|
persist, gain privileges in the machine or even lateral movement. This technique
|
|
can be executed using reg.exe application or using windows API like for example
|
|
the CrashOveride malware. This detection is a good indicator that a process is trying
|
|
to create a service entry using registry ImagePath.
|
|
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime
|
|
max(_time) as lastTime FROM datamodel=Endpoint.Registry where Registry.registry_path="*\\SYSTEM\\CurrentControlSet\\Services*"
|
|
Registry.registry_value_name = ImagePath by _time span=1h Registry.dest Registry.user
|
|
Registry.registry_path Registry.registry_value_name Registry.registry_value_data
|
|
Registry.process_guid | `drop_dm_object_name(Registry)` |rename process_guid as
|
|
proc_guid |join proc_guid, _time [| tstats `security_content_summariesonly` count
|
|
FROM datamodel=Endpoint.Processes by _time span=1h Processes.process_id Processes.process_name
|
|
Processes.process Processes.dest Processes.parent_process_name Processes.parent_process
|
|
Processes.process_guid | `drop_dm_object_name(Processes)` |rename process_guid as
|
|
proc_guid | fields _time dest user parent_process_name parent_process process_name
|
|
process_path process proc_guid registry_path registry_value_name registry_value_data]
|
|
| table _time dest user parent_process_name parent_process process_name process_path
|
|
process proc_guid registry_path registry_value_name registry_value_data | `windows_service_creation_using_registry_entry_filter`'
|
|
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.
|
|
known_false_positives: Third party tools may used this technique to create services
|
|
but not so common.
|
|
references:
|
|
- https://github.com/redcanaryco/atomic-red-team/blob/36d49de4c8b00bf36054294b4a1fcbab3917d7c5/atomics/T1574.011/T1574.011.md
|
|
tags:
|
|
analytic_story:
|
|
- Active Directory Lateral Movement
|
|
- Suspicious Windows Registry Activities
|
|
- Windows Persistence Techniques
|
|
- Windows Registry Abuse
|
|
- Brute Ratel C4
|
|
cis20:
|
|
- CIS 3
|
|
- CIS 5
|
|
- CIS 16
|
|
confidence: 80
|
|
context:
|
|
- Source:Endpoint
|
|
- Stage:Lateral Movement
|
|
- Stage:Persistence
|
|
- Stage:Privilege Escalation
|
|
dataset:
|
|
- https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1574.011/change_registry_path_service/windows-sysmon.log
|
|
impact: 80
|
|
kill_chain_phases:
|
|
- Exploitation
|
|
message: A Windows Service was created on a endpoint from $dest$
|
|
mitre_attack_id:
|
|
- T1574.011
|
|
nist:
|
|
- DE.CM
|
|
observable:
|
|
- name: dest
|
|
type: Endpoint
|
|
role:
|
|
- Victim
|
|
product:
|
|
- Splunk Enterprise
|
|
- Splunk Enterprise Security
|
|
- Splunk Cloud
|
|
required_fields:
|
|
- _time
|
|
- Registry.registry_key_name
|
|
- Registry.registry_path
|
|
- Registry.user
|
|
- Registry.dest
|
|
- Registry.registry_value_name
|
|
- Processes.process_id
|
|
- Processes.process_name
|
|
- Processes.process
|
|
- Processes.dest
|
|
- Processes.parent_process_name
|
|
- Processes.parent_process
|
|
- Processes.process_guid
|
|
risk_score: 64
|
|
security_domain: endpoint
|
|
asset_type: Endpoint
|