[Security Rules] Update security rules package to v9.3.6-beta.1#18006
Merged
shashank-elastic merged 2 commits intomainfrom Mar 24, 2026
Merged
[Security Rules] Update security rules package to v9.3.6-beta.1#18006shashank-elastic merged 2 commits intomainfrom
shashank-elastic merged 2 commits intomainfrom
Conversation
Contributor
Awaiting a recent change confirmation before we approve and merge. |
Comment on lines
+8
to
+10
| "index": [ | ||
| "logs-endpoint.events.process*" | ||
| ], |
There was a problem hiding this comment.
🟢 Low security_rule/44cb1d8a-1922-4fc0-a00f-36c1caf57393_1.json:8
The rule queries logs-endpoint.events.process* but the EQL query uses file where to detect file creation events. File events are stored in logs-endpoint.events.file*, so the rule will never match any events and will fail to detect the CVE.
- "logs-endpoint.events.process*"
+ "logs-endpoint.events.file*"🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
In file packages/security_detection_engine/kibana/security_rule/44cb1d8a-1922-4fc0-a00f-36c1caf57393_1.json around lines 8-10:
The rule queries `logs-endpoint.events.process*` but the EQL query uses `file where` to detect file creation events. File events are stored in `logs-endpoint.events.file*`, so the rule will never match any events and will fail to detect the CVE.
💚 Build Succeeded
|
shashank-elastic
approved these changes
Mar 24, 2026
|
Package security_detection_engine - 9.3.6-beta.1 containing this change is available at https://epr.elastic.co/package/security_detection_engine/9.3.6-beta.1/ |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Update the Security Rules package to version 9.3.6-beta.1.
Autogenerated from commit https://github.com/elastic/detection-rules/tree/05c5c5cdc5b5ed239b2a85610cf7a47375ce2361
Checklist
I have verified that all data streams collect metrics or logs.changelog.ymlfile.manifest.ymlfile to point to the latest Elastic stack release (e.g.^7.13.0).Author's Checklist
How to test this PR locally
package-storageto build EPR from sourceRelated issues
None
Screenshots
None