[Security Solution] KQL/Lucene Query bar filters generate diff when saved without changes in Prebuilt Rule Customization workflow #202966
Labels
8.18 candidate
bug
Fixes for quality problems that affect the customer experience
Feature:Prebuilt Detection Rules
Security Solution Prebuilt Detection Rules area
impact:medium
Addressing this issue will have a medium level of impact on the quality/strength of our product.
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.
v8.18.0
Summary
Query bar for editing KQL/Lucene query allows to manage query filters. Some prebuilt rules have such filters. Saving query bar with filters leads to extra fields like
alias: null
appearing in the diff. Saving rule edit form without any changes leads to the same result.Steps to reproduce:
Threat Intel Hash Indicator Match
rule in rule update preview flyoutExpected behavior: There is NO diff in query filters
Actual behavior: There is diff in query filters
Screenshots:
The video below demonstrates how changes to threat query appear even without actual changes while editing a rule in the rule form
Screen.Recording.2024-12-17.at.20.20.15.mov
Setup the environment
prebuiltRulesCustomizationEnabled
feature flag is enabledserver.restrictInternalApis: false
tokibana.dev.yaml
security_detection_engine
Fleet packagethreat_match
rule for editing. For exampleThreat Intel Hash Indicator Match
with rule_idaab184d3-72b3-4639-b242-6597c99d8bca
.The text was updated successfully, but these errors were encountered: