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

74 lines
2.5 KiB
YAML

name: Detect Prohibited Applications Spawning cmd exe
id: dcfd6b40-42f9-469d-a433-2e53f7486664
version: 6
date: '2020-11-10'
author: Bhavin Patel, Splunk
status: production
type: Hunting
description: This search looks for executions of cmd.exe spawned by a process that
is often abused by attackers and that does not typically launch cmd.exe.
data_source:
- Sysmon Event ID 1
search:
selection1:
OriginalFileName: Cmd.Exe
selection2:
Image|endswith: cmd.exe
condition: (selection1 or selection2)
how_to_implement: You must be ingesting data that records process activity from your
hosts and populates the Endpoint data model with the resultant dataset. This search
includes a lookup file, `prohibited_apps_launching_cmd.csv`, that contains a list
of processes that should not be spawning cmd.exe. You can modify this lookup to
better suit your environment. To successfully implement this search you need to
be ingesting information on process that include the name of the process responsible
for the changes from your endpoints into the `Endpoint` datamodel in the `Processes`
node. In addition, confirm the latest CIM App 4.20 or higher is installed and the
latest TA for the endpoint product.
known_false_positives: There are circumstances where an application may legitimately
execute and interact with the Windows command-line interface. Investigate and modify
the lookup file, as appropriate.
references: []
tags:
analytic_story:
- Suspicious Command-Line Executions
- Suspicious MSHTA Activity
- Suspicious Zoom Child Processes
- NOBELIUM Group
asset_type: Endpoint
confidence: 100
impact: 80
message: An instance of $parent_process_name$ spawning $process_name$ was identified
on endpoint $dest$ by user $user$ running prohibited applications.
mitre_attack_id:
- T1059
- T1059.003
observable:
- name: user
type: User
role:
- Victim
- name: Computer
type: Hostname
role:
- Victim
- name: parent_process_name
type: Process
role:
- Parent Process
- name: process_name
type: Process
role:
- Child Process
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
risk_score: 80
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1059.003/powershell_spawn_cmd/windows-sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog