Ruben Groenewoud
ae3f4737ab
* [Tuning] Linux DR Tuning - Part 6 * Update discovery_dynamic_linker_via_od.toml * Update discovery_esxi_software_via_find.toml * Update discovery_esxi_software_via_grep.toml * Update discovery_linux_hping_activity.toml * Update discovery_linux_nping_activity.toml --------- Co-authored-by: Colson Wilhoit <48036388+DefSecSentinel@users.noreply.github.com>
96 lines
4.3 KiB
TOML
96 lines
4.3 KiB
TOML
[metadata]
|
|
creation_date = "2020/04/23"
|
|
integration = ["endpoint"]
|
|
maturity = "production"
|
|
min_stack_comments = "Multiple field support in the New Terms rule type was added in Elastic 8.6"
|
|
min_stack_version = "8.6.0"
|
|
updated_date = "2024/02/20"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Loadable Kernel Modules (or LKMs) are pieces of code that can be loaded and unloaded into the kernel upon demand. They
|
|
extend the functionality of the kernel without the need to reboot the system. This identifies attempts to enumerate
|
|
information about a kernel module.
|
|
"""
|
|
false_positives = [
|
|
"""
|
|
Security tools and device drivers may run these programs in order to enumerate kernel modules. Use of these programs
|
|
by ordinary users is uncommon. These can be exempted by process name or username.
|
|
""",
|
|
]
|
|
from = "now-9m"
|
|
index = ["logs-endpoint.events.*", "endgame-*"]
|
|
language = "kuery"
|
|
license = "Elastic License v2"
|
|
name = "Enumeration of Kernel Modules"
|
|
risk_score = 47
|
|
rule_id = "2d8043ed-5bda-4caf-801c-c1feb7410504"
|
|
setup = """
|
|
|
|
This rule requires data coming in from Elastic Defend.
|
|
|
|
### Elastic Defend Integration Setup
|
|
Elastic 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.
|
|
|
|
#### Prerequisite Requirements:
|
|
- Fleet is required for Elastic Defend.
|
|
- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
|
|
|
|
#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
|
|
- Go to the Kibana home page and click "Add integrations".
|
|
- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
|
|
- Click "Add Elastic Defend".
|
|
- Configure the integration name and optionally add a description.
|
|
- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
|
|
- 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).
|
|
- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
|
|
- 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.
|
|
For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
|
|
- Click "Save and Continue".
|
|
- 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.
|
|
For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
|
|
|
|
"""
|
|
severity = "medium"
|
|
tags = [
|
|
"Domain: Endpoint",
|
|
"OS: Linux",
|
|
"Use Case: Threat Detection",
|
|
"Tactic: Discovery",
|
|
"Data Source: Elastic Defend",
|
|
"Data Source: Elastic Endgame"
|
|
]
|
|
timestamp_override = "event.ingested"
|
|
type = "new_terms"
|
|
query = '''
|
|
event.category:process and host.os.type:linux and event.action:(exec or exec_event) and event.type:start and (
|
|
(process.name:(lsmod or modinfo)) or
|
|
(process.name:kmod and process.args:list) or
|
|
(process.name:depmod and process.args:(--all or -a))
|
|
) and not process.parent.name:(mkinitramfs or cryptroot or framebuffer or dracut or jem or thin-provisioning-tools
|
|
or readykernel or lvm2 or vz-start or iscsi or mdadm or ovalprobes or bcache or plymouth or dkms or overlayroot or
|
|
weak-modules or zfs)
|
|
'''
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
|
|
[[rule.threat.technique]]
|
|
id = "T1082"
|
|
name = "System Information Discovery"
|
|
reference = "https://attack.mitre.org/techniques/T1082/"
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0007"
|
|
name = "Discovery"
|
|
reference = "https://attack.mitre.org/tactics/TA0007/"
|
|
|
|
[rule.new_terms]
|
|
field = "new_terms_fields"
|
|
value = ["process.parent.command_line", "process.command_line", "host.id"]
|
|
|
|
[[rule.new_terms.history_window_start]]
|
|
field = "history_window_start"
|
|
value = "now-14d"
|