Files
splunk-security_content/detections/endpoint/detect_sharphound_command_line_arguments.yml
tccontre 14e3597bf4 CARS_UPDATE_MITRE_ID_B4
CARS_UPDATE_MITRE_ID_B3
2021-10-13 11:13:24 +02:00

74 lines
2.8 KiB
YAML

name: Detect SharpHound Command-Line Arguments
id: a0bdd2f6-c2ff-11eb-b918-acde48001122
version: 1
date: '2021-06-01'
author: Michael Haag, Splunk
type: TTP
datamodel:
- Endpoint
description: The following analytic identifies common command-line arguments used
by SharpHound `-collectionMethod` and `invoke-bloodhound`. Being the script is FOSS,
function names may be modified, but these changes are dependent upon the operator.
In most instances the defaults are used. This analytic works to identify the common
command-line attributes 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 IN ("*-collectionMethod*","*invoke-bloodhound*")
by Processes.dest Processes.user Processes.parent_process Processes.process_name
Processes.process Processes.process_id Processes.parent_process_id | `drop_dm_object_name(Processes)`
| `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `detect_sharphound_command_line_arguments_filter`'
how_to_implement: 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.
known_false_positives: False positives should be limited as the arguments used are
specific to SharpHound. Filter as needed or add more command-line arguments as needed.
references:
- https://attack.mitre.org/software/S0521/
- https://thedfirreport.com/?s=bloodhound
- https://github.com/BloodHoundAD/BloodHound/tree/master/Collectors
- https://github.com/BloodHoundAD/SharpHound3
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1059.001/T1059.001.md#atomic-test-2---run-bloodhound-from-local-disk
tags:
analytic_story:
- Discovery Techniques
- Ransomware
automated_detection_testing: passed
confidence: 80
context:
- Source:Endpoint
- Stage:Discovery
dataset:
- https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1059.001/sharphound/windows-sysmon.log
impact: 30
kill_chain_phases:
- Reconnaissance
message: Possible SharpHound command-Line arguments identified on $dest$
mitre_attack_id:
- T1087.002
- T1069.001
- T1482
- T1087.001
- T1087
- T1069.002
- T1069
observable:
- name: dest
type: Endpoint
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
required_fields:
- _time
- Processes.dest
- Processes.user
- Processes.parent_process
- Processes.process_name
- Processes.process
- Processes.process_id
- Processes.parent_process_id
risk_score: 24
security_domain: endpoint