Skip to content
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

[Security Solution] [Prebuilt Rules Customization] Add "Last Updated" column in the Add Elastic Rules and Rule Updates tables #174767

Open
Tracked by #179907
jpdjere opened this issue Jan 12, 2024 · 2 comments
Open
Tracked by #179907

[Security Solution] [Prebuilt Rules Customization] Add "Last Updated" column in the Add Elastic Rules and Rule Updates tables #174767

jpdjere opened this issue Jan 12, 2024 · 2 comments
Labels
Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules Team:Detection Rule Management Security Detection Rule Management Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@jpdjere
Copy link
Contributor

jpdjere commented Jan 12, 2024 •
edited
Loading

EPIC: #174168

Depends on:

  1. [FR] Add source_updated_at to Rule Schema as a Build Time Field detection-rules#2826
  2. [Security Solution] Add source_updated_at field to RuleResponse via ResponseFields #174740

Describe the feature:

In our Add Elastic Rules and Rule Updates table, we want to show users a column with information of when was the rule last updated. This information will be provided in the prebuilt rule asset object and returned in the RuleResponse objects of our endpoints: POST /prebuilt_rules/installation/_review and POST /prebuilt_rules/upgrade/_review.

The user should be able to sort the table by this column, in order to see, which are the lastest updates, or in the opposite order, the updates which have been pending the most, i.e. more urgent.

*Designs:

Link: https://www.figma.com/file/gLHm8LpTtSkAUQHrkG3RHU/%5B8.7%5D-%5BRules%5D-Rule-Immutability%2FCustomization?type=design&node-id=2832-551423&mode=design&t=YgkGXlOjlZ9G0wWZ-0

Installation (Add Elastic Rules):
image

Upgrade (Rule Upgrades):
image
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 12, 2024
@jpdjere jpdjere added Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. and removed needs-team Issues missing a team label labels Jan 12, 2024
@elasticmachine
Copy link
Contributor

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

@jpdjere jpdjere added Team:Detection Rule Management Security Detection Rule Management Team Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules labels Jan 12, 2024
@elasticmachine
Copy link
Contributor

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

This was referenced Jan 12, 2024
Open
Merged
@banderror banderror mentioned this issue Apr 3, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules Team:Detection Rule Management Security Detection Rule Management Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jpdjere @elasticmachine