- Notifications
You must be signed in to change notification settings - Fork 603
[New Rule] Potential Hex Payload Execution #4241
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits Select commit Hold shift + click to select a range
b0f31e2
[New Rule] Potential Hex Payload Execution
Aegrah 56e0858
Merge branch 'main' into hex-payload-execution
shashank-elastic c4d1e9a
Update rules/linux/defense_evasion_hex_payload_execution.toml
Aegrah 8b195ea
Merge branch 'main' into hex-payload-execution
Aegrah 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
This file contains hidden or 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,111 @@ | ||
[metadata] | ||
creation_date = "2024/11/04" | ||
integration = ["endpoint"] | ||
maturity = "production" | ||
updated_date = "2024/11/04" | ||
| ||
[rule] | ||
author = ["Elastic"] | ||
description = """ | ||
This rule detects potential hex payload execution on Linux systems. Adversaries may use hex encoding to obfuscate payloads | ||
and evade detection mechanisms. | ||
""" | ||
from = "now-9m" | ||
index = ["logs-endpoint.events.process*"] | ||
language = "eql" | ||
license = "Elastic License v2" | ||
name = "Potential Hex Payload Execution" | ||
risk_score = 21 | ||
rule_id = "0c1e8fda-4f09-451e-bc77-a192b6cbfc32" | ||
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: Defense Evasion", | ||
"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 == "xxd" and process.args like ("-r*", "-p*")) or | ||
(process.name like "python*" and process.command_line like "*fromhex*" and process.command_line like ("*decode*", "*encode*")) or | ||
(process.name like "php*" and process.command_line like "*hex2bin*") or | ||
(process.name like "ruby*" and process.command_line like "*].pack(\"H*\")*") or | ||
(process.name like "perl*" and process.command_line like "*pack(\"H*\",*") or | ||
(process.name like "lua*" and process.command_line like "*tonumber(cc, 16)*") | ||
) | ||
''' | ||
| ||
[[rule.threat]] | ||
framework = "MITRE ATT&CK" | ||
| ||
[rule.threat.tactic] | ||
name = "Defense Evasion" | ||
id = "TA0005" | ||
reference = "https://attack.mitre.org/tactics/TA0005/" | ||
| ||
[[rule.threat.technique]] | ||
name = "Obfuscated Files or Information" | ||
id = "T1027" | ||
reference = "https://attack.mitre.org/techniques/T1027/" | ||
| ||
[[rule.threat.technique]] | ||
name = "Deobfuscate/Decode Files or Information" | ||
id = "T1140" | ||
reference = "https://attack.mitre.org/techniques/T1140/" | ||
| ||
[[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.technique]] | ||
name = "User Execution" | ||
id = "T1204" | ||
reference = "https://attack.mitre.org/techniques/T1204/" | ||
| ||
[[rule.threat.technique.subtechnique]] | ||
name = "Malicious File" | ||
id = "T1204.002" | ||
reference = "https://attack.mitre.org/techniques/T1204/002/" |
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.
Uh oh!
There was an error while loading. Please reload this page.