mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
P4T12ICK
91 lines
3.2 KiB
YAML
91 lines
3.2 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
|
|
type: Hunting
|
|
datamodel:
|
|
- Endpoint
|
|
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.
|
|
search: '| tstats `security_content_summariesonly` count values(Processes.process)
|
|
as process min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes
|
|
where `process_cmd` by Processes.parent_process_name Processes.process_name Processes.original_file_name
|
|
Processes.dest Processes.user| `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)`|
|
|
`security_content_ctime(lastTime)` |search [`prohibited_apps_launching_cmd`] | `detect_prohibited_applications_spawning_cmd_exe_filter`'
|
|
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
|
|
cis20:
|
|
- CIS 8
|
|
confidence: 100
|
|
context:
|
|
- Source:Endpoint
|
|
- Stage:Execution
|
|
dataset:
|
|
- https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1059.003/powershell_spawn_cmd/windows-sysmon.log
|
|
impact: 80
|
|
kill_chain_phases:
|
|
- Exploitation
|
|
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
|
|
nist:
|
|
- PR.PT
|
|
- DE.CM
|
|
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
|
|
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: 80
|
|
security_domain: endpoint
|