Potential Reverse Shell via UDP

  1[metadata]
  2creation_date = "2023/07/04"
  3integration = ["auditd_manager"]
  4maturity = "production"
  5updated_date = "2024/05/21"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10This detection rule identifies suspicious network traffic patterns associated with UDP reverse shell activity. This
 11activity consists of a sample of an execve, socket and connect syscall executed by the same process, where the
 12auditd.data.a0-1 indicate a UDP connection, ending with an egress connection event. An attacker may establish a Linux
 13UDP reverse shell to bypass traditional firewall restrictions and gain remote access to a target system covertly.
 14"""
 15from = "now-9m"
 16index = ["auditbeat-*", "logs-auditd_manager.auditd-*"]
 17language = "eql"
 18license = "Elastic License v2"
 19name = "Potential Reverse Shell via UDP"
 20references = [
 21    "https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Reverse%20Shell%20Cheatsheet.md",
 22]
 23risk_score = 47
 24rule_id = "a5eb21b7-13cc-4b94-9fe2-29bb2914e037"
 25setup = """## Setup
 26
 27This rule requires data coming in from one of the following integrations:
 28- Auditbeat
 29- Auditd Manager
 30
 31### Auditbeat Setup
 32Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
 33
 34#### The following steps should be executed in order to add the Auditbeat on a Linux System:
 35- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
 36- To install the APT and YUM repositories follow the setup instructions in this [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html).
 37- To run Auditbeat on Docker follow the setup instructions in the [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html).
 38- To run Auditbeat on Kubernetes follow the setup instructions in the [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html).
 39- For complete “Setup and Run Auditbeat” information refer to the [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html).
 40
 41### Auditd Manager Integration Setup
 42The Auditd Manager Integration receives audit events from the Linux Audit Framework which is a part of the Linux kernel.
 43Auditd Manager provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system.
 44
 45#### The following steps should be executed in order to add the Elastic Agent System integration "auditd_manager" on a Linux System:
 46- Go to the Kibana home page and click “Add integrations”.
 47- In the query bar, search for “Auditd Manager” and select the integration to see more details about it.
 48- Click “Add Auditd Manager”.
 49- Configure the integration name and optionally add a description.
 50- Review optional and advanced settings accordingly.
 51- Add the newly installed “auditd manager” to an existing or a new agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
 52- Click “Save and Continue”.
 53- For more details on the integration refer to the [helper guide](https://docs.elastic.co/integrations/auditd_manager).
 54
 55#### Rule Specific Setup Note
 56Auditd Manager subscribes to the kernel and receives events as they occur without any additional configuration.
 57However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
 58- For this detection rule no additional audit rules are required to be added to the integration.
 59"""
 60severity = "medium"
 61tags = [
 62    "Data Source: Auditd Manager",
 63    "Domain: Endpoint",
 64    "OS: Linux",
 65    "Use Case: Threat Detection",
 66    "Tactic: Execution",
 67]
 68timestamp_override = "event.ingested"
 69type = "eql"
 70
 71query = '''
 72sample by host.id, process.pid, process.parent.pid
 73  [process where host.os.type == "linux" and event.type == "start" and event.action == "executed" and process.name : (
 74    "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "perl", "python*", "nc", "ncat", "netcat", "php*",
 75    "ruby", "openssl", "awk", "telnet", "lua*", "socat"
 76    )]
 77  [process where host.os.type == "linux" and auditd.data.syscall == "socket" and process.name : (
 78    "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "perl", "python*", "nc", "ncat", "netcat", "php*",
 79    "ruby", "openssl", "awk", "telnet", "lua*", "socat"
 80    ) and auditd.data.a1 == "2"]
 81  [network where host.os.type == "linux" and event.type == "start" and event.action == "connected-to" and
 82   process.name : (
 83    "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "perl", "python*", "nc", "ncat", "netcat", "php*",
 84    "ruby", "openssl", "awk", "telnet", "lua*", "socat"
 85    ) and network.direction == "egress" and destination.ip != null and
 86   not cidrmatch(destination.ip, "127.0.0.0/8", "169.254.0.0/16", "224.0.0.0/4", "::1")]
 87'''
 88
 89
 90[[rule.threat]]
 91framework = "MITRE ATT&CK"
 92[[rule.threat.technique]]
 93id = "T1059"
 94name = "Command and Scripting Interpreter"
 95reference = "https://attack.mitre.org/techniques/T1059/"
 96[[rule.threat.technique.subtechnique]]
 97id = "T1059.004"
 98name = "Unix Shell"
 99reference = "https://attack.mitre.org/techniques/T1059/004/"
100
101
102
103[rule.threat.tactic]
104id = "TA0002"
105name = "Execution"
106reference = "https://attack.mitre.org/tactics/TA0002/"
107[[rule.threat]]
108framework = "MITRE ATT&CK"
109[[rule.threat.technique]]
110id = "T1071"
111name = "Application Layer Protocol"
112reference = "https://attack.mitre.org/techniques/T1071/"
113
114
115[rule.threat.tactic]
116id = "TA0011"
117name = "Command and Control"
118reference = "https://attack.mitre.org/tactics/TA0011/"