IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« New Systemd Service Created by Previously Unknown Process Potential Unauthorized Access via Wildcard Injection Detected »

› ›

Tainted Kernel Module Load

edit

Tainted Kernel Module Load

edit

This rule monitors the syslog log file for messages related to instances of a tainted kernel module load. Rootkits often leverage kernel modules as their main defense evasion technique. Detecting tainted kernel module loads is crucial for ensuring system security and integrity, as malicious or unauthorized modules can compromise the kernel and lead to system vulnerabilities or unauthorized access.

Rule type: query

Rule indices:

logs-system.syslog-*

Severity: low

Risk score: 21

Runs every: 5m

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

References: None

Tags:

Domain: Endpoint
OS: Linux
Use Case: Threat Detection
Tactic: Persistence
Tactic: Defense Evasion

Version: 4

Rule authors:

Elastic

Rule license: Elastic License v2

Setup

edit

Setup

This rule requires data coming in from one of the following integrations: - Filebeat

Filebeat Setup

Filebeat is a lightweight shipper for forwarding and centralizing log data. Installed as an agent on your servers, Filebeat monitors the log files or locations that you specify, collects log events, and forwards them either to Elasticsearch or Logstash for indexing.

The following steps should be executed in order to add the Filebeat for the Linux System:

Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
To install the APT and YUM repositories follow the setup instructions in this helper guide.
To run Filebeat on Docker follow the setup instructions in the helper guide.
To run Filebeat on Kubernetes follow the setup instructions in the helper guide.
For quick start information for Filebeat refer to the helper guide.
For complete Setup and Run Filebeat information refer to the helper guide.

Rule Specific Setup Note

This rule requires the Filebeat System Module to be enabled.
The system module collects and parses logs created by the system logging service of common Unix/Linux based distributions.
To run the system module of Filebeat on Linux follow the setup instructions in the helper guide.

Rule query

edit

host.os.type:linux and event.dataset:"system.syslog" and process.name:kernel and
message:"module verification failed: signature and/or required key missing - tainting kernel"

Framework: MITRE ATT&CK^TM

Tactic:
- Name: Persistence
- ID: TA0003
- Reference URL: https://attack.mitre.org/tactics/TA0003/
Technique:
- Name: Boot or Logon Autostart Execution
- ID: T1547
- Reference URL: https://attack.mitre.org/techniques/T1547/
Sub-technique:
- Name: Kernel Modules and Extensions
- ID: T1547.006
- Reference URL: https://attack.mitre.org/techniques/T1547/006/
Tactic:
- Name: Defense Evasion
- ID: TA0005
- Reference URL: https://attack.mitre.org/tactics/TA0005/
Technique:
- Name: Rootkit
- ID: T1014
- Reference URL: https://attack.mitre.org/techniques/T1014/

« New Systemd Service Created by Previously Unknown Process Potential Unauthorized Access via Wildcard Injection Detected »