Files
splunk-security_content/detections/endpoint/windows_soaphound_binary_execution.yml
2024-03-20 20:01:18 +00:00

83 lines
3.6 KiB
YAML

name: Windows SOAPHound Binary Execution
id: 8e53f839-e127-4d6d-a54d-a2f67044a57f
version: 2
date: '2024-03-14'
author: Michael Haag, Splunk
status: production
type: TTP
data_source:
- Sysmon Event ID 1
description: The following analytic identifies the common command-line argument used
by SOAPHound `soaphound.exe`. Being the script is publicly available, function names may be modified,
but these changes are dependent upon the operator. In most instances the defaults
are used.
It does not cover the entirety of every argument in order to avoid false positives.
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name="soaphound.exe" OR Processes.original_file_name="soaphound.exe" AND Processes.process IN ("*--buildcache *", "*--bhdump *", "*--certdump *", "*--dnsdump *", "*-c *", "*--cachefilename *", "*-o *", "*--outputdirectory *") by Processes.process Processes.dest Processes.process_current_directory Processes.process_name Processes.process_path Processes.process_integrity_level Processes.parent_process Processes.parent_process_path Processes.parent_process_guid Processes.parent_process_id Processes.process_guid Processes.process_id Processes.user
| `drop_dm_object_name(Processes)`
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`| `windows_soaphound_binary_execution_filter`'
how_to_implement: The detection is based on data that originates from Endpoint Detection
and Response (EDR) agents. These agents are designed to provide security-related
telemetry from the endpoints where the agent is installed. To implement this search,
you must ingest logs that contain the process GUID, process name, and parent process.
Additionally, you must ingest complete command-line executions. These logs must
be processed using the appropriate Splunk Technology Add-ons that are specific to
the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint`
data model. Use the Splunk Common Information Model (CIM) to normalize the field
names and speed up the data modeling process.
known_false_positives: False positives should be limited as the command-line arguments
are specific to SOAPHound. Filter as needed.
references:
- https://github.com/FalconForceTeam/SOAPHound
tags:
analytic_story:
- Windows Discovery Techniques
asset_type: Endpoint
atomic_guid: []
confidence: 100
impact: 80
message: The process $process_name$ was executed on $dest$ related to SOAPHound.
mitre_attack_id:
- T1087.002
- T1069.001
- T1482
- T1087.001
- T1087
- T1069.002
- T1069
observable:
- name: process_name
type: Process
role:
- Victim
- name: dest
type: Hostname
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
risk_score: 80
required_fields:
- Processes.process
- Processes.dest
- Processes.process_current_directory
- Processes.process_path
- Processes.process_integrity_level
- Processes.parent_process
- Processes.parent_process_path
- Processes.parent_process_guid
- Processes.parent_process_id
- Processes.process_guid
- Processes.process_id
- Processes.user
- Processes.original_file_nam
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1059.001/soaphound/sysmon_soaphound.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog