Files
splunk-security_content/docs/_posts/2021-05-27-detect_sharphound_usage.md
2021-11-10 16:16:30 +00:00

5.5 KiB

title, excerpt, categories, last_modified_at, toc, toc_label, tags
title excerpt categories last_modified_at toc toc_label tags
Detect SharpHound Usage Domain Account, Local Groups, Domain Trust Discovery, Local Account, Account Discovery, Domain Groups, Permission Groups Discovery
Endpoint
2021-05-27 true
Domain Account
Discovery
Local Groups
Discovery
Domain Trust Discovery
Discovery
Local Account
Discovery
Account Discovery
Discovery
Domain Groups
Discovery
Permission Groups Discovery
Discovery
Splunk Enterprise
Splunk Enterprise Security
Splunk Cloud
Endpoint

Try in Splunk Security Cloud{: .btn .btn--success}

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.

  • Type: TTP
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
  • Datamodel: Endpoint
  • Last Updated: 2021-05-27
  • Author: Michael Haag, Splunk
  • ID: dd04b29a-beed-11eb-87bc-acde48001122

ATT&CK

ID Technique Tactic
T1087.002 Domain Account Discovery

| T1069.001 | Local Groups | Discovery |

| T1482 | Domain Trust Discovery | Discovery |

| T1087.001 | Local Account | Discovery |

| T1087 | Account Discovery | Discovery |

| T1069.002 | Domain Groups | Discovery |

| T1069 | Permission Groups Discovery | Discovery |


| 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`

Associated Analytic Story

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.

Required field

  • _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

Kill Chain Phase

  • Reconnaissance

Known False Positives

False positives should be limited as this is specific to a file attribute not used by anything else. Filter as needed.

RBA

Risk Score Impact Confidence Message
24.0 30 80 Potential SharpHound binary identified on dest

Reference

Test Dataset

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 2