Potential Reverse Shell via UDP

 1[metadata]
 2creation_date = "2023/07/04"
 3integration = ["auditd_manager"]
 4maturity = "production"
 5min_stack_comments = "The sampling feature within EQL was introduced in 8.6.0"
 6min_stack_version = "8.6.0"
 7updated_date = "2023/07/04"
 8
 9[rule]
10author = ["Elastic"]
11description = """
12This detection rule identifies suspicious network traffic patterns associated with UDP reverse shell activity. This 
13activity consists of a sample of an execve, socket and connect syscall executed by the same process, where the
14auditd.data.a0-1 indicate a UDP connection, ending with an egress connection event. An attacker may establish a Linux 
15UDP reverse shell to bypass traditional firewall restrictions and gain remote access to a target system covertly.
16"""
17from = "now-9m"
18index = ["auditbeat-*", "logs-auditd_manager.auditd-*"]
19language = "eql"
20license = "Elastic License v2"
21name = "Potential Reverse Shell via UDP"
22note = """## Setup
23This rule requires the use of the `auditd_manager` integration. `Auditd_manager` is a tool designed to simplify and enhance the management of the audit subsystem in Linux systems. It 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. The following steps should be executed in order to install and deploy `auditd_manager` on a Linux system. 

1`Auditd_manager` subscribes to the kernel and receives events as they occur without any additional configuration. However, 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. 

 1Add the newly installed `auditd manager` to an agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
 2"""
 3references = [
 4    "https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Methodology%20and%20Resources/Reverse%20Shell%20Cheatsheet.md"
 5]
 6risk_score = 47
 7rule_id = "a5eb21b7-13cc-4b94-9fe2-29bb2914e037"
 8severity = "medium"
 9tags = ["OS: Linux", "Use Case: Threat Detection", "Tactic: Execution"]
10timestamp_override = "event.ingested"
11type = "eql"
12query = '''
13sample by host.id, process.pid, process.parent.pid
14[process where host.os.type == "linux" and event.dataset == "auditd_manager.auditd" and 
15 auditd.data.syscall == "execve" and process.name : ("bash", "dash", "sh", "tcsh",
16 "csh", "zsh", "ksh", "fish", "perl", "python*", "nc", "ncat", "netcat", "php*", "ruby",
17 "openssl", "awk", "telnet", "lua*", "socat")]
18[process where host.os.type == "linux" and event.dataset == "auditd_manager.auditd" and 
19 auditd.data.syscall == "socket" and process.name : ("bash", "dash", "sh", "tcsh", "csh",
20 "zsh", "ksh", "fish", "perl", "python*", "nc", "ncat", "netcat", "php*", "ruby", "openssl",
21 "awk", "telnet", "lua*", "socat") and auditd.data.a0 == "2" and auditd.data.a1 : ("2", "802")]
22[network where host.os.type == "linux" and event.dataset == "auditd_manager.auditd" and 
23 auditd.data.syscall == "connect" and process.name : ("bash", "dash", "sh", "tcsh", "csh",
24 "zsh", "ksh", "fish", "perl", "python*", "nc", "ncat", "netcat", "php*", "ruby", "openssl",
25 "awk", "telnet", "lua*", "socat") and network.direction == "egress" and destination.ip != null and 
26 destination.ip != "127.0.0.1" and destination.ip != "127.0.0.53" and destination.ip != "::1"]
27'''
28
29[[rule.threat]]
30framework = "MITRE ATT&CK"
31
32[rule.threat.tactic]
33name = "Execution"
34id = "TA0002"
35reference = "https://attack.mitre.org/tactics/TA0002/"
36
37[[rule.threat.technique]]
38id = "T1059"
39name = "Command and Scripting Interpreter"
40reference = "https://attack.mitre.org/techniques/T1059/"
41
42[[rule.threat.technique.subtechnique]]
43id = "T1059.004"
44name = "Unix Shell"
45reference = "https://attack.mitre.org/techniques/T1059/004/"
46
47[[rule.threat]]
48framework = "MITRE ATT&CK"
49
50[rule.threat.tactic]
51name = "Command and Control"
52id = "TA0011"
53reference = "https://attack.mitre.org/tactics/TA0011/"
54
55[[rule.threat.technique]]
56name = "Application Layer Protocol"
57id = "T1071"
58reference = "https://attack.mitre.org/techniques/T1071/"

1Kibana -->
2Management -->
3Integrations -->
4Auditd Manager -->
5Add Auditd Manager

1For this detection rule no additional audit rules are required to be added to the integration.