Ruben Groenewoud
9f8638a004
Co-authored-by: Terrance DeJesus <99630311+terrancedejesus@users.noreply.github.com>
88 lines
4.1 KiB
TOML
88 lines
4.1 KiB
TOML
[metadata]
|
|
creation_date = "2023/09/22"
|
|
integration = ["endpoint", "auditd_manager"]
|
|
maturity = "production"
|
|
updated_date = "2024/03/08"
|
|
min_stack_comments = "New fields added: required_fields, related_integrations, setup"
|
|
min_stack_version = "8.3.0"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
Monitors for the execution of different processes that might be used by attackers for malicious intent. An alert from
|
|
this rule should be investigated further, as hack tools are commonly used by blue teamers and system administrators as
|
|
well.
|
|
"""
|
|
from = "now-9m"
|
|
index = ["logs-endpoint.events.*", "endgame-*", "auditbeat-*", "logs-auditd_manager.auditd-*"]
|
|
language = "eql"
|
|
license = "Elastic License v2"
|
|
name = "Potential Linux Hack Tool Launched"
|
|
risk_score = 47
|
|
rule_id = "1df1152b-610a-4f48-9d7a-504f6ee5d9da"
|
|
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"
|
|
timestamp_override = "event.ingested"
|
|
tags = [
|
|
"Domain: Endpoint",
|
|
"OS: Linux",
|
|
"Use Case: Threat Detection",
|
|
"Tactic: Execution",
|
|
"Data Source: Elastic Endgame",
|
|
"Data Source: Elastic Defend",
|
|
"Data Source: Auditd Manager"
|
|
]
|
|
type = "eql"
|
|
query = '''
|
|
process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event", "executed", "process_started")
|
|
and process.name in (
|
|
// exploitation frameworks
|
|
"crackmapexec", "msfconsole", "msfvenom", "sliver-client", "sliver-server", "havoc",
|
|
// network scanners (nmap left out to reduce noise)
|
|
"zenmap", "nuclei", "netdiscover", "legion",
|
|
// web enumeration
|
|
"gobuster", "dirbuster", "dirb", "wfuzz", "ffuf", "whatweb", "eyewitness",
|
|
// web vulnerability scanning
|
|
"wpscan", "joomscan", "droopescan", "nikto",
|
|
// exploitation tools
|
|
"sqlmap", "commix", "yersinia",
|
|
// cracking and brute forcing
|
|
"john", "hashcat", "hydra", "ncrack", "cewl", "fcrackzip", "rainbowcrack",
|
|
// host and network
|
|
"linenum.sh", "linpeas.sh", "pspy32", "pspy32s", "pspy64", "pspy64s", "binwalk", "evil-winrm"
|
|
)
|
|
'''
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0002"
|
|
name = "Execution"
|
|
reference = "https://attack.mitre.org/tactics/TA0002/"
|