shashank-elastic
75 lines
3.7 KiB
TOML
75 lines
3.7 KiB
TOML
[metadata]
|
|
creation_date = "2023/04/11"
|
|
integration = ["endpoint"]
|
|
maturity = "production"
|
|
min_stack_comments = "New fields added: required_fields, related_integrations, setup"
|
|
min_stack_version = "8.5.0"
|
|
updated_date = "2023/10/16"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Identifies instances where VMware processes, such as "vmware-vmx" or "vmx," are terminated on a Linux system
|
|
by a "kill" command. The rule monitors for the "end" event type, which signifies the termination of a process.
|
|
The presence of a "kill" command as the parent process for terminating VMware processes may indicate that a
|
|
threat actor is attempting to interfere with the virtualized environment on the targeted system.
|
|
"""
|
|
from = "now-9m"
|
|
index = ["logs-endpoint.events.*"]
|
|
language = "eql"
|
|
license = "Elastic License v2"
|
|
name = "Suspicious Termination of ESXI Process"
|
|
note = """## 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).
|
|
|
|
"""
|
|
references = [
|
|
"https://www.bleepingcomputer.com/news/security/massive-esxiargs-ransomware-attack-targets-vmware-esxi-servers-worldwide/",
|
|
]
|
|
risk_score = 47
|
|
rule_id = "6641a5af-fb7e-487a-adc4-9e6503365318"
|
|
severity = "medium"
|
|
tags = ["Domain: Endpoint", "OS: Linux", "Use Case: Threat Detection", "Tactic: Impact", "Data Source: Elastic Defend"]
|
|
timestamp_override = "event.ingested"
|
|
type = "eql"
|
|
query = '''
|
|
process where host.os.type == "linux" and event.type == "end" and process.name : ("vmware-vmx", "vmx")
|
|
and process.parent.name : "kill"
|
|
'''
|
|
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
[[rule.threat.technique]]
|
|
id = "T1489"
|
|
name = "Service Stop"
|
|
reference = "https://attack.mitre.org/techniques/T1489/"
|
|
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0040"
|
|
name = "Impact"
|
|
reference = "https://attack.mitre.org/tactics/TA0040/" |