elastic/kibana
View on GitHub[Security Solution] Deleting exception container using the API can break a rule
Open
#163,122 opened on Aug 3, 2023
Feature:Rule ExceptionsTeam: SecuritySolutionTeam:Detection EngineTeam:Detection EngineeringTeam:Detections and Respbugeffort:mediumgood first issueimpact:mediumvalue:high
Repository metrics
- Stars
- (19,065 stars)
- PR merge metrics
- (Avg merge 1d 16h) (999 merged PRs in 30d)
Description
Describe the bug: Deleting exception container using the API can break any linked rules.
Kibana/Elasticsearch Stack version: 8.7.0
Steps to reproduce: Occurs when deleting an exception container from a rule with at least 1 exception item using the API without first removing/unlinking the exception from the rule.
- Create a rule and link an exception container with at least 1 item.
- Delete the exception container using the API without unlinking the rule first.
Current behavior: The Kibana interface for a given rule is broken and rules are stuck with non-existent exception containers.
Expected behavior: Add a warning to the docs or unlink all rules automatically when deleting an exception container.
Screenshots (if relevant):