Detection: Linux Deletion Of Cron Jobs
Description
The following analytic detects the deletion of cron jobs on a Linux machine. It leverages filesystem event logs to identify when files within the "/etc/cron.*" directory are deleted. This activity is significant because attackers or malware may delete cron jobs to disable scheduled security tasks or evade detection mechanisms. If confirmed malicious, this action could allow an attacker to disrupt system operations, evade security measures, or facilitate further malicious activities such as data wiping, as seen with the acidrain malware.
Search
1
2| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime FROM datamodel=Endpoint.Filesystem
3 WHERE Filesystem.action=deleted Filesystem.file_path="/etc/cron.*"
4 BY Filesystem.action Filesystem.dest Filesystem.file_access_time
5 Filesystem.file_create_time Filesystem.file_hash Filesystem.file_modify_time
6 Filesystem.file_name Filesystem.file_path Filesystem.file_acl
7 Filesystem.file_size Filesystem.process_guid Filesystem.process_id
8 Filesystem.user Filesystem.vendor_product
9
10| `drop_dm_object_name(Filesystem)`
11
12| `security_content_ctime(firstTime)`
13
14| `security_content_ctime(lastTime)`
15
16| `linux_deletion_of_cron_jobs_filter`
Data Source
Macros Used
| Name |
Value |
| security_content_summariesonly |
summariesonly=summariesonly_config allow_old_summaries=oldsummaries_config fillnull_value=fillnull_config`` |
| linux_deletion_of_cron_jobs_filter |
search * |
linux_deletion_of_cron_jobs_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Annotations
| ID |
Technique |
Tactic |
| T1070.004 |
File Deletion |
Stealth |
| T1485 |
Data Destruction |
Impact |
Actions on Objectives
Exploitation
Default Configuration
This detection is configured by default in Splunk Enterprise Security to run with the following settings:
| Setting |
Value |
| Disabled |
true |
| Cron Schedule |
0 * * * * |
| Earliest Time |
-70m@m |
| Latest Time |
-10m@m |
| Schedule Window |
auto |
| Creates Finding (Notable) |
No |
| Creates Intermediate Finding (Risk Event) |
Yes |
Anomaly detections generate Intermediate Findings (Risk Events). They do not generate a Finding (Notable) directly.
Implementation
To successfully implement this search, you need to be ingesting logs with the process name, parent process, and command-line executions from your endpoints. If you are using Sysmon, you can use the Add-on for Linux Sysmon from Splunkbase.
Known False Positives
Administrator or network operator can execute this command. Please update the filter macros to remove false positives.
Associated Analytic Story
| Message |
Entity Field |
Entity Type |
Risk Score |
| Linux cron jobs are deleted on host $dest$ by process GUID- $process_guid$ |
dest |
system |
20 |
Threat Objects
| Field |
Type |
| file_name |
file_name |
References
Detection Testing
| Test Type |
Status |
Dataset |
Source |
Sourcetype |
| Validation |
✅ Passing |
N/A |
N/A |
N/A |
| Unit |
✅ Passing |
Dataset |
Syslog:Linux-Sysmon/Operational |
sysmon:linux |
| Integration |
✅ Passing |
Dataset |
Syslog:Linux-Sysmon/Operational |
sysmon:linux |
Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI.
Alternatively you can replay a dataset into a Splunk Attack Range
Source: GitHub |
Version: 12