Shell Execution via Elastic Endpoint

  1[metadata]
  2creation_date = "2026/07/02"
  3integration = ["endpoint", "sentinel_one_cloud_funnel"]
  4maturity = "production"
  5updated_date = "2026/07/02"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10This rule detects shell executions via Elastic Endpoint. Elastic Endpoint has a built-in response action
 11console that can be used to execute shell commands on compromised systems.
 12"""
 13from = "now-9m"
 14index = [
 15    "logs-endpoint.events.process*",
 16    "logs-sentinel_one_cloud_funnel.*",
 17]
 18language = "eql"
 19license = "Elastic License v2"
 20name = "Shell Execution via Elastic Endpoint"
 21risk_score = 21
 22rule_id = "ef35b103-7fca-4af4-879d-a7e73c918659"
 23setup = """## Setup
 24
 25This rule requires data coming in from Elastic Defend.
 26
 27### Elastic Defend Integration Setup
 28Elastic 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.
 29
 30#### Prerequisite Requirements:
 31- Fleet is required for Elastic Defend.
 32- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
 33
 34#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
 35- Go to the Kibana home page and click "Add integrations".
 36- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
 37- Click "Add Elastic Defend".
 38- Configure the integration name and optionally add a description.
 39- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
 40- 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).
 41- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
 42- 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.
 43For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
 44- Click "Save and Continue".
 45- 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.
 46For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
 47"""
 48severity = "low"
 49tags = [
 50    "Domain: Endpoint",
 51    "OS: Linux",
 52    "Use Case: Threat Detection",
 53    "Tactic: Command and Control",
 54    "Tactic: Defense Evasion",
 55    "Tactic: Execution",
 56    "Data Source: Elastic Defend",
 57    "Data Source: SentinelOne",
 58]
 59timestamp_override = "event.ingested"
 60type = "eql"
 61query = '''
 62process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "start") and
 63process.parent.executable == "/opt/Elastic/Endpoint/elastic-endpoint" and
 64process.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and
 65process.args in ("-c", "-cl", "-lc", "--command")
 66'''
 67
 68[[rule.threat]]
 69framework = "MITRE ATT&CK"
 70
 71  [rule.threat.tactic]
 72  name = "Command and Control"
 73  id = "TA0011"
 74  reference = "https://attack.mitre.org/tactics/TA0011/"
 75
 76  [[rule.threat.technique]]
 77  name = "Remote Access Tools"
 78  id = "T1219"
 79  reference = "https://attack.mitre.org/techniques/T1219/"
 80
 81[[rule.threat]]
 82framework = "MITRE ATT&CK"
 83
 84  [rule.threat.tactic]
 85  name = "Defense Evasion"
 86  id = "TA0005"
 87  reference = "https://attack.mitre.org/tactics/TA0005/"
 88
 89    [[rule.threat.technique]]
 90    id = "T1218"
 91    name = "System Binary Proxy Execution"
 92    reference = "https://attack.mitre.org/techniques/T1218/"
 93
 94[[rule.threat]]
 95framework = "MITRE ATT&CK"
 96
 97  [rule.threat.tactic]
 98  name = "Execution"
 99  id = "TA0002"
100  reference = "https://attack.mitre.org/tactics/TA0002/"
101
102  [[rule.threat.technique]]
103  id = "T1059"
104  name = "Command and Scripting Interpreter"
105  reference = "https://attack.mitre.org/techniques/T1059/"
106
107    [[rule.threat.technique.subtechnique]]
108    name = "Unix Shell"
109    id = "T1059.004"
110    reference = "https://attack.mitre.org/techniques/T1059/004/"