Files
splunk-security_content/detections/remote_wmi_command_attempt.yml
2020-05-06 17:42:38 +02:00

40 lines
1.5 KiB
YAML

name: Remote WMI Command Attempt
id: 272df6de-61f1-4784-877c-1fbc3e2d0838
version: 2
date: '2018-12-03'
description: This search looks for wmic.exe being launched with parameters to operate
on remote systems.
how_to_implement: You must be ingesting data that records process activity from your
hosts to populate the Endpoint data model in the Processes node. You must also be
ingesting logs with both the process name and command line from your endpoints.
The command-line arguments are mapped to the "process" field in the Endpoint data
model.
type: ESCU
references: []
author: Rico Valdez, Splunk
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=wmic.exe AND
Processes.process= */node* 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)` | `remote_wmi_command_attempt_filter`'
known_false_positives: Administrators may use this legitimately to gather info from
remote systems.
tags:
analytics_story:
- Suspicious WMI Use
mitre_attack_id:
- T1047
kill_chain_phases:
- Actions on Objectives
cis20:
- CIS 3
- CIS 5
nist:
- PR.PT
- PR.AT
- PR.AC
- PR.IP
security_domain: endpoint
asset_type: Endpoint