Mika Ayenson
122 lines
4.6 KiB
TOML
122 lines
4.6 KiB
TOML
[metadata]
|
|
creation_date = "2023/10/18"
|
|
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/04/30"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
This rule monitors for network connections from a kworker 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 = "kuery"
|
|
license = "Elastic License v2"
|
|
name = "Network Activity Detected via Kworker"
|
|
risk_score = 21
|
|
rule_id = "25d917c4-aa3c-4111-974c-286c0312ff95"
|
|
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 = "low"
|
|
tags = [
|
|
"Domain: Endpoint",
|
|
"OS: Linux",
|
|
"Use Case: Threat Detection",
|
|
"Tactic: Command and Control",
|
|
"Data Source: Elastic Defend"
|
|
]
|
|
timestamp_override = "event.ingested"
|
|
type = "new_terms"
|
|
query = '''
|
|
host.os.type:linux and event.category:network and event.action:(connection_attempted or connection_accepted) and
|
|
process.name:kworker* and not destination.ip:(
|
|
10.0.0.0/8 or
|
|
127.0.0.0/8 or
|
|
169.254.0.0/16 or
|
|
172.16.0.0/12 or
|
|
192.168.0.0/16 or
|
|
224.0.0.0/4 or
|
|
"::1" or
|
|
"FE80::/10" or
|
|
"FF00::/8"
|
|
) and not destination.port:2049
|
|
'''
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0011"
|
|
name = "Command and Control"
|
|
reference = "https://attack.mitre.org/tactics/TA0011/"
|
|
|
|
[[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 = "Masquerading"
|
|
id = "T1036"
|
|
reference = "https://attack.mitre.org/techniques/T1036/"
|
|
|
|
[[rule.threat.technique]]
|
|
name = "Rootkit"
|
|
id = "T1014"
|
|
reference = "https://attack.mitre.org/techniques/T1014/"
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0010"
|
|
name = "Exfiltration"
|
|
reference = "https://attack.mitre.org/tactics/TA0010/"
|
|
|
|
[[rule.threat.technique]]
|
|
name = "Exfiltration Over C2 Channel"
|
|
id = "T1041"
|
|
reference = "https://attack.mitre.org/techniques/T1041/"
|
|
|
|
[rule.new_terms]
|
|
field = "new_terms_fields"
|
|
value = ["process.name", "destination.ip", "destination.port"]
|
|
|
|
[[rule.new_terms.history_window_start]]
|
|
field = "history_window_start"
|
|
value = "now-14d"
|
|
|