94 lines
4.0 KiB
TOML
94 lines
4.0 KiB
TOML
|
|
[metadata]
|
||
|
|
creation_date = "2023/10/26"
|
||
|
|
integration = ["endpoint"]
|
||
|
|
maturity = "production"
|
||
|
|
min_stack_comments = "New fields added: required_fields, related_integrations, setup"
|
||
|
|
min_stack_version = "8.3.0"
|
||
|
|
updated_date = "2023/10/26"
|
||
|
|
|
||
|
|
[rule]
|
||
|
|
author = ["Elastic"]
|
||
|
|
description = """
|
||
|
|
This rule monitors for a file creation event originating from a kworker parent process. kworker, or kernel worker,
|
||
|
|
processes are part of the kernel's workqueue mechanism. They are responsible for executing work that has been scheduled
|
||
|
|
to be done in kernel space, which might include tasks like handling interrupts, background activities, and other
|
||
|
|
kernel-related tasks. Attackers may attempt to evade detection by masquerading as a kernel worker process.
|
||
|
|
"""
|
||
|
|
from = "now-9m"
|
||
|
|
index = ["logs-endpoint.events.*"]
|
||
|
|
language = "eql"
|
||
|
|
license = "Elastic License v2"
|
||
|
|
name = "Suspicious File Creation via Kworker"
|
||
|
|
risk_score = 47
|
||
|
|
rule_id = "ae343298-97bc-47bc-9ea2-5f2ad831c16e"
|
||
|
|
setup = """## 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 to select "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: Persistence",
|
||
|
|
"Tactic: Defense Evasion",
|
||
|
|
"Data Source: Elastic Defend"
|
||
|
|
]
|
||
|
|
timestamp_override = "event.ingested"
|
||
|
|
type = "eql"
|
||
|
|
query = '''
|
||
|
|
file where event.action == "creation" and process.name : "kworker*" and not (
|
||
|
|
process.name : "kworker*kcryptd*" or file.path : ("/var/log/*", "/var/crash/*")
|
||
|
|
)
|
||
|
|
'''
|
||
|
|
|
||
|
|
[[rule.threat]]
|
||
|
|
framework = "MITRE ATT&CK"
|
||
|
|
|
||
|
|
[[rule.threat.technique]]
|
||
|
|
id = "T1547"
|
||
|
|
name = "Boot or Logon Autostart Execution"
|
||
|
|
reference = "https://attack.mitre.org/techniques/T1547/"
|
||
|
|
|
||
|
|
[rule.threat.tactic]
|
||
|
|
id = "TA0003"
|
||
|
|
name = "Persistence"
|
||
|
|
reference = "https://attack.mitre.org/tactics/TA0003/"
|
||
|
|
|
||
|
|
[[rule.threat]]
|
||
|
|
framework = "MITRE ATT&CK"
|
||
|
|
|
||
|
|
[rule.threat.tactic]
|
||
|
|
id = "TA0005"
|
||
|
|
name = "Defense Evasion"
|
||
|
|
reference = "https://attack.mitre.org/tactics/TA0005/"
|
||
|
|
|
||
|
|
[[rule.threat.technique]]
|
||
|
|
name = "Rootkit"
|
||
|
|
id = "T1014"
|
||
|
|
reference = "https://attack.mitre.org/techniques/T1014/"
|
||
|
|
|