Files
splunk-security_content/detections/endpoint/possible_lateral_movement_powershell_spawn.yml
mhaag-spl 76642e3c97 MMC
T1218.014
2022-07-01 07:43:45 -06:00

90 lines
3.5 KiB
YAML

name: Possible Lateral Movement PowerShell Spawn
id: cb909b3e-512b-11ec-aa31-3e22fbd008af
version: 1
date: '2021-11-29'
author: Mauricio Velazco, Splunk
type: TTP
datamodel:
- Endpoint
description: The following analytic assists with identifying a PowerShell process
spawned as a child or grand child process of commonly abused processes during lateral
movement techniques including `services.exe`, `wmiprsve.exe`, `svchost.exe`, `wsmprovhost.exe`
and `mmc.exe`. Legitimate Windows features such as the Service Control Manager,
Windows Management Instrumentation, Task Scheduler, Windows Remote Management and
the DCOM protocol can be abused to start a process on a remote endpoint. Looking
for PowerShell spawned out of this processes may reveal a lateral movement attack.
Red Teams and adversaries alike may abuse these services during a breach for lateral
movement and remote code execution.
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
as lastTime from datamodel=Endpoint.Processes where (Processes.parent_process_name=wmiprvse.exe
OR Processes.parent_process_name=services.exe OR Processes.parent_process_name=svchost.exe
OR Processes.parent_process_name=wsmprovhost.exe OR Processes.parent_process_name=mmc.exe)
(Processes.process_name=powershell.exe OR (Processes.process_name=cmd.exe AND Processes.process=*powershell.exe*)
OR Processes.process_name=pwsh.exe OR (Processes.process_name=cmd.exe AND Processes.process=*pwsh.exe*))
by Processes.dest Processes.user Processes.parent_process Processes.process_name
Processes.process Processes.process_id Processes.parent_process_id | `drop_dm_object_name(Processes)`
| `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `possible_lateral_movement_powershell_spawn_filter`'
how_to_implement: To successfully implement this search, you need to be ingesting
logs with the process name, parent process, and command-line executions from your
endpoints.
known_false_positives: Legitimate applications may spawn PowerShell as a child process
of the the identified processes. Filter as needed.
references:
- https://attack.mitre.org/techniques/T1021/003/
- https://attack.mitre.org/techniques/T1021/006/
- https://attack.mitre.org/techniques/T1047/
- https://attack.mitre.org/techniques/T1053/005/
- https://attack.mitre.org/techniques/T1543/003/
tags:
analytic_story:
- Hermetic Wiper
- Active Directory Lateral Movement
- Malicious PowerShell
confidence: 50
context:
- Source:Endpoint
- Stage:Lateral Movement
dataset:
- https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1543.003/lateral_movement_powershell/windows-sysmon.log
impact: 90
kill_chain_phases:
- Exploitation
message: A PowerShell process was spawned as a child process of typically abused
processes on $dest$
mitre_attack_id:
- T1021
- T1021.003
- T1021.006
- T1047
- T1053.005
- T1543.003
- T1059.001
- T1218.014
observable:
- name: dest
type: Endpoint
role:
- Victim
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: 45
security_domain: endpoint
supported_tas:
- Splunk_TA_microsoft_sysmon
asset_type: Endpoint