Kernel Driver Load

 1[metadata]
 2creation_date = "2023/10/26"
 3integration = ["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/22"
 8
 9[rule]
10author = ["Elastic"]
11description = """
12Detects the loading of a Linux kernel module through system calls. Threat actors may leverage Linux kernel modules to 
13load a rootkit on a system providing them with complete control and the ability to hide from security products. As other
14rules monitor for the addition of Linux kernel modules through system utilities or .ko files, this rule covers the gap 
15that evasive rootkits leverage by monitoring for kernel module additions on the lowest level through auditd_manager. 
16"""
17from = "now-9m"
18index = ["auditbeat-*", "logs-auditd_manager.auditd-*"]
19language = "eql"
20license = "Elastic License v2"
21name = "Kernel Driver Load"
22risk_score = 21
23rule_id = "3e12a439-d002-4944-bc42-171c0dcb9b96"
24setup = """## Setup
25This 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
2`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. 
3
4For this detection rule to trigger, the following additional audit rules are required to be added to the integration:

 1
 2Add the newly installed `auditd manager` to an agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
 3"""
 4severity = "low"
 5tags = [
 6        "Data Source: Auditd Manager",
 7        "Domain: Endpoint",
 8        "OS: Linux",
 9        "Use Case: Threat Detection",
10        "Tactic: Persistence",
11        "Tactic: Defense Evasion"
12        ]
13timestamp_override = "event.ingested"
14type = "eql"
15query = '''
16driver where host.os.type == "linux" and event.action == "loaded-kernel-module" and
17auditd.data.syscall in ("init_module", "finit_module")
18'''
19
20[[rule.threat]]
21framework = "MITRE ATT&CK"
22
23[[rule.threat.technique]]
24id = "T1547"
25name = "Boot or Logon Autostart Execution"
26reference = "https://attack.mitre.org/techniques/T1547/"
27
28[[rule.threat.technique.subtechnique]]
29id = "T1547.006"
30name = "Kernel Modules and Extensions"
31reference = "https://attack.mitre.org/techniques/T1547/006/"
32
33[rule.threat.tactic]
34id = "TA0003"
35name = "Persistence"
36reference = "https://attack.mitre.org/tactics/TA0003/"
37
38[[rule.threat]]
39framework = "MITRE ATT&CK"
40
41[rule.threat.tactic]
42id = "TA0005"
43name = "Defense Evasion"
44reference = "https://attack.mitre.org/tactics/TA0005/"
45
46[[rule.threat.technique]]
47name = "Rootkit"
48id = "T1014"
49reference = "https://attack.mitre.org/techniques/T1014/"