[Security Rules] Update security rules package to v8.19.17-beta.1#17732
Merged
shashank-elastic merged 2 commits intoMar 10, 2026
Conversation
shashank-elastic
added
enhancement
shashank-elastic
approved these changes
Mar 10, 2026
💚 Build Succeeded
|
shashank-elastic
merged commit 2ee1b9a
into
backport-security_detection_engine-8.19
12 checks passed
|
Package security_detection_engine - 8.19.17-beta.1 containing this change is available at https://epr.elastic.co/package/security_detection_engine/8.19.17-beta.1/ |
maximpn
added a commit
to elastic/kibana
that referenced
this pull request
Mar 12, 2026
…tion FTR tests (#257073) **Resolves: #256891 ## Summary This PR unskips the tests skipped in the scope of #256891. The failure was caused by publishing a malformed prebuilt rule in a **security_detection_engine** prerelease package version. The problem has been fixed in the release package version. ## Details The following **security_detection_engine** prerelease package versions have a malformed prebuilt rule - [9.3.5-beta.1](elastic/integrations#17735) - [9.2.9-beta.1](elastic/integrations#17734) - [9.1.17-beta.1](elastic/integrations#17733) - [8.19.17-beta.1](elastic/integrations#17732) `First Time Seen DNS Query to RMM Domain` (rule_id = `e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b`) in those package versions has a small history window size. The failed functional test installs all prebuilt rules. And the error `params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'` gets thrown upon this rule installation. The problem has been fixed and the tests pass for the following prerelese and release versions - [9.3.5-beta.2](elastic/integrations#17740) released [9.3.5](elastic/integrations#17749) - [9.2.9-beta.2](elastic/integrations#17739) released [9.2.9](elastic/integrations#17747) - [9.1.17-beta.2](elastic/integrations#17738) released [9.1.17](elastic/integrations#17746) - [8.19.17-beta.2](elastic/integrations#17737) released [8.19.17](elastic/integrations#17745) This PR unskips previously skipped in the scope of #256891 FTR tests. On top of that this PR improves related debug logging message to be able to faster troubleshoot similar issues in the future. An example error message looks like ```` createPrebuiltRules: Creating prebuilt rules - done. Rules created: 1532. Rules failed to create: 1. Errors: [{"rule_id":"e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b","ruleName":"First Time Seen DNS Query to RMM Domain","error":"params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'"}] ````
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Mar 12, 2026
…tion FTR tests (elastic#257073) **Resolves: elastic#256891 ## Summary This PR unskips the tests skipped in the scope of elastic#256891. The failure was caused by publishing a malformed prebuilt rule in a **security_detection_engine** prerelease package version. The problem has been fixed in the release package version. ## Details The following **security_detection_engine** prerelease package versions have a malformed prebuilt rule - [9.3.5-beta.1](elastic/integrations#17735) - [9.2.9-beta.1](elastic/integrations#17734) - [9.1.17-beta.1](elastic/integrations#17733) - [8.19.17-beta.1](elastic/integrations#17732) `First Time Seen DNS Query to RMM Domain` (rule_id = `e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b`) in those package versions has a small history window size. The failed functional test installs all prebuilt rules. And the error `params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'` gets thrown upon this rule installation. The problem has been fixed and the tests pass for the following prerelese and release versions - [9.3.5-beta.2](elastic/integrations#17740) released [9.3.5](elastic/integrations#17749) - [9.2.9-beta.2](elastic/integrations#17739) released [9.2.9](elastic/integrations#17747) - [9.1.17-beta.2](elastic/integrations#17738) released [9.1.17](elastic/integrations#17746) - [8.19.17-beta.2](elastic/integrations#17737) released [8.19.17](elastic/integrations#17745) This PR unskips previously skipped in the scope of elastic#256891 FTR tests. On top of that this PR improves related debug logging message to be able to faster troubleshoot similar issues in the future. An example error message looks like ```` createPrebuiltRules: Creating prebuilt rules - done. Rules created: 1532. Rules failed to create: 1. Errors: [{"rule_id":"e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b","ruleName":"First Time Seen DNS Query to RMM Domain","error":"params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'"}] ```` (cherry picked from commit 9370986)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Mar 12, 2026
…tion FTR tests (elastic#257073) **Resolves: elastic#256891 ## Summary This PR unskips the tests skipped in the scope of elastic#256891. The failure was caused by publishing a malformed prebuilt rule in a **security_detection_engine** prerelease package version. The problem has been fixed in the release package version. ## Details The following **security_detection_engine** prerelease package versions have a malformed prebuilt rule - [9.3.5-beta.1](elastic/integrations#17735) - [9.2.9-beta.1](elastic/integrations#17734) - [9.1.17-beta.1](elastic/integrations#17733) - [8.19.17-beta.1](elastic/integrations#17732) `First Time Seen DNS Query to RMM Domain` (rule_id = `e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b`) in those package versions has a small history window size. The failed functional test installs all prebuilt rules. And the error `params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'` gets thrown upon this rule installation. The problem has been fixed and the tests pass for the following prerelese and release versions - [9.3.5-beta.2](elastic/integrations#17740) released [9.3.5](elastic/integrations#17749) - [9.2.9-beta.2](elastic/integrations#17739) released [9.2.9](elastic/integrations#17747) - [9.1.17-beta.2](elastic/integrations#17738) released [9.1.17](elastic/integrations#17746) - [8.19.17-beta.2](elastic/integrations#17737) released [8.19.17](elastic/integrations#17745) This PR unskips previously skipped in the scope of elastic#256891 FTR tests. On top of that this PR improves related debug logging message to be able to faster troubleshoot similar issues in the future. An example error message looks like ```` createPrebuiltRules: Creating prebuilt rules - done. Rules created: 1532. Rules failed to create: 1. Errors: [{"rule_id":"e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b","ruleName":"First Time Seen DNS Query to RMM Domain","error":"params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'"}] ```` (cherry picked from commit 9370986)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Mar 12, 2026
…tion FTR tests (elastic#257073) **Resolves: elastic#256891 ## Summary This PR unskips the tests skipped in the scope of elastic#256891. The failure was caused by publishing a malformed prebuilt rule in a **security_detection_engine** prerelease package version. The problem has been fixed in the release package version. ## Details The following **security_detection_engine** prerelease package versions have a malformed prebuilt rule - [9.3.5-beta.1](elastic/integrations#17735) - [9.2.9-beta.1](elastic/integrations#17734) - [9.1.17-beta.1](elastic/integrations#17733) - [8.19.17-beta.1](elastic/integrations#17732) `First Time Seen DNS Query to RMM Domain` (rule_id = `e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b`) in those package versions has a small history window size. The failed functional test installs all prebuilt rules. And the error `params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'` gets thrown upon this rule installation. The problem has been fixed and the tests pass for the following prerelese and release versions - [9.3.5-beta.2](elastic/integrations#17740) released [9.3.5](elastic/integrations#17749) - [9.2.9-beta.2](elastic/integrations#17739) released [9.2.9](elastic/integrations#17747) - [9.1.17-beta.2](elastic/integrations#17738) released [9.1.17](elastic/integrations#17746) - [8.19.17-beta.2](elastic/integrations#17737) released [8.19.17](elastic/integrations#17745) This PR unskips previously skipped in the scope of elastic#256891 FTR tests. On top of that this PR improves related debug logging message to be able to faster troubleshoot similar issues in the future. An example error message looks like ```` createPrebuiltRules: Creating prebuilt rules - done. Rules created: 1532. Rules failed to create: 1. Errors: [{"rule_id":"e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b","ruleName":"First Time Seen DNS Query to RMM Domain","error":"params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'"}] ```` (cherry picked from commit 9370986)
sorenlouv
pushed a commit
to elastic/kibana
that referenced
this pull request
Mar 17, 2026
…tion FTR tests (#257073) **Resolves: #256891 ## Summary This PR unskips the tests skipped in the scope of #256891. The failure was caused by publishing a malformed prebuilt rule in a **security_detection_engine** prerelease package version. The problem has been fixed in the release package version. ## Details The following **security_detection_engine** prerelease package versions have a malformed prebuilt rule - [9.3.5-beta.1](elastic/integrations#17735) - [9.2.9-beta.1](elastic/integrations#17734) - [9.1.17-beta.1](elastic/integrations#17733) - [8.19.17-beta.1](elastic/integrations#17732) `First Time Seen DNS Query to RMM Domain` (rule_id = `e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b`) in those package versions has a small history window size. The failed functional test installs all prebuilt rules. And the error `params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'` gets thrown upon this rule installation. The problem has been fixed and the tests pass for the following prerelese and release versions - [9.3.5-beta.2](elastic/integrations#17740) released [9.3.5](elastic/integrations#17749) - [9.2.9-beta.2](elastic/integrations#17739) released [9.2.9](elastic/integrations#17747) - [9.1.17-beta.2](elastic/integrations#17738) released [9.1.17](elastic/integrations#17746) - [8.19.17-beta.2](elastic/integrations#17737) released [8.19.17](elastic/integrations#17745) This PR unskips previously skipped in the scope of #256891 FTR tests. On top of that this PR improves related debug logging message to be able to faster troubleshoot similar issues in the future. An example error message looks like ```` createPrebuiltRules: Creating prebuilt rules - done. Rules created: 1532. Rules failed to create: 1. Errors: [{"rule_id":"e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b","ruleName":"First Time Seen DNS Query to RMM Domain","error":"params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'"}] ````
jeramysoucy
pushed a commit
to jeramysoucy/kibana
that referenced
this pull request
Mar 26, 2026
…tion FTR tests (elastic#257073) **Resolves: elastic#256891 ## Summary This PR unskips the tests skipped in the scope of elastic#256891. The failure was caused by publishing a malformed prebuilt rule in a **security_detection_engine** prerelease package version. The problem has been fixed in the release package version. ## Details The following **security_detection_engine** prerelease package versions have a malformed prebuilt rule - [9.3.5-beta.1](elastic/integrations#17735) - [9.2.9-beta.1](elastic/integrations#17734) - [9.1.17-beta.1](elastic/integrations#17733) - [8.19.17-beta.1](elastic/integrations#17732) `First Time Seen DNS Query to RMM Domain` (rule_id = `e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b`) in those package versions has a small history window size. The failed functional test installs all prebuilt rules. And the error `params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'` gets thrown upon this rule installation. The problem has been fixed and the tests pass for the following prerelese and release versions - [9.3.5-beta.2](elastic/integrations#17740) released [9.3.5](elastic/integrations#17749) - [9.2.9-beta.2](elastic/integrations#17739) released [9.2.9](elastic/integrations#17747) - [9.1.17-beta.2](elastic/integrations#17738) released [9.1.17](elastic/integrations#17746) - [8.19.17-beta.2](elastic/integrations#17737) released [8.19.17](elastic/integrations#17745) This PR unskips previously skipped in the scope of elastic#256891 FTR tests. On top of that this PR improves related debug logging message to be able to faster troubleshoot similar issues in the future. An example error message looks like ```` createPrebuiltRules: Creating prebuilt rules - done. Rules created: 1532. Rules failed to create: 1. Errors: [{"rule_id":"e5f6a7b8-c9d0-8e1f-2a3b-4c5d6e7f8a9b","ruleName":"First Time Seen DNS Query to RMM Domain","error":"params invalid: History window size is smaller than rule interval + additional lookback, 'historyWindowStart' must be earlier than 'from'"}] ````
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
3 participants
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 8.19.17-beta.1.
Autogenerated from commit https://github.com/elastic/detection-rules/tree/a9e4da6586dda0b470bc9439394093d2a7062262
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