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

82 lines
3.7 KiB
YAML

name: Linux Auditd Shred Overwrite Command
id: ce2bde4d-a1d4-4452-8c87-98440e5adfb3
version: 5
date: '2025-05-02'
author: Teoderick Contreras, Splunk
status: production
type: TTP
description: The following analytic detects the execution of the 'shred' command on
a Linux machine, which is used to overwrite files to make them unrecoverable. It
leverages data from Linux Auditd, focusing on process names and command-line arguments.
This activity is significant because the 'shred' command can be used in destructive
attacks, such as those seen in the Industroyer2 malware targeting energy facilities.
If confirmed malicious, this activity could lead to the permanent destruction of
critical files, severely impacting system integrity and data availability.
data_source:
- Linux Auditd Proctitle
search: '`linux_auditd` proctitle IN ("*shred*") AND proctitle IN ("*-n*", "*-z*", "*-u*", "*-s*")
| rename host as dest
| stats count min(_time) as firstTime max(_time) as lastTime by proctitle dest
| `security_content_ctime(firstTime)`
|`security_content_ctime(lastTime)`
| `linux_auditd_shred_overwrite_command_filter`'
how_to_implement: To implement this detection, the process begins by ingesting auditd
data, that consist SYSCALL, TYPE, EXECVE and PROCTITLE events, which captures command-line
executions and process details on Unix/Linux systems. These logs should be ingested
and processed using Splunk Add-on for Unix and Linux (https://splunkbase.splunk.com/app/833),
which is essential for correctly parsing and categorizing the data. The next step
involves normalizing the field names to match the field names set by the Splunk
Common Information Model (CIM) to ensure consistency across different data sources
and enhance the efficiency of data modeling. This approach enables effective monitoring
and detection of linux endpoints where auditd is deployed
known_false_positives: Administrator or network operator can use this application
for automation purposes. Please update the filter macros to remove false positives.
references:
- https://www.welivesecurity.com/2022/04/12/industroyer2-industroyer-reloaded/
- https://cert.gov.ua/article/39518
drilldown_searches:
- name: View the detection results for - "$dest$"
search: '%original_detection_search% | search dest = "$dest$"'
earliest_offset: $info_min_time$
latest_offset: $info_max_time$
- name: View risk events for the last 7 days for - "$dest$"
search: '| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$dest$")
starthoursago=168 | stats count min(_time) as firstTime max(_time) as lastTime
values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories)
as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic)
as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`'
earliest_offset: $info_min_time$
latest_offset: $info_max_time$
rba:
message: A [$proctitle$] event occurred on host - [$dest$] to overwrite files
using the shred utility.
risk_objects:
- field: dest
type: system
score: 81
threat_objects: []
tags:
analytic_story:
- AwfulShred
- Linux Privilege Escalation
- Data Destruction
- Linux Persistence Techniques
- Industroyer2
- Compromised Linux Host
asset_type: Endpoint
mitre_attack_id:
- T1485
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
security_domain: endpoint
tests:
- name: True Positive Test
attack_data:
- data:
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1485/linux_auditd_shred/auditd_proctitle_shred.log
source: auditd
sourcetype: auditd