Files
splunk-security_content/detections/deprecated/windows_connhost_exe_force_flag.yml
2022-03-09 14:43:09 +01:00

56 lines
1.9 KiB
YAML

name: Windows connhost exe started forcefully
id: c114aaca-68ee-41c2-ad8c-32bf21db8769
version: 1
date: '2020-11-06'
author: Rod Soto, Jose Hernandez, Splunk
type: TTP
datamodel: []
description: 'The search looks for the Console Window Host process (connhost.exe)
executed using the force flag -ForceV1. This is not regular behavior in the Windows
OS and is often seen executed by the Ryuk Ransomware. DEPRECATED This event is actually
seen in the windows 10 client of attack_range_local. After further testing we realized
this is not specific to Ryuk. '
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
as lastTime FROM datamodel=Endpoint.Processes WHERE Processes.process="*C:\\Windows\\system32\\conhost.exe*
0xffffffff *-ForceV1*" by Processes.user Processes.process_name Processes.process
Processes.dest | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)`|
`security_content_ctime(lastTime)` | `windows_connhost_exe_started_forcefully_filter`'
how_to_implement: You must be ingesting data that records the process-system activity
from your hosts to populate the Endpoint Processes data-model object. If you are
using Sysmon, you will need a Splunk Universal Forwarder on each endpoint from which
you want to collect data.
known_false_positives: This process should not be ran forcefully, we have not see
any false positives for this detection
references: []
tags:
analytic_story:
- Ryuk Ransomware
asset_type: Endpoint
cis20:
- CIS 8
kill_chain_phases:
- Delivery
mitre_attack_id:
- T1059.003
nist:
- PR.PT
- DE.CM
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
required_fields:
- _time
security_domain: endpoint
confidence: 50
impact: 50
risk_score: 25
context:
- Unknown
message: tbd
observable:
- name: field
type: Unknown
role:
- Unknown