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

53 lines
1.5 KiB
YAML

name: Script Execution via WMI
id: aa73f80d-d728-4077-b226-81ea0c8be589
version: 4
date: '2020-03-16'
author: Rico Valdez, Michael Haag, Splunk
status: production
type: TTP
description: This search looks for scripts launched via WMI.
data_source:
- Sysmon Event ID 1
search:
selection1:
Image|endswith: scrcons.exe
condition: selection1
how_to_implement: You must be ingesting endpoint data that tracks process activity,
including parent-child relationships from your endpoints to populate the Endpoint
data model in the Processes node. The command-line arguments are mapped to the "process"
field in the Endpoint data model.
known_false_positives: Although unlikely, administrators may use wmi to launch scripts
for legitimate purposes. Filter as needed.
references:
- https://redcanary.com/blog/child-processes/
tags:
analytic_story:
- Suspicious WMI Use
asset_type: Endpoint
confidence: 60
impact: 60
message: A wmic.exe process $process_name$ taht execute script in host $dest$
mitre_attack_id:
- T1047
observable:
- name: dest
type: Hostname
role:
- Victim
- name: user
type: User
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
risk_score: 36
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1047/execution_scrcons/windows-sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog