-
Notifications
You must be signed in to change notification settings - Fork 518
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] Potential Buffer Overflow Attack Detected #3312
Merged
Merged
Changes from 6 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
f8e32a6
[New Rule] Potential Buffer Overflow Attack
Aegrah d87ac8d
Added timestamp_override
Aegrah d3fa394
Merge branch 'main' into new-rule-potential-bufferoverflow-detected
Aegrah 9ecf2bf
Merge branch 'main' into new-rule-potential-bufferoverflow-detected
Aegrah 65431d2
Update privilege_escalation_potential_bufferoverflow_attack.toml
Aegrah c0abad1
Merge branch 'main' into new-rule-potential-bufferoverflow-detected
Aegrah 06899b4
Merge branch 'main' into new-rule-potential-bufferoverflow-detected
shashank-elastic 1bfeee9
Update privilege_escalation_potential_bufferoverflow_attack.toml
Aegrah 7c5c8cc
Update rules/linux/privilege_escalation_potential_bufferoverflow_atta…
Aegrah ab96dd3
Update rules/linux/privilege_escalation_potential_bufferoverflow_atta…
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
93 changes: 93 additions & 0 deletions
93
rules/linux/privilege_escalation_potential_bufferoverflow_attack.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,93 @@ | ||
[metadata] | ||
creation_date = "2023/12/11" | ||
maturity = "production" | ||
min_stack_comments = "New fields added: required_fields, related_integrations, setup" | ||
min_stack_version = "8.3.0" | ||
updated_date = "2023/12/11" | ||
|
||
[rule] | ||
author = ["Elastic"] | ||
description = """ | ||
Detects potential buffer overflow attacks by querying the "Segfault Detected" pre-built rule signal index, through a | ||
threshold rule, with a minimum number of 100 segfault alerts in a short timespan. A large amount of segfaults in a short | ||
time interval could indicate application exploitation attempts. | ||
""" | ||
from = "now-9m" | ||
index = [".alerts-security.*"] | ||
language = "kuery" | ||
license = "Elastic License v2" | ||
name = "Potential Buffer Overflow Attack Detected" | ||
risk_score = 21 | ||
rule_id = "b7c05aaf-78c2-4558-b069-87fa25973489" | ||
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: Privilege Escalation", | ||
"Tactic: Initial Access", | ||
"Use Case: Vulnerability", | ||
"Rule Type: Higher-Order Rule" | ||
] | ||
timestamp_override = "event.ingested" | ||
type = "threshold" | ||
query = ''' | ||
kibana.alert.rule.rule_id:5c81fc9d-1eae-437f-ba07-268472967013 and event.kind:signal | ||
''' | ||
|
||
[[rule.threat]] | ||
framework = "MITRE ATT&CK" | ||
|
||
[[rule.threat.technique]] | ||
id = "T1068" | ||
name = "Exploitation for Privilege Escalation" | ||
reference = "https://attack.mitre.org/techniques/T1068/" | ||
|
||
[rule.threat.tactic] | ||
id = "TA0004" | ||
name = "Privilege Escalation" | ||
reference = "https://attack.mitre.org/tactics/TA0004/" | ||
|
||
[[rule.threat]] | ||
framework = "MITRE ATT&CK" | ||
|
||
[[rule.threat.technique]] | ||
id = "T1190" | ||
name = "Exploit Public-Facing Application" | ||
reference = "https://attack.mitre.org/techniques/T1190/" | ||
|
||
[rule.threat.tactic] | ||
id = "TA0001" | ||
name = "Initial Access" | ||
reference = "https://attack.mitre.org/tactics/TA0001/" | ||
|
||
[rule.threshold] | ||
field = ["event.kind", "host.id"] | ||
value = 100 | ||
|
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.
May require a few line additions post review from @approksiu
https://docs.google.com/document/d/1J4ClwoAkhcP4BDTw94Bwb3nC_6kXsl5pu99Um8Ddt58/edit?pli=1
We need to mention the dependent Detection rule that needs to be enabled for this threshold rule to fire.