Potential Linux Tunneling and/or Port Forwarding

  1[metadata]
  2creation_date = "2023/08/23"
  3integration = ["endpoint", "crowdstrike", "sentinel_one_cloud_funnel"]
  4maturity = "production"
  5min_stack_version = "8.13.0"
  6min_stack_comments = "Breaking change at 8.13.0 for SentinelOne Integration."
  7updated_date = "2025/01/15"
  8
  9[transform]
 10[[transform.osquery]]
 11label = "Osquery - Retrieve Listening Ports"
 12query = "SELECT pid, address, port, socket, protocol, path FROM listening_ports"
 13
 14[[transform.osquery]]
 15label = "Osquery - Retrieve Open Sockets"
 16query = "SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"
 17
 18[[transform.osquery]]
 19label = "Osquery - Retrieve Information for a Specific User"
 20query = "SELECT * FROM users WHERE username = {{user.name}}"
 21
 22[[transform.osquery]]
 23label = "Osquery - Investigate the Account Authentication Status"
 24query = "SELECT * FROM logged_in_users WHERE user = {{user.name}}"
 25
 26[[transform.osquery]]
 27label = "Osquery - Retrieve Running Processes by User"
 28query = "SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"
 29
 30[[transform.osquery]]
 31label = "Osquery - Retrieve Process Info"
 32query = "SELECT name, cmdline, parent, path, uid FROM processes"
 33
 34
 35[rule]
 36author = ["Elastic"]
 37description = """
 38This rule monitors for a set of Linux utilities that can be used for tunneling and port forwarding. Attackers can
 39leverage tunneling and port forwarding techniques to bypass network defenses, establish hidden communication channels,
 40and gain unauthorized access to internal resources, facilitating data exfiltration, lateral movement, and remote
 41control.
 42"""
 43from = "now-9m"
 44index = ["logs-endpoint.events.*", "endgame-*", "logs-crowdstrike.fdr*", "logs-sentinel_one_cloud_funnel.*"]
 45language = "eql"
 46license = "Elastic License v2"
 47name = "Potential Linux Tunneling and/or Port Forwarding"
 48note = """## Triage and analysis
 49
 50### Investigating Potential Linux Tunneling and/or Port Forwarding
 51
 52Attackers can leverage many utilities to clandestinely tunnel network communications and evade security measures, potentially gaining unauthorized access to sensitive systems.
 53
 54This rule looks for several utilities that are capable of setting up tunnel network communications by analyzing process names or command line arguments. 
 55
 56> **Note**:
 57> This investigation guide uses the [Osquery Markdown Plugin](https://www.elastic.co/guide/en/security/master/invest-guide-run-osquery.html) introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
 58> This investigation guide uses [placeholder fields](https://www.elastic.co/guide/en/security/current/osquery-placeholder-fields.html) to dynamically pass alert data into Osquery queries. Placeholder fields were introduced in Elastic Stack version 8.7.0. If you're using Elastic Stack version 8.6.0 or earlier, you'll need to manually adjust this investigation guide's queries to ensure they properly run.
 59
 60#### Possible investigation steps
 61
 62- Identify any signs of suspicious network activity or anomalies that may indicate protocol tunneling. This could include unexpected traffic patterns or unusual network behavior.
 63  - Investigate listening ports and open sockets to look for potential protocol tunneling, reverse shells, or data exfiltration.
 64    - $osquery_0
 65    - $osquery_1
 66- Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
 67  - $osquery_2
 68- Investigate whether the user is currently logged in and active.
 69  - $osquery_3
 70- Investigate the script execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence and whether they are located in expected locations.
 71  - $osquery_4
 72  - $osquery_5
 73- Investigate other alerts associated with the user/host during the past 48 hours.
 74  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
 75    - Use a private sandboxed malware analysis system to perform analysis.
 76      - Observe and collect information about the following activities:
 77        - Attempts to contact external domains and addresses.
 78          - Check if the domain is newly registered or unexpected.
 79          - Check the reputation of the domain or IP address.
 80        - File access, modification, and creation activities.
 81
 82### Related rules
 83
 84- Potential Protocol Tunneling via Chisel Client - 3f12325a-4cc6-410b-8d4c-9fbbeb744cfd
 85- Potential Protocol Tunneling via Chisel Server - ac8805f6-1e08-406c-962e-3937057fa86f
 86- Potential Protocol Tunneling via EarthWorm - 9f1c4ca3-44b5-481d-ba42-32dc215a2769
 87- Suspicious Utility Launched via ProxyChains - 6ace94ba-f02c-4d55-9f53-87d99b6f9af4
 88- ProxyChains Activity - 4b868f1f-15ff-4ba3-8c11-d5a7a6356d37
 89
 90### False positive analysis
 91
 92- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
 93- If this activity is related to a system administrator or developer who uses port tunneling/forwarding for benign purposes, consider adding exceptions for specific user accounts or hosts. 
 94- Try to understand the context of the execution by thinking about the user, machine, or business purpose. A small number of endpoints, such as servers with unique software, might appear unusual but satisfy a specific business need.
 95
 96### Response and remediation
 97
 98- Initiate the incident response process based on the outcome of the triage.
 99- Isolate the involved host to prevent further post-compromise behavior.
100- If the triage identified malware, search the environment for additional compromised hosts.
101  - Implement temporary network rules, procedures, and segmentation to contain the malware.
102  - Stop suspicious processes.
103  - Immediately block the identified indicators of compromise (IoCs).
104  - Inspect the affected systems for additional malware backdoors, such as reverse shells, reverse proxies, or droppers, that attackers could use to reinfect the system.
105- Remove and block malicious artifacts identified during triage.
106- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
107- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
108- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
109- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
110"""
111references = [
112    "https://blog.bitsadmin.com/living-off-the-foreign-land-windows-as-offensive-platform",
113    "https://book.hacktricks.xyz/generic-methodologies-and-resources/tunneling-and-port-forwarding",
114]
115risk_score = 47
116rule_id = "6ee947e9-de7e-4281-a55d-09289bdf947e"
117setup = """## Setup
118
119This rule requires data coming in from Elastic Defend.
120
121### Elastic Defend Integration Setup
122Elastic 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.
123
124#### Prerequisite Requirements:
125- Fleet is required for Elastic Defend.
126- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
127
128#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
129- Go to the Kibana home page and click "Add integrations".
130- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
131- Click "Add Elastic Defend".
132- Configure the integration name and optionally add a description.
133- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
134- 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).
135- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
136- 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.
137For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
138- Click "Save and Continue".
139- 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.
140For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
141"""
142severity = "medium"
143tags = [
144    "Domain: Endpoint",
145    "OS: Linux",
146    "Use Case: Threat Detection",
147    "Tactic: Command and Control",
148    "Data Source: Elastic Defend",
149    "Data Source: Elastic Endgame",
150    "Data Source: Crowdstrike",
151    "Data Source: SentinelOne",
152    "Resources: Investigation Guide",
153]
154timestamp_override = "event.ingested"
155type = "eql"
156
157query = '''
158process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "start", "ProcessRollup2") and (
159  (
160    // gost & pivotnacci - spawned without process.parent.name
161    (process.name == "gost" and process.args : ("-L*", "-C*", "-R*")) or (process.name == "pivotnacci")) or (
162    // ssh
163    (process.name in ("ssh", "sshd") and (process.args in ("-R", "-L", "-D", "-w") and process.args_count >= 4 and 
164     not process.args : "chmod")) or
165    // sshuttle
166    (process.name == "sshuttle" and process.args in ("-r", "--remote", "-l", "--listen") and process.args_count >= 4) or
167    // socat
168    (process.name == "socat" and process.args : ("TCP4-LISTEN:*", "SOCKS*") and process.args_count >= 3) or
169    // chisel
170    (process.name : "chisel*" and process.args in ("client", "server")) or
171    // iodine(d), dnscat, hans, ptunnel-ng, ssf, 3proxy & ngrok 
172    (process.name in ("iodine", "iodined", "dnscat", "hans", "hans-ubuntu", "ptunnel-ng", "ssf", "3proxy", "ngrok"))
173  ) and process.parent.name in ("bash", "dash", "ash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")
174)
175'''
176
177
178[[rule.threat]]
179framework = "MITRE ATT&CK"
180[[rule.threat.technique]]
181id = "T1572"
182name = "Protocol Tunneling"
183reference = "https://attack.mitre.org/techniques/T1572/"
184
185
186[rule.threat.tactic]
187id = "TA0011"
188name = "Command and Control"
189reference = "https://attack.mitre.org/tactics/TA0011/"