Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Rule Tuning] Remove hardcoded logic from description #4503

Merged
merged 1 commit into from
Feb 28, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions rules/network/discovery_potential_network_sweep_detected.toml
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,16 @@
creation_date = "2023/05/17"
integration = ["network_traffic", "panw"]
maturity = "production"
updated_date = "2025/02/04"
updated_date = "2025/02/28"

[rule]
author = ["Elastic"]
description = """
This rule identifies a potential network sweep. A network sweep is a method used by attackers to scan a target network,
identifying active hosts, open ports, and available services to gather information on vulnerabilities and weaknesses.
This reconnaissance helps them plan subsequent attacks and exploit potential entry points for unauthorized access, data
theft, or other malicious activities. This rule proposes threshold logic to check for connection attempts from one
source host to 100 or more destination hosts on commonly used network services.
theft, or other malicious activities. This rule defines a threshold-based approach to detect multiple connection
attempts from a single host to numerous destination hosts over commonly used network services.
"""
from = "now-9m"
index = ["packetbeat-*", "filebeat-*", "logs-network_traffic.*", "logs-panw.panos*"]
Expand Down
6 changes: 3 additions & 3 deletions rules/network/discovery_potential_port_scan_detected.toml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
creation_date = "2023/05/17"
integration = ["network_traffic", "panw"]
maturity = "production"
updated_date = "2025/02/04"
updated_date = "2025/02/28"

[rule]
author = ["Elastic"]
Expand All @@ -11,8 +11,8 @@ This rule identifies a potential port scan. A port scan is a method utilized by
target system or network for open ports, allowing them to identify available services and potential vulnerabilities. By
mapping out the open ports, attackers can gather critical information to plan and execute targeted attacks, gaining
unauthorized access, compromising security, and potentially leading to data breaches, unauthorized control, or further
exploitation of the targeted system or network. This rule proposes threshold logic to check for connection attempts from
one source host to 250 or more destination ports.
exploitation of the targeted system or network. This rule defines a threshold-based approach to detect connection
attempts from a single source to a wide range of destination ports.
"""
from = "now-9m"
index = ["logs-network_traffic.*", "packetbeat-*", "filebeat-*", "logs-panw.panos*"]
Expand Down
6 changes: 3 additions & 3 deletions rules/network/discovery_potential_syn_port_scan_detected.toml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
creation_date = "2023/05/17"
integration = ["network_traffic", "panw"]
maturity = "production"
updated_date = "2025/02/04"
updated_date = "2025/02/28"

[rule]
author = ["Elastic"]
Expand All @@ -11,8 +11,8 @@ This rule identifies a potential SYN-Based port scan. A SYN port scan is a techn
target network for open ports by sending SYN packets to multiple ports and observing the response. Attackers use this
method to identify potential entry points or services that may be vulnerable to exploitation, allowing them to launch
targeted attacks or gain unauthorized access to the system or network, compromising its security and potentially leading
to data breaches or further malicious activities. This rule proposes threshold logic to check for connection attempts
from one source host to 250 or more destination ports using 2 or less packets per port.
to data breaches or further malicious activities. This rule defines a threshold-based approach to detect connection
attempts from a single source to a large number of unique destination ports, while limiting the number of packets per port.
"""
from = "now-9m"
index = ["logs-network_traffic.*", "packetbeat-*", "filebeat-*", "logs-panw.panos*"]
Expand Down
Loading