Files
splunk-security_content/dev/endpoint/windows_ngrok_reverse_proxy_usage.yml
T
2023-01-20 13:24:15 +01:00

78 lines
2.4 KiB
YAML

name: Windows Ngrok Reverse Proxy Usage
id: e2549f2c-0aef-408a-b0c1-e0f270623436
version: 1
date: '2022-11-16'
author: Michael Haag, Splunk
status: production
type: Anomaly
description: The following analytic identifies the use of ngrok.exe being utilized
on the Windows operating system. Unfortunately, there is no original file name for
Ngrok, so it may be worth an additional hunt to identify any command-line arguments.
The sign of someone using Ngrok is not malicious, however, more recenctly it has
become an adversary tool.
data_source:
- Sysmon Event ID 1
search:
selection1:
CommandLine:
- '*start*'
- '*--config*'
- '*http*'
- '*authtoken*'
- '*http*'
- (*tcp*
Image|endswith: ngrok.exe
condition: selection1
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 will be present based on organizations that
allow the use of Ngrok. Filter or monitor as needed.
references:
- https://www.cisa.gov/uscert/sites/default/files/publications/aa22-320a_joint_csa_iranian_government-sponsored_apt_actors_compromise_federal%20network_deploy_crypto%20miner_credential_harvester.pdf
tags:
analytic_story:
- Reverse Network Proxy
- CISA AA22-320A
asset_type: Endpoint
confidence: 100
impact: 50
message: A reverse proxy was identified spawning from $parent_process_name$ - $process_name$
on endpoint $dest$ by user $user$.
mitre_attack_id:
- T1572
- T1090
- T1102
observable:
- name: user
type: User
role:
- Victim
- name: dest
type: Hostname
role:
- Victim
- name: parent_process_name
type: Process
role:
- Parent Process
- name: process_name
type: Process
role:
- Child Process
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
risk_score: 50
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1572/ngrok/windows-sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog
update_timestamp: true