Kernel Module Load via insmod

  1[metadata]
  2creation_date = "2022/07/11"
  3integration = ["endpoint", "auditd_manager"]
  4maturity = "production"
  5min_stack_comments = "New fields added: required_fields, related_integrations, setup"
  6min_stack_version = "8.3.0"
  7updated_date = "2024/02/21"
  8
  9[transform]
 10[[transform.osquery]]
 11label = "Osquery - Retrieve all Kernel Modules"
 12query = "SELECT * FROM kernel_modules"
 13
 14[[transform.osquery]]
 15label = "Osquery - Retrieve Running Processes by User"
 16query = "SELECT pid, username, name FROM processes p JOIN users u ON u.uid = p.uid ORDER BY username"
 17
 18[[transform.osquery]]
 19label = "Osquery - Retrieve Listening Ports"
 20query = "SELECT pid, address, port, socket, protocol, path FROM listening_ports"
 21
 22[[transform.osquery]]
 23label = "Osquery - Retrieve Open Sockets"
 24query = "SELECT pid, family, remote_address, remote_port, socket, state FROM process_open_sockets"
 25
 26[[transform.osquery]]
 27label = "Osquery - Retrieve Information for a Specific User"
 28query = "SELECT * FROM users WHERE username = {{user.name}}"
 29
 30[[transform.osquery]]
 31label = "Osquery - Investigate the Account Authentication Status"
 32query = "SELECT * FROM logged_in_users WHERE user = {{user.name}}"
 33
 34[rule]
 35author = ["Elastic"]
 36description = """
 37Detects the use of the insmod binary to load a Linux kernel object file. Threat actors can use this binary, given they
 38have root privileges, to load a rootkit on a system providing them with complete control and the ability to hide from
 39security products. Manually loading a kernel module in this manner should not be at all common and can indicate
 40suspcious or malicious behavior.
 41"""
 42from = "now-9m"
 43index = ["logs-endpoint.events.*", "endgame-*", "auditbeat-*", "logs-auditd_manager.auditd-*"]
 44language = "eql"
 45license = "Elastic License v2"
 46name = "Kernel Module Load via insmod"
 47note = """## Triage and analysis
 48
 49### Investigating Kernel module load via insmod
 50
 51The insmod binary is a Linux utility that allows users with root privileges to load kernel modules, which are object files that extend the functionality of the kernel. 
 52
 53Threat actors can abuse this utility to load rootkits, granting them full control over the system and the ability to evade security products.
 54
 55The detection rule 'Kernel module load via insmod' is designed to identify instances where the insmod binary is used to load a kernel object file (with a .ko extension) on a Linux system. This activity is uncommon and may indicate suspicious or malicious behavior.
 56
 57> **Note**:
 58> 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.
 59> 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.
 60
 61### Possible investigation steps
 62
 63- Investigate the kernel object file that was loaded via insmod.
 64  - $osquery_1
 65- 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.
 66  - $osquery_2
 67- Investigate the kernel ring buffer for any warnings or messages, such as tainted or out-of-tree kernel module loads through `dmesg`.
 68- Investigate syslog for any unusual segfaults or other messages. Rootkits may be installed on targets with different architecture as expected, and could potentially cause segmentation faults. 
 69- Investigate other alerts associated with the user/host during the past 48 hours.
 70- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
 71- Investigate whether the altered scripts call other malicious scripts elsewhere on the file system. 
 72  - If scripts or executables were dropped, retrieve the files and determine if they are malicious:
 73    - Use a private sandboxed malware analysis system to perform analysis.
 74      - Observe and collect information about the following activities:
 75        - Attempts to contact external domains and addresses.
 76          - Check if the domain is newly registered or unexpected.
 77          - Check the reputation of the domain or IP address.
 78        - File access, modification, and creation activities.
 79- Investigate abnormal behaviors by the subject process/user such as network connections, file modifications, and any other spawned child processes.
 80  - Investigate listening ports and open sockets to look for potential command and control traffic or data exfiltration.
 81    - $osquery_3
 82    - $osquery_4
 83  - Identify the user account that performed the action, analyze it, and check whether it should perform this kind of action.
 84    - $osquery_5
 85- Investigate whether the user is currently logged in and active.
 86    - $osquery_6
 87
 88### False positive analysis
 89
 90- If this activity is related to new benign software installation activity, consider adding exceptions — preferably with a combination of user and command line conditions.
 91- If this activity is related to a system administrator who uses cron jobs for administrative purposes, consider adding exceptions for this specific administrator user account. 
 92- 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.
 93
 94### Related Rules
 95
 96- Kernel Driver Load - 3e12a439-d002-4944-bc42-171c0dcb9b96
 97- Tainted Out-Of-Tree Kernel Module Load - 51a09737-80f7-4551-a3be-dac8ef5d181a
 98- Tainted Kernel Module Load - 05cad2fb-200c-407f-b472-02ea8c9e5e4a
 99- Attempt to Clear Kernel Ring Buffer - 2724808c-ba5d-48b2-86d2-0002103df753
100- Enumeration of Kernel Modules via Proc - 80084fa9-8677-4453-8680-b891d3c0c778
101- Suspicious Modprobe File Event - 40ddbcc8-6561-44d9-afc8-eefdbfe0cccd
102- Kernel Module Removal - cd66a5af-e34b-4bb0-8931-57d0a043f2ef
103- Enumeration of Kernel Modules - 2d8043ed-5bda-4caf-801c-c1feb7410504
104
105### Response and Remediation
106
107- Initiate the incident response process based on the outcome of the triage.
108- Isolate the involved host to prevent further post-compromise behavior.
109- If the triage identified malware, search the environment for additional compromised hosts.
110  - Implement temporary network rules, procedures, and segmentation to contain the malware.
111  - Stop suspicious processes.
112  - Immediately block the identified indicators of compromise (IoCs).
113  - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
114- 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.
115- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
116- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
117- Leverage the incident response data and logging to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
118"""
119references = [
120    "https://decoded.avast.io/davidalvarez/linux-threat-hunting-syslogk-a-kernel-rootkit-found-under-development-in-the-wild/"
121]
122risk_score = 47
123rule_id = "2339f03c-f53f-40fa-834b-40c5983fc41f"
124setup = """## Setup
125
126This rule requires data coming in from Elastic Defend.
127
128### Elastic Defend Integration Setup
129Elastic 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.
130
131#### Prerequisite Requirements:
132- Fleet is required for Elastic Defend.
133- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
134
135#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
136- Go to the Kibana home page and click "Add integrations".
137- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
138- Click "Add Elastic Defend".
139- Configure the integration name and optionally add a description.
140- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
141- 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).
142- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
143- 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.
144For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
145- Click "Save and Continue".
146- 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.
147For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
148"""
149severity = "medium"
150tags = [
151        "Domain: Endpoint",
152        "OS: Linux",
153        "Use Case: Threat Detection",
154        "Tactic: Persistence",
155        "Threat: Rootkit",
156        "Data Source: Elastic Endgame",
157        "Data Source: Elastic Defend",
158        "Data Source: Auditd Manager"
159        ]
160timestamp_override = "event.ingested"
161type = "eql"
162query = '''
163process where host.os.type == "linux" and event.type == "start" and process.name == "insmod" and process.args : "*.ko"
164'''
165
166[[rule.threat]]
167framework = "MITRE ATT&CK"
168
169[[rule.threat.technique]]
170id = "T1547"
171name = "Boot or Logon Autostart Execution"
172reference = "https://attack.mitre.org/techniques/T1547/"
173
174[[rule.threat.technique.subtechnique]]
175id = "T1547.006"
176name = "Kernel Modules and Extensions"
177reference = "https://attack.mitre.org/techniques/T1547/006/"
178
179[rule.threat.tactic]
180id = "TA0003"
181name = "Persistence"
182reference = "https://attack.mitre.org/tactics/TA0003/"