shashank-elastic
87 lines
3.8 KiB
TOML
87 lines
3.8 KiB
TOML
[metadata]
|
|
creation_date = "2023/09/04"
|
|
integration = ["endpoint", "auditd_manager"]
|
|
maturity = "production"
|
|
updated_date = "2024/05/21"
|
|
|
|
[rule]
|
|
author = ["Elastic"]
|
|
description = """
|
|
This threshold rule monitors for the rapid execution of unix utilities that are capable of conducting network scans.
|
|
Adversaries may leverage built-in tools such as ping, netcat or socat to execute ping sweeps across the network while
|
|
attempting to evade detection or due to the lack of network mapping tools available on the compromised host.
|
|
"""
|
|
from = "now-9m"
|
|
index = ["logs-endpoint.events.*", "endgame-*", "auditbeat-*", "logs-auditd_manager.auditd-*"]
|
|
language = "kuery"
|
|
license = "Elastic License v2"
|
|
name = "Potential Network Scan Executed From Host"
|
|
risk_score = 47
|
|
rule_id = "03c23d45-d3cb-4ad4-ab5d-b361ffe8724a"
|
|
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: Discovery",
|
|
"Data Source: Elastic Defend",
|
|
"Data Source: Elastic Endgame",
|
|
"Data Source: Auditd Manager",
|
|
]
|
|
timestamp_override = "event.ingested"
|
|
type = "threshold"
|
|
|
|
query = '''
|
|
event.category:process and host.os.type:linux and event.action:(exec or exec_event or executed or process_started) and
|
|
event.type:start and process.name:(ping or nping or hping or hping2 or hping3 or nc or ncat or netcat or socat)
|
|
'''
|
|
|
|
|
|
[[rule.threat]]
|
|
framework = "MITRE ATT&CK"
|
|
[[rule.threat.technique]]
|
|
id = "T1046"
|
|
name = "Network Service Discovery"
|
|
reference = "https://attack.mitre.org/techniques/T1046/"
|
|
|
|
|
|
[rule.threat.tactic]
|
|
id = "TA0007"
|
|
name = "Discovery"
|
|
reference = "https://attack.mitre.org/tactics/TA0007/"
|
|
|
|
[rule.threshold]
|
|
field = ["host.id", "process.parent.entity_id", "process.executable"]
|
|
value = 1
|
|
[[rule.threshold.cardinality]]
|
|
field = "process.args"
|
|
value = 100
|
|
|
|
|