-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[SIEM Migrations] Add missing fields to rule migrations results (#206833
) ## Summary Include all data from the migration process in the translated rule documents, so we are able to display the correct information in the table, allowing us also to sort and filter by these fields. The fields added are: - `integration_ids` -> new field mapped in the index (from `integration_id`), the field is set when we match a prebuilt rule too. - `risk_score` -> new field mapped in the index, the field is set when we match a prebuilt rule and set the default value otherwise. - `severity` -> the field is set when we match a prebuilt rule too. Defaults moved from the UI to the LLM graph result. Next steps: - Take the `risk_score` from the original rule for the custom translated rules - Infer `severity` from the original rule risk_score (and maybe other parameters) for the custom translated rules Other changes - The RuleMigrationSevice has been refactored to take all dependencies (clients, services) from the API context factory. This change makes all dependencies always available within the Rule migration service so we don't need to pass them by parameters in each single operation. - The Prebuilt rule retriever now stores all the prebuilt rules data in memory during the migration, so we can return all the prebuilt rule information when we execute semantic searches. This was necessary to set `rule_id`, `integration_ids`, `severity`, and `risk_score` fields correctly. ## Screenshots ![screenshot](https://github.com/user-attachments/assets/ee85879e-9d37-498c-9803-0fd3850c3cc5) --------- Co-authored-by: kibanamachine <[email protected]>
- Loading branch information
1 parent
a042747
commit 7f1e24e
Showing
28 changed files
with
168 additions
and
147 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.