[Security Solution][Detections] Investigate updating _id to be static rule_id when migrating rules to rule registry #99741
Labels
chore
Feature:Detection Rules
Security Solution rules and Detection Engine
investigating
Team:Detection Rule Management
Security Detection Rule Management Team
Team:Detections and Resp
Security Detection Response Team
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
technical debt
Improvement of the software architecture and operational architecture
With #5026, Rules will now be exportable via the SO Management UI. Since Detection Rules store their static id's within alert
tags
as__internal_rule_id:[ID_HERE]
, that means importing/exporting rules from different sessions/spaces/clusters/etc could potentially introduce duplicates since the SO imported determines uniqueness perspace
per_id
.We're currently looking to filter out Detection Rules from the SO Management UI in favor of using the security UI, however there's a core dependency preventing this (#99680). This issue is for investigating if it's feasible to replace the Rule SO's
_id
with the value in alerttags
as__internal_rule_id:[ID_HERE]
when performing the SO migrations from a singlesiem.signals
rule type to dedicated security rule types.Consideration:
_id
If the above ends up being a breaking change, we should determine feasibility for 8.x migration.
The text was updated successfully, but these errors were encountered: