Files
splunk-security_content/detections/malicious_powershell_process_with_obfuscation_techniques.yml
Patrick Bareiss 9a50a74ee7 bug in generate
2020-05-14 10:00:55 +02:00

44 lines
1.7 KiB
YAML

name: Malicious PowerShell Process With Obfuscation Techniques
id: cde75cf6-3c7a-4dd6-af01-27cdb4511fd4
version: 2
date: '2020-01-17'
description: This search looks for PowerShell processes launched with arguments that
have characters indicative of obfuscation on the command-line.
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: David Dorsey, 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=powershell.exe
by Processes.user Processes.process_name Processes.parent_process_name Processes.dest
Processes.process | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)`|
`security_content_ctime(lastTime)`| eval num_obfuscation = (mvcount(split(process,
"`"))-1) + (mvcount(split(process, "^"))-1) | `malicious_powershell_process_with_obfuscation_techniques_filter`
| search num_obfuscation > 0'
known_false_positives: These characters might be legitimately on the command-line,
but it is not common.
tags:
analytics_story:
- Malicious PowerShell
mitre_attack_id:
- T1086
- T1064
kill_chain_phases:
- Command and Control
- Actions on Objectives
cis20:
- CIS 3
- CIS 7
- CIS 8
nist:
- PR.PT
- DE.CM
- PR.IP
security_domain: endpoint
asset_type: Endpoint