Files
splunk-security_content/dev/endpoint/remcos_client_registry_install_entry.yml
2023-01-20 13:24:15 +01:00

51 lines
1.6 KiB
YAML

name: Remcos client registry install entry
id: f2a1615a-1d63-11ec-97d2-acde48001122
version: 2
date: '2022-01-26'
author: Bhavin Patel, Rod Soto, Teoderick Contreras, Splunk
status: production
type: TTP
description: This search detects registry key license at host where Remcos RAT agent
is installed.
data_source:
- Sysmon Event ID 13
search:
selection1:
Registry.registry_key_name: '*\\Software\\Remcos*'
condition: (selection1)
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: unknown
references:
- https://attack.mitre.org/software/S0332/
tags:
analytic_story:
- Remcos
- Windows Registry Abuse
asset_type: Endpoint
confidence: 100
impact: 90
message: A registry entry $registry_path$ with registry keyname $registry_key_name$
related to Remcos RAT in host $dest$
mitre_attack_id:
- T1112
observable:
- name: dest
type: Hostname
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
risk_score: 90
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/malware/remcos/remcos_registry/sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog