Files
splunk-security_content/dev_ssa/endpoint/ssa___windows_diskshadow_proxy_execution.yml
Eric McGinnis 9fdf182033 Release v4.24.0
2024-02-14 23:54:00 +00:00

53 lines
2.0 KiB
YAML

name: Windows Diskshadow Proxy Execution
id: aa502688-9037-11ec-842d-acde48001122
version: 4
date: '2022-02-17'
author: Lou Stella, Splunk
status: production
type: Anomaly
description: DiskShadow.exe is a Microsoft Signed binary present on Windows Server.
It has a scripting mode intended for complex scripted backup operations. This feature
also allows for execution of arbitrary unsigned code. This analytic looks for the
usage of the scripting mode flags in executions of DiskShadow. During triage, compare
to known backup behavior in your environment and then review the scripts called
by diskshadow.
data_source:
- Windows Security 4688
search:
selection1:
process.cmd_line|contains:
- /s
- -S
process.file.name: diskshadow.exe
condition: selection1
how_to_implement: To successfully implement this search you need to be ingesting information
on processes that include the name of the process responsible for the changes from
your endpoints into the `Endpoint_Processess` datamodel.
known_false_positives: Administrators using the DiskShadow tool in their infrastructure
as a main backup tool with scripts will cause false positives
references:
- https://bohops.com/2018/03/26/diskshadow-the-return-of-vss-evasion-persistence-and-active-directory-database-extraction/
tags:
analytic_story:
- Living Off The Land
asset_type: Endpoint
confidence: 70
impact: 70
message: An instance of $parent_process_name$ spawning $process_name$ was identified
on endpoint $dest_device_id$ by user $dest_user_id$ attempting to run a script.
mitre_attack_id:
- T1218
observable: []
product:
- Splunk Behavioral Analytics
required_fields: []
kill_chain_phases:
- Exploitation
risk_score: 49
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1218/diskshadow/windows-security.log
source: WinEventLog:Security