Ruben Groenewoud
d5dee5a6c8
* [New Rules] sysctl and modprobe enumeration * Update discovery_linux_modprobe_enumeration.toml * Update discovery_linux_sysctl_enumeration.toml * reverted manifest/schema update * updated tags * Update discovery_linux_modprobe_enumeration.toml
67 lines
3.0 KiB
TOML
67 lines
3.0 KiB
TOML
[metadata]
|
|
creation_date = "2023/06/08"
|
|
integration = ["auditd_manager"]
|
|
maturity = "production"
|
|
min_stack_comments = "New fields added: required_fields, related_integrations, setup"
|
|
min_stack_version = "8.3.0"
|
|
updated_date = "2023/07/06"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Detects file events involving kernel modules in modprobe configuration files, which may indicate unauthorized
|
|
access or manipulation of critical kernel modules. Attackers may tamper with the modprobe files to load malicious or
|
|
unauthorized kernel modules, potentially bypassing security measures, escalating privileges, or hiding their activities
|
|
within the system.
|
|
"""
|
|
from = "now-9m"
|
|
index = ["auditbeat-*", "logs-auditd_manager.auditd-*"]
|
|
language = "eql"
|
|
license = "Elastic License v2"
|
|
name = "Suspicious Modprobe File Event"
|
|
note = """## Setup
|
|
This 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.
|
|
|
|
```
|
|
Kibana -->
|
|
Management -->
|
|
Integrations -->
|
|
Auditd Manager -->
|
|
Add Auditd Manager
|
|
```
|
|
|
|
`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.
|
|
|
|
For this detection rule to trigger, the following additional audit rules are required to be added to the integration:
|
|
```
|
|
-w /etc/modprobe.conf -p wa -k modprobe
|
|
-w /etc/modprobe.d -p wa -k modprobe
|
|
```
|
|
|
|
Add the newly installed `auditd manager` to an agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
|
|
"""
|
|
risk_score = 21
|
|
rule_id = "40ddbcc8-6561-44d9-afc8-eefdbfe0cccd"
|
|
severity = "low"
|
|
tags = ["OS: Linux", "Use Case: Threat Detection", "Tactic: Discovery"]
|
|
timestamp_override = "event.ingested"
|
|
type = "eql"
|
|
query = '''
|
|
file where host.os.type == "linux" and event.action in ("opened-file", "read-file", "wrote-to-file") and
|
|
file.path : ("/etc/modprobe.conf", "/etc/modprobe.d", "/etc/modprobe.d/*") and not
|
|
(process.name in ("auditbeat", "kmod", "modprobe", "lsmod", "insmod", "modinfo", "rmmod") or process.title : ("*grep*") or process.parent.pid == 1)
|
|
'''
|
|
|
|
[[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/"
|