Files
splunk-security_content/detections/endpoint/icacls_grant_command.yml
2023-09-15 10:58:38 -07:00

76 lines
3.2 KiB
YAML

name: ICACLS Grant Command
id: b1b1e316-accc-11eb-a9b4-acde48001122
version: 1
date: '2023-06-06'
author: Teoderick Contreras, Splunk
status: production
type: TTP
description: This analytic identifies adversaries who manipulate the security permissions
of specific files or directories by granting additional access. This technique is
frequently observed in the tradecraft of Advanced Persistent Threats (APTs) and
coinminer scripts. The objective behind this behavior is to actively evade detection
mechanisms and tightly control access to their associated files. By identifying
these security permission modifications, we can improve our ability to identify
and respond to potential threats, thereby minimizing the impact of malicious activities
on the system.
data_source:
- Sysmon Event ID 1
search: '| tstats `security_content_summariesonly` min(_time) as firstTime max(_time)
as lastTime from datamodel=Endpoint.Processes where Processes.process_name IN( "icacls.exe",
"cacls.exe", "xcacls.exe") AND Processes.process IN ("*/grant*", "*/G*") by Processes.parent_process_name
Processes.parent_process Processes.process_name Processes.process Processes.process_guid
Processes.dest Processes.user | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)` | `icacls_grant_command_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.
known_false_positives: Unknown. Filter as needed.
references:
- https://thedfirreport.com/2020/04/20/sqlserver-or-the-miner-in-the-basement/
tags:
analytic_story:
- XMRig
- Ransomware
asset_type: Endpoint
confidence: 70
impact: 70
message: Process name $process_name$ with grant argument executed by $user$ to change
security permission of a specific file or directory on host $dest$
mitre_attack_id:
- T1222
observable:
- name: dest
type: Endpoint
role:
- Victim
- name: user
type: User
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
required_fields:
- _time
- Processes.parent_process_name
- Processes.process_name
- Processes.dest
- Processes.user
- Processes.process_id
- Processes.process
risk_score: 49
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/malware/xmrig_miner/windows-sysmon.log
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
sourcetype: xmlwineventlog