
Linux Auditd Possible Append Cronjob Entry On Existing Cronjob File
Splunk Security Content
View SourceSummary
This detection rule targets potential tampering with cronjob files on Linux systems, specifically monitoring for `echo` commands that may append unauthorized entries to existing cron files. The analytic leverages logs generated by Linux Auditd, focusing on crucial parameters like process names and command-line executions. The rationale behind this monitoring stems from the observation that adversaries frequently employ such techniques to establish persistence or escalate privileges within compromised systems. If these actions are determined to be malicious, they could facilitate the automatic execution of unauthorized scripts, ultimately compromising system integrity and data confidentiality. The implementation requires proper ingestion of auditd logs, normalized to adhere to the Splunk CIM, ensuring accurate and efficient detection of unauthorized alterations in cronjob configurations.
Categories
- Linux
- Endpoint
Data Sources
- Pod
- Container
- User Account
- Windows Registry
- Script
- Image
- Web Credential
- Named Pipe
- Certificate
- WMI
- Cloud Storage
- Internet Scan
- Persona
- Group
- Application Log
- Logon Session
- Instance
- Sensor Health
- File
- Drive
- Snapshot
- Command
- Kernel
- Driver
- Volume
- Cloud Service
- Malware Repository
- Network Share
- Network Traffic
- Scheduled Job
- Firmware
- Active Directory
- Service
- Domain Name
- Process
- Firewall
- Module
- Network Traffic
- Scheduled Job
ATT&CK Techniques
- T1053
- T1053.003
Created: 2025-01-20