mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
Bhavin Patel
73 lines
3.2 KiB
YAML
73 lines
3.2 KiB
YAML
name: Fsutil Zeroing File
|
|
id: 4e5e024e-fabb-11eb-8b8f-acde48001122
|
|
version: 2
|
|
date: '2024-05-20'
|
|
author: Teoderick Contreras, Splunk
|
|
status: production
|
|
type: TTP
|
|
description: The following analytic detects the execution of the 'fsutil' command
|
|
with the 'setzerodata' parameter, which zeros out a target file. This detection
|
|
leverages data from Endpoint Detection and Response (EDR) agents, focusing on process
|
|
names and command-line arguments. This activity is significant because it is a technique
|
|
used by ransomware, such as LockBit, to evade detection by erasing its malware path
|
|
after encrypting the host. If confirmed malicious, this action could hinder forensic
|
|
investigations and allow attackers to cover their tracks, complicating incident
|
|
response efforts.
|
|
data_source:
|
|
- Sysmon EventID 1
|
|
search: '| tstats `security_content_summariesonly` count values(Processes.process)
|
|
as process values(Processes.parent_process) as parent_process min(_time) as firstTime
|
|
max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name=fsutil.exe
|
|
Processes.process="*setzerodata*" by Processes.user Processes.process_name Processes.parent_process_name
|
|
Processes.dest Processes.process Processes.parent_process | `drop_dm_object_name(Processes)`
|
|
| `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `fsutil_zeroing_file_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
|
|
references:
|
|
- https://app.any.run/tasks/e0ac072d-58c9-4f53-8a3b-3e491c7ac5db/
|
|
- https://news.sophos.com/en-us/2020/04/24/lockbit-ransomware-borrows-tricks-to-keep-up-with-revil-and-maze/
|
|
tags:
|
|
analytic_story:
|
|
- Ransomware
|
|
- LockBit Ransomware
|
|
asset_type: Endpoint
|
|
confidence: 90
|
|
impact: 60
|
|
message: Possible file data deletion on $dest$ using $process$
|
|
mitre_attack_id:
|
|
- T1070
|
|
observable:
|
|
- name: dest
|
|
type: Endpoint
|
|
role:
|
|
- Victim
|
|
product:
|
|
- Splunk Enterprise
|
|
- Splunk Enterprise Security
|
|
- Splunk Cloud
|
|
required_fields:
|
|
- _time
|
|
- Processes.user
|
|
- Processes.process_name
|
|
- Processes.parent_process_name
|
|
- Processes.dest
|
|
- Processes.process
|
|
- Processes.parent_process
|
|
risk_score: 54
|
|
security_domain: endpoint
|
|
tests:
|
|
- name: True Positive Test
|
|
attack_data:
|
|
- data:
|
|
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1070/fsutil_file_zero/windows-sysmon.log
|
|
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
|
|
sourcetype: xmlwineventlog
|