Suspicious CronTab Creation or Modification

  1[metadata]
  2creation_date = "2022/04/25"
  3integration = ["endpoint"]
  4maturity = "production"
  5updated_date = "2025/03/18"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Identifies attempts to create or modify a crontab via a process that is not crontab (i.e python, osascript, etc.). This
 11activity should not be highly prevalent and could indicate the use of cron as a persistence mechanism by a threat actor.
 12"""
 13from = "now-9m"
 14index = ["logs-endpoint.events.file*"]
 15language = "eql"
 16license = "Elastic License v2"
 17name = "Suspicious CronTab Creation or Modification"
 18references = [
 19    "https://taomm.org/PDFs/vol1/CH%200x02%20Persistence.pdf",
 20    "https://theevilbit.github.io/beyond/beyond_0004/",
 21]
 22risk_score = 47
 23rule_id = "530178da-92ea-43ce-94c2-8877a826783d"
 24setup = """## Setup
 25
 26This rule requires data coming in from Elastic Defend.
 27
 28### Elastic Defend Integration Setup
 29Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 30
 31#### Prerequisite Requirements:
 32- Fleet is required for Elastic Defend.
 33- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
 34
 35#### The following steps should be executed in order to add the Elastic Defend integration on a macOS System:
 36- Go to the Kibana home page and click "Add integrations".
 37- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
 38- Click "Add Elastic Defend".
 39- Configure the integration name and optionally add a description.
 40- Select the type of environment you want to protect, for MacOS it is recommended to select "Traditional Endpoints".
 41- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. [Helper guide](https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html).
 42- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
 43- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
 44For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/current/agent-policy.html).
 45- Click "Save and Continue".
 46- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
 47For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
 48"""
 49severity = "medium"
 50tags = [
 51    "Domain: Endpoint",
 52    "OS: macOS",
 53    "Use Case: Threat Detection",
 54    "Tactic: Persistence",
 55    "Data Source: Elastic Defend",
 56    "Resources: Investigation Guide",
 57]
 58timestamp_override = "event.ingested"
 59type = "eql"
 60
 61query = '''
 62file where host.os.type == "macos" and event.type != "deletion" and process.name != null and
 63  file.path like "/private/var/at/tabs/*" and not process.executable == "/usr/bin/crontab"
 64'''
 65note = """## Triage and analysis
 66
 67> **Disclaimer**:
 68> This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.
 69
 70### Investigating Suspicious CronTab Creation or Modification
 71
 72Cron is a time-based job scheduler in Unix-like operating systems, including macOS, used to automate repetitive tasks. Adversaries may exploit cron to maintain persistence by scheduling malicious scripts or commands. The detection rule identifies unusual crontab modifications by non-standard processes, flagging potential misuse by threat actors seeking to establish persistence.
 73
 74### Possible investigation steps
 75
 76- Review the process name and executable path that triggered the alert to determine if it is a known legitimate application or a potentially malicious one.
 77- Examine the file path "/private/var/at/tabs/*" to identify any recent changes or additions to crontab entries that could indicate unauthorized scheduling of tasks.
 78- Investigate the user account associated with the process to determine if it has a history of legitimate crontab modifications or if it might be compromised.
 79- Check for any related alerts or logs around the same timeframe that might indicate additional suspicious activity or corroborate the use of cron for persistence.
 80- Analyze the command or script scheduled in the crontab entry to assess its purpose and potential impact on the system, looking for signs of malicious intent.
 81
 82### False positive analysis
 83
 84- System maintenance scripts or legitimate administrative tools may modify crontabs using non-standard processes. Review the process name and executable path to determine if the activity is part of routine maintenance.
 85- Development or testing environments might use scripts or automation tools that modify crontabs for legitimate purposes. Identify and document these processes to create exceptions in the detection rule.
 86- Some third-party applications may use cron jobs for updates or scheduled tasks. Verify the legitimacy of these applications and consider excluding their processes if they are known and trusted.
 87- User-initiated scripts that automate personal tasks could trigger this rule. Educate users on the implications of using cron for personal automation and establish a process for approving such scripts.
 88- Regularly review and update the list of excluded processes to ensure that only verified and non-threatening activities are exempt from detection.
 89
 90### Response and remediation
 91
 92- Immediately isolate the affected macOS system from the network to prevent potential lateral movement or further execution of malicious tasks.
 93- Terminate any suspicious processes identified as modifying the crontab, especially those not typically associated with crontab modifications, such as python or osascript.
 94- Review and remove any unauthorized or suspicious entries in the crontab file located at /private/var/at/tabs/* to eliminate persistence mechanisms established by the threat actor.
 95- Conduct a thorough scan of the system using updated antivirus or endpoint detection and response (EDR) tools to identify and remove any additional malware or malicious scripts.
 96- Restore the system from a known good backup if the integrity of the system is in question and ensure all security patches and updates are applied.
 97- Escalate the incident to the security operations center (SOC) or incident response team for further analysis and to determine if additional systems are affected.
 98- Implement enhanced monitoring and logging for crontab modifications and related processes to detect and respond to similar threats in the future."""
 99
100
101[[rule.threat]]
102framework = "MITRE ATT&CK"
103[[rule.threat.technique]]
104id = "T1053"
105name = "Scheduled Task/Job"
106reference = "https://attack.mitre.org/techniques/T1053/"
107[[rule.threat.technique.subtechnique]]
108id = "T1053.003"
109name = "Cron"
110reference = "https://attack.mitre.org/techniques/T1053/003/"
111
112
113
114[rule.threat.tactic]
115id = "TA0003"
116name = "Persistence"
117reference = "https://attack.mitre.org/tactics/TA0003/"