mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
P4T12ICK
85 lines
3.3 KiB
YAML
85 lines
3.3 KiB
YAML
name: Detect SharpHound Usage
|
|
id: dd04b29a-beed-11eb-87bc-acde48001122
|
|
version: 2
|
|
date: '2021-05-27'
|
|
author: Michael Haag, Splunk
|
|
type: TTP
|
|
datamodel:
|
|
- Endpoint
|
|
description: The following analytic identifies SharpHound binary usage by using the
|
|
original filena,e. In addition to renaming the PE, other coverage is available to
|
|
detect command-line arguments. This particular analytic looks for the original_file_name
|
|
of `SharpHound.exe` and the process name. It is possible older instances of SharpHound.exe
|
|
have different original filenames. Dependent upon the operator, the code may be
|
|
re-compiled and the attributes removed or changed to anything else. During triage,
|
|
review the metadata of the binary in question. Review parallel processes for suspicious
|
|
behavior. Identify the source of this binary.
|
|
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
|
|
as lastTime from datamodel=Endpoint.Processes where (Processes.process_name=sharphound.exe
|
|
OR Processes.original_file_name=SharpHound.exe) by Processes.dest Processes.user
|
|
Processes.parent_process_name Processes.original_file_name 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_usage_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. In addition,
|
|
confirm the latest CIM App 4.20 or higher is installed and the latest TA for the
|
|
endpoint product.
|
|
known_false_positives: False positives should be limited as this is specific to a
|
|
file attribute not used by anything else. Filter 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
|
|
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: Potential SharpHound binary 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_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: 24
|
|
security_domain: endpoint
|
|
supported_tas:
|
|
- Splunk_TA_microsoft_sysmon
|
|
asset_type: Endpoint
|