-
Notifications
You must be signed in to change notification settings - Fork 513
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
[New Rule] Simple HTTP Web Server Creation #4308
Open
Aegrah
wants to merge
1
commit into
main
Choose a base branch
from
new-rule-simple-webserver-creation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
112 changes: 112 additions & 0 deletions
112
rules/linux/persistence_simple_web_server_creation.toml
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,112 @@ | ||
[metadata] | ||
creation_date = "2024/12/17" | ||
integration = ["endpoint"] | ||
maturity = "production" | ||
updated_date = "2024/12/17" | ||
|
||
[rule] | ||
author = ["Elastic"] | ||
description = """ | ||
This rule detects the creation of a simple HTTP web server using PHP or Python built-in modules. Adversaries may create | ||
simple HTTP web servers to establish persistence on a compromised system by uploading a reverse or command shell payload | ||
to the server web root, allowing them to regain remote access to the system if lost. | ||
""" | ||
from = "now-9m" | ||
index = ["logs-endpoint.events.process*"] | ||
language = "eql" | ||
license = "Elastic License v2" | ||
name = "Simple HTTP Web Server Creation" | ||
risk_score = 21 | ||
rule_id = "907a26f5-3eb6-4338-a70e-6c375c1cde8a" | ||
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: Persistence", | ||
"Tactic: Execution", | ||
"Tactic: Command and Control", | ||
"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 regex~ """php?[0-9]?\.?[0-9]{0,2}""" and process.args == "-S") or | ||
(process.name like "python*" and process.args in ("--cgi", "CGIHTTPServer")) | ||
) | ||
''' | ||
|
||
[[rule.threat]] | ||
framework = "MITRE ATT&CK" | ||
|
||
[rule.threat.tactic] | ||
name = "Persistence" | ||
id = "TA0003" | ||
reference = "https://attack.mitre.org/tactics/TA0003/" | ||
|
||
[[rule.threat.technique]] | ||
id = "T1505" | ||
name = "Server Software Component" | ||
reference = "https://attack.mitre.org/techniques/T1505/" | ||
|
||
[[rule.threat.technique.subtechnique]] | ||
id = "T1505.003" | ||
name = "Web Shell" | ||
reference = "https://attack.mitre.org/techniques/T1505/003/" | ||
|
||
[[rule.threat]] | ||
framework = "MITRE ATT&CK" | ||
|
||
[rule.threat.tactic] | ||
name = "Execution" | ||
id = "TA0002" | ||
reference = "https://attack.mitre.org/tactics/TA0002/" | ||
|
||
[[rule.threat.technique]] | ||
id = "T1059" | ||
name = "Command and Scripting Interpreter" | ||
reference = "https://attack.mitre.org/techniques/T1059/" | ||
|
||
[[rule.threat.technique.subtechnique]] | ||
name = "Unix Shell" | ||
id = "T1059.004" | ||
reference = "https://attack.mitre.org/techniques/T1059/004/" | ||
|
||
[[rule.threat]] | ||
framework = "MITRE ATT&CK" | ||
|
||
[rule.threat.tactic] | ||
name = "Command and Control" | ||
id = "TA0011" | ||
reference = "https://attack.mitre.org/tactics/TA0011/" | ||
|
||
[[rule.threat.technique]] | ||
name = "Application Layer Protocol" | ||
id = "T1071" | ||
reference = "https://attack.mitre.org/techniques/T1071/" |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thoughts on adding
http.server
(known as SimpleHTTPServer) as well? -->python -m http.server
. You can setup CGI with the--cgi
argument as well and bind to a specific port or listen on any address. I'd be interested in alerts where0.0.0.0
is the specified address as it is a "accept any" on cloud instances.Another option would be Flask setup via inline code execution as shown below. I thing from command line args you could check for
import flask and app.run
and flag it as you will always need to import and initialize callapp.run
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The python web server spawn is already in
detection-rules/rules/linux/execution_python_webserver_spawned.toml
Line 57 in 2ff2965
I did not add flask in there because it requires an additional module, which attackers would prefer not to install. And I think starting flask applications will be very noisy. I can check telemetry though!