Local Scheduled Task Creation

  1[metadata]
  2creation_date = "2020/02/18"
  3integration = ["endpoint", "windows"]
  4maturity = "production"
  5updated_date = "2025/02/04"
  6min_stack_version = "8.14.0"
  7min_stack_comments = "Breaking change at 8.14.0 for the Windows Integration."
  8
  9[rule]
 10author = ["Elastic"]
 11description = """
 12Indicates the creation of a scheduled task. Adversaries can use these to establish persistence, move laterally, and/or
 13escalate privileges.
 14"""
 15false_positives = ["Legitimate scheduled tasks may be created during installation of new software."]
 16from = "now-9m"
 17index = ["winlogbeat-*", "logs-endpoint.events.process-*", "logs-windows.sysmon_operational-*"]
 18language = "eql"
 19license = "Elastic License v2"
 20name = "Local Scheduled Task Creation"
 21references = [
 22    "https://www.elastic.co/security-labs/hunting-for-persistence-using-elastic-security-part-1",
 23    "https://www.elastic.co/security-labs/hunting-for-persistence-using-elastic-security-part-2",
 24    "https://www.elastic.co/security-labs/invisible-miners-unveiling-ghostengine",
 25    "https://www.elastic.co/security-labs/elastic-protects-against-data-wiper-malware-targeting-ukraine-hermeticwiper",
 26]
 27risk_score = 21
 28rule_id = "afcce5ad-65de-4ed2-8516-5e093d3ac99a"
 29severity = "low"
 30tags = [
 31    "Domain: Endpoint",
 32    "OS: Windows",
 33    "Use Case: Threat Detection",
 34    "Tactic: Persistence",
 35    "Data Source: Elastic Defend",
 36    "Data Source: Sysmon",
 37    "Resources: Investigation Guide",
 38]
 39type = "eql"
 40
 41query = '''
 42sequence with maxspan=1m
 43  [process where host.os.type == "windows" and event.type == "start" and
 44    ((process.name : ("cmd.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe", "wmic.exe", "mshta.exe",
 45                      "powershell.exe", "pwsh.exe", "powershell_ise.exe", "WmiPrvSe.exe", "wsmprovhost.exe", "winrshost.exe") or
 46    process.pe.original_file_name : ("cmd.exe", "wscript.exe", "rundll32.exe", "regsvr32.exe", "wmic.exe", "mshta.exe",
 47                                     "powershell.exe", "pwsh.dll", "powershell_ise.exe", "WmiPrvSe.exe", "wsmprovhost.exe",
 48                                     "winrshost.exe")) or
 49    ?process.code_signature.trusted == false)] by process.entity_id
 50  [process where host.os.type == "windows" and event.type == "start" and
 51    (process.name : "schtasks.exe" or process.pe.original_file_name == "schtasks.exe") and
 52    process.args : ("/create", "-create") and process.args : ("/RU", "/SC", "/TN", "/TR", "/F", "/XML") and
 53    /* exclude SYSTEM Integrity Level - look for task creations by non-SYSTEM user */
 54    not (?process.Ext.token.integrity_level_name : "System" or ?winlog.event_data.IntegrityLevel : "System")
 55  ] by process.parent.entity_id
 56'''
 57note = """## Triage and analysis
 58
 59> **Disclaimer**:
 60> 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.
 61
 62### Investigating Local Scheduled Task Creation
 63
 64Scheduled tasks in Windows automate routine tasks, but adversaries exploit them for persistence, lateral movement, or privilege escalation. They may use command-line tools like `schtasks.exe` to create tasks under non-system accounts. The detection rule identifies suspicious task creation by monitoring specific processes and command-line arguments, excluding those initiated by system-level users, to flag potential misuse.
 65
 66### Possible investigation steps
 67
 68- Review the process entity ID to identify the parent process that initiated the scheduled task creation. This can provide context on whether the task was created by a legitimate application or a potentially malicious one.
 69- Examine the command-line arguments used with schtasks.exe, specifically looking for unusual or suspicious parameters that might indicate malicious intent, such as unexpected task names or execution paths.
 70- Check the user account associated with the task creation to determine if it is a non-system account and assess whether this account should have the capability to create scheduled tasks.
 71- Investigate the integrity level of the process to confirm it is not running with elevated privileges, which could indicate an attempt to bypass security controls.
 72- Correlate the event with other recent activities on the host, such as file modifications or network connections, to identify any patterns or additional indicators of compromise.
 73- Review the code signature of the initiating process to determine if it is trusted or untrusted, which can help assess the legitimacy of the process creating the task.
 74
 75### False positive analysis
 76
 77- Scheduled tasks created by legitimate administrative tools or scripts may trigger false positives. Users should identify and whitelist these known benign processes to prevent unnecessary alerts.
 78- Routine maintenance tasks initiated by IT departments, such as software updates or system checks, can be mistaken for suspicious activity. Exclude these tasks by specifying their unique process names or command-line arguments.
 79- Tasks created by trusted third-party applications for legitimate purposes might be flagged. Review and exclude these applications by verifying their code signatures and adding them to an exception list.
 80- Automated tasks set up by non-system accounts for regular operations, like backups or monitoring, can be misinterpreted. Document these tasks and exclude them based on their specific parameters or user accounts involved.
 81- Consider excluding tasks with a consistent and verified schedule that aligns with organizational policies, as these are less likely to be malicious.
 82
 83### Response and remediation
 84
 85- Immediately isolate the affected system from the network to prevent potential lateral movement by the adversary.
 86- Terminate any suspicious scheduled tasks identified by the alert using Task Scheduler or command-line tools like schtasks.exe to stop further execution.
 87- Review and remove any unauthorized scheduled tasks created by non-system accounts to eliminate persistence mechanisms.
 88- Conduct a thorough scan of the affected system using updated antivirus or endpoint detection and response (EDR) tools to identify and remove any additional malicious artifacts.
 89- Analyze the user account involved in the task creation for signs of compromise, and reset credentials if necessary to prevent further unauthorized access.
 90- Escalate the incident to the security operations center (SOC) or incident response team for further investigation and to determine if additional systems are affected.
 91- Implement enhanced monitoring and logging for scheduled task creation events to detect similar threats in the future, ensuring alerts are configured to notify the appropriate teams promptly."""
 92
 93
 94[[rule.threat]]
 95framework = "MITRE ATT&CK"
 96[[rule.threat.technique]]
 97id = "T1053"
 98name = "Scheduled Task/Job"
 99reference = "https://attack.mitre.org/techniques/T1053/"
100[[rule.threat.technique.subtechnique]]
101id = "T1053.005"
102name = "Scheduled Task"
103reference = "https://attack.mitre.org/techniques/T1053/005/"
104
105
106
107[rule.threat.tactic]
108id = "TA0003"
109name = "Persistence"
110reference = "https://attack.mitre.org/tactics/TA0003/"