-
Notifications
You must be signed in to change notification settings - Fork 339
/
deleting_shadow_copies.yml
100 lines (100 loc) · 3.88 KB
/
deleting_shadow_copies.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
name: Deleting Shadow Copies
id: b89919ed-ee5f-492c-b139-95dbb162039e
version: 5
date: '2024-05-18'
author: David Dorsey, Splunk
status: production
type: TTP
description: The following analytic detects the deletion of shadow copies using the
vssadmin.exe or wmic.exe utilities. It leverages data from Endpoint Detection and
Response (EDR) agents, focusing on process names and command-line arguments. This
activity is significant because deleting shadow copies is a common tactic used by
attackers to prevent recovery and hide their tracks. If confirmed malicious, this
action could hinder incident response efforts and allow attackers to maintain persistence
and cover their activities, making it crucial for security teams to investigate
promptly.
data_source:
- Sysmon EventID 1
search: '| tstats `security_content_summariesonly` count values(Processes.process)
as process values(Processes.parent_process) as parent_process min(_time) as firstTime
max(_time) as lastTime from datamodel=Endpoint.Processes where (Processes.process_name=vssadmin.exe
OR Processes.process_name=wmic.exe) Processes.process=*delete* Processes.process=*shadow*
by Processes.user Processes.process_name Processes.parent_process_name Processes.dest |
`drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)`| `security_content_ctime(lastTime)`
| `deleting_shadow_copies_filter`'
how_to_implement: The detection is based on data that originates from Endpoint Detection
and Response (EDR) agents. These agents are designed to provide security-related
telemetry from the endpoints where the agent is installed. To implement this search,
you must ingest logs that contain the process GUID, process name, and parent process.
Additionally, you must ingest complete command-line executions. These logs must
be processed using the appropriate Splunk Technology Add-ons that are specific to
the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint`
data model. Use the Splunk Common Information Model (CIM) to normalize the field
names and speed up the data modeling process.
known_false_positives: vssadmin.exe and wmic.exe are standard applications shipped
with modern versions of windows. They may be used by administrators to legitimately
delete old backup copies, although this is typically rare.
references:
- https://blogs.vmware.com/security/2022/10/lockbit-3-0-also-known-as-lockbit-black.html
tags:
analytic_story:
- Windows Log Manipulation
- SamSam Ransomware
- Ransomware
- Clop Ransomware
- CISA AA22-264A
- Prestige Ransomware
- Chaos Ransomware
- LockBit Ransomware
- DarkGate Malware
- Rhysida Ransomware
asset_type: Endpoint
confidence: 90
impact: 90
message: An instance of $parent_process_name$ spawning $process_name$ was identified
on endpoint $dest$ by user $user$ attempting to delete shadow copies.
mitre_attack_id:
- T1490
observable:
- name: user
type: User
role:
- Victim
- name: dest
type: Hostname
role:
- Victim
- name: parent_process_name
type: Process
role:
- Parent Process
- name: process_name
type: Process
role:
- Child Process
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
risk_score: 81
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data:
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1490/atomic_red_team/windows-sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog