Skip to content

[Security Rules] Update security rules package to v9.3.6-beta.1#18006

Merged
shashank-elastic merged 2 commits intomainfrom
detection-rules/9.3.6-beta.1-05c5c5cdc
Mar 24, 2026
Merged

[Security Rules] Update security rules package to v9.3.6-beta.1#18006
shashank-elastic merged 2 commits intomainfrom
detection-rules/9.3.6-beta.1-05c5c5cdc

Conversation

@tradebot-elastic
Copy link
Copy Markdown
Contributor

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 reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • If I'm introducing a new feature, I have modified the Kibana version constraint in my package's manifest.yml file to point to the latest Elastic stack release (e.g. ^7.13.0).

Author's Checklist

  • Install the most recently release security rules in the Detection Engine
  • Install the package
  • Confirm the update is available in Kibana. Click "Update X rules" or "Install X rules"
  • Look at the changes made after the install and confirm they are consistent

How to test this PR locally

  • Perform the above checklist, and use package-storage to build EPR from source

Related issues

None

Screenshots

None

@shashank-elastic shashank-elastic added enhancement New feature or request Integration:security_detection_engine Prebuilt Security Detection Rules labels Mar 24, 2026
@shashank-elastic
Copy link
Copy Markdown
Contributor

Awaiting a recent change confirmation before we approve and merge.

Comment on lines +8 to +10
"index": [
"logs-endpoint.events.process*"
],
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 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.

@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

cc @shashank-elastic

@shashank-elastic shashank-elastic marked this pull request as ready for review March 24, 2026 12:01
@shashank-elastic shashank-elastic requested a review from a team as a code owner March 24, 2026 12:01
@shashank-elastic shashank-elastic merged commit 524209e into main Mar 24, 2026
10 checks passed
@shashank-elastic shashank-elastic deleted the detection-rules/9.3.6-beta.1-05c5c5cdc branch March 24, 2026 12:01
@elastic-vault-github-plugin-prod
Copy link
Copy Markdown

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/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request Integration:security_detection_engine Prebuilt Security Detection Rules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants