Files
splunk-security_content/detections/endpoint/detect_remote_access_software_usage_process.yml

96 lines
4.3 KiB
YAML

name: Detect Remote Access Software Usage Process
id: ffd5e001-2e34-48f4-97a2-26dc4bb08178
version: 3
date: '2024-07-09'
author: Steven Dick
status: production
type: Anomaly
description: The following analytic detects the execution of known remote access software
within the environment. It leverages data from Endpoint Detection and Response (EDR)
agents, focusing on process names and parent processes mapped to the Endpoint data
model. This activity is significant as adversaries often use remote access tools
like AnyDesk, GoToMyPC, LogMeIn, and TeamViewer to maintain unauthorized access.
If confirmed malicious, this could allow attackers to control systems remotely,
exfiltrate data, or deploy additional malware, posing a severe threat to the organization's
security.
data_source:
- Sysmon EventID 1
- Windows Event Log Security 4688
- CrowdStrike ProcessRollup2
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
as lastTime values(Processes.parent_process) as parent_process from datamodel=Endpoint.Processes
where Processes.dest!=unknown Processes.process!=unknown by Processes.dest Processes.user
Processes.process_name Processes.process | `security_content_ctime(firstTime)` |
`security_content_ctime(lastTime)` | `drop_dm_object_name(Processes)` | lookup remote_access_software
remote_utility AS process_name OUTPUT isutility, description as signature, comment_reference
as desc, category | search isutility = True | `remote_access_software_usage_exceptions` | `detect_remote_access_software_usage_process_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. The "exceptions" macro leverages
both an Assets and Identities lookup, as well as a KVStore collection called
"remote_software_exceptions" that lets you track and maintain device-
based exceptions for this set of detections.
known_false_positives: It is possible that legitimate remote access software is used
within the environment. Ensure that the lookup is reviewed and updated with any
additional remote access software that is used within the environment.
Known false positives can be added to the remote_access_software_usage_exception.csv
lookup to globally suppress these situations across all remote access content
references:
- https://attack.mitre.org/techniques/T1219/
- https://thedfirreport.com/2022/08/08/bumblebee-roasts-its-way-to-domain-admin/
- https://thedfirreport.com/2022/11/28/emotet-strikes-again-lnk-file-leads-to-domain-wide-ransomware/
tags:
analytic_story:
- Insider Threat
- Command And Control
- Ransomware
- Gozi Malware
asset_type: Endpoint
confidence: 50
impact: 50
message: A process for a known remote access software $process_name$ was identified
on $dest$.
mitre_attack_id:
- T1219
observable:
- name: dest
type: Hostname
role:
- Victim
- name: user
type: User
role:
- Victim
- name: process_name
type: Process
role:
- Attacker
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
required_fields:
- _time
- Processes.dest
- Processes.user
- Processes.process_name
- Processes.process
- Processes.process_id
- Processes.parent_process_name
risk_score: 25
security_domain: endpoint
manual_test: This detection uses A&I lookups from Enterprise Security.
tests:
- name: True Positive Test
attack_data:
- data:
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1219/screenconnect/screenconnect_sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: XmlWinEventLog