Skip to content

[Security Solution] Indicate conflicting rules in the Rule Upgrade table #190500

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Tracked by #214746
banderror opened this issue Aug 14, 2024 · 4 comments
Closed
Tracked by #214746

[Security Solution] Indicate conflicting rules in the Rule Upgrade table #190500

banderror opened this issue Aug 14, 2024 · 4 comments
Assignees
@approksiu @ARWNightingale
Labels
Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area needs 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. UX: UI/UX Designs Requires design mocks before development and UX lead approval on PR before merge.

Comments

@banderror
Copy link
Contributor

banderror commented Aug 14, 2024 •
edited by approksiu
Loading

Epics: https://github.com/elastic/security-team/issues/1974 (internal), #179907
Designs: TBD

Summary

Then the Elastic prebuilt rules update is available, and the user has modified prebuilt rules, some rules will have conflicting field updates that require the user to resolve them. To help users assess the time the update will take, and prioritize their rule update tasks, we want to show which rules require review.

User story

As a user, I want to be able to understand which rules in the rule's update table have conflicts.

Acceptance criteria

  • user can filter/sort the rule updates table to find rules that "require updates review"

Telemetry

  • (Adoption) collect telemetry on the filter usage
@banderror banderror added Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Rule Management Security Detection Rule Management Team Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area labels Aug 14, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@banderror banderror mentioned this issue Aug 14, 2024
Open
33 tasks
@approksiu approksiu added the UX: UI/UX Designs Requires design mocks before development and UX lead approval on PR before merge. label Jan 20, 2025
@approksiu approksiu changed the title [Security Solution] Indicate conflicting rules in the Rule Upgrade table (DRAFT) [Security Solution] Indicate conflicting rules in the Rule Upgrade table Jan 20, 2025
@banderror banderror mentioned this issue Mar 17, 2025
Open
20 tasks
@banderror
Copy link
Contributor Author

This was addressed as part of Milestone 3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@approksiu approksiu

@ARWNightingale ARWNightingale

Labels
Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area needs 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. UX: UI/UX Designs Requires design mocks before development and UX lead approval on PR before merge.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@banderror @elasticmachine @approksiu @ARWNightingale