Files
splunk-security_content/detections/endpoint/windows_query_registry_reg_save.yml
2022-12-21 12:38:29 -08:00

85 lines
3.1 KiB
YAML

name: Windows Query Registry Reg Save
id: cbee60c1-b776-456f-83c2-faa56bdbe6c6
version: 1
date: '2022-12-12'
author: Teoderick Contreras, Splunk
type: Hunting
datamodel:
- Endpoint
description: The following analytic identifies a process execution of reg.exe with "save" parameter.
This reg.exe parameter is commonly being abused by threat actors, adversaries and red-teamers to dump credentials or to check
the registry modification capabilities of certain users or administrators in targeted hosts. This approach was seen in post-exploitation
tool like winpeas where it uses "reg save" and "reg restore" to check registry modification restriction in targeted host after gaining
access to it.
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes
where `process_reg` AND Processes.process = "* save *"
by Processes.process_name Processes.original_file_name Processes.process Processes.process_id Processes.process_guid
Processes.parent_process_name Processes.parent_process Processes.parent_process_guid Processes.dest Processes.user
| `drop_dm_object_name(Processes)`
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| `windows_query_registry_reg_save_filter`'
how_to_implement: To successfully implement this search, you need to be ingesting
logs with the process name, parent process, and command-line executions from your
endpoints. If you are using Sysmon, you must have at least version 6.0.4 of the
Sysmon TA. Tune and filter known instances of wermgr.exe may be used.
known_false_positives: network administrator can use this command tool to backup registry before updates or modifying critical registries.
references:
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/quser
- https://github.com/carlospolop/PEASS-ng/tree/master/winPEAS
- https://www.microsoft.com/en-us/security/blog/2022/10/14/new-prestige-ransomware-impacts-organizations-in-ukraine-and-poland/
tags:
analytic_story:
- Windows Post-Exploitation
- Prestige Ransomware
asset_type: Endpoint
cis20:
- CIS 3
- CIS 5
- CIS 16
confidence: 30
context:
- Source:Endpoint
- Stage:Discovery
- Stage:Recon
dataset:
- https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/malware/winpeas/sysmon.log
impact: 30
kill_chain_phases:
- Exploitation
message: execution of process $process_name$ in $dest$
mitre_attack_id:
- T1012
nist:
- DE.CM
observable:
- name: dest
type: Hostname
role:
- Victim
- name: user
type: User
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
required_fields:
- _time
- Processes.dest
- Processes.user
- Processes.parent_process_name
- Processes.parent_process
- Processes.original_file_name
- Processes.process_name
- Processes.process
- Processes.process_id
- Processes.parent_process_path
- Processes.process_path
- Processes.parent_process_id
- Processes.parent_process_guid
- Processes.process_guid
risk_score: 9
security_domain: endpoint