IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Potential Persistence via Cron Job
editPotential Persistence via Cron Job
editIdentifies the creation or execution of a cron job. Adversaries may abuse cron jobs to perform task scheduling for initial or recurring execution of malicious code.
Rule type: query
Rule indices:
- auditbeat-*
- logs-endpoint.events.*
Severity: low
Risk score: 21
Runs every: 5 minutes
Searches indices from: now-9m (Date Math format, see also Additional look-back time
)
Maximum alerts per execution: 100
References:
Tags:
- Elastic
- Host
- Linux
- macOS
- Threat Detection
- Persistence
Version: 1
Added (Elastic Stack release): 7.12.0
Rule authors: Elastic
Rule license: Elastic License v2
Potential false positives
editLegitimate software or scripts using cron jobs for recurring tasks.
Rule query
editevent.category:process and event.type:(start or process_started or info) and not user.name:root and ((process.name:crontab and not process.args:("-l" or "-r" or "-e" or "-help" or "-h")) or (process.parent.name:cron and not process.name:"running job" and not p rocess.executable:(/Applications/Docker.app/Contents/Resources/bin/doc ker or /usr/bin/killall or /usr/sbin/sendmail or /usr/bin/env or /usr/bin/timeshift or /bin/rm)))
Threat mapping
editFramework: MITRE ATT&CKTM
-
Tactic:
- Name: Persistence
- ID: TA0003
- Reference URL: https://attack.mitre.org/tactics/TA0003/
-
Technique:
- Name: Scheduled Task/Job
- ID: T1053
- Reference URL: https://attack.mitre.org/techniques/T1053/