-
Notifications
You must be signed in to change notification settings - Fork 512
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[New Rule] Web Server Spawned via Python (#4236)
* [New Rule] Web Server Spawned via Python * Update execution_python_webserver_spawned.toml * Update rules/linux/execution_python_webserver_spawned.toml Co-authored-by: shashank-elastic <[email protected]> * Update execution_python_webserver_spawned.toml --------- Co-authored-by: shashank-elastic <[email protected]> (cherry picked from commit 267a6b6)
- Loading branch information
1 parent
9f86756
commit 34bb461
Showing
1 changed file
with
94 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,94 @@ | ||
[metadata] | ||
creation_date = "2024/11/04" | ||
integration = ["endpoint"] | ||
maturity = "production" | ||
updated_date = "2024/11/04" | ||
|
||
[rule] | ||
author = ["Elastic"] | ||
description = """ | ||
This rule identifies when a web server is spawned via Python. Attackers may use Python to spawn a web server to | ||
exfiltrate/infiltrate data or to move laterally within a network. | ||
""" | ||
from = "now-9m" | ||
index = ["logs-endpoint.events.*"] | ||
language = "eql" | ||
license = "Elastic License v2" | ||
name = "Web Server Spawned via Python" | ||
risk_score = 21 | ||
rule_id = "99c2b626-de44-4322-b1f9-157ca408c17e" | ||
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 selecting "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: Execution", | ||
"Data Source: Elastic Defend", | ||
] | ||
timestamp_override = "event.ingested" | ||
type = "eql" | ||
query = ''' | ||
process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and ( | ||
(process.name like "python*" and process.args in ("http.server", "SimpleHTTPServer")) or | ||
( | ||
process.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and | ||
process.command_line like~ "*python* -m http.server*" | ||
) | ||
) | ||
''' | ||
|
||
[[rule.threat]] | ||
framework = "MITRE ATT&CK" | ||
|
||
[[rule.threat.technique]] | ||
id = "T1059" | ||
name = "Command and Scripting Interpreter" | ||
reference = "https://attack.mitre.org/techniques/T1059/" | ||
|
||
[[rule.threat.technique.subtechnique]] | ||
id = "T1059.006" | ||
name = "Python" | ||
reference = "https://attack.mitre.org/techniques/T1059/006/" | ||
|
||
[rule.threat.tactic] | ||
id = "TA0002" | ||
name = "Execution" | ||
reference = "https://attack.mitre.org/tactics/TA0002/" | ||
|
||
[[rule.threat]] | ||
framework = "MITRE ATT&CK" | ||
|
||
[rule.threat.tactic] | ||
name = "Lateral Movement" | ||
id = "TA0008" | ||
reference = "https://attack.mitre.org/tactics/TA0008/" | ||
|
||
[[rule.threat.technique]] | ||
id = "T1570" | ||
name = "Lateral Tool Transfer" | ||
reference = "https://attack.mitre.org/techniques/T1570/" |