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] [PRC Milestone 3] Update Prebuilt Rules endpoints to new Prebuilt schema #175771

Closed
jpdjere opened this issue Jan 29, 2024 · 4 comments
Closed

[Security Solution] [PRC Milestone 3] Update Prebuilt Rules endpoints to new Prebuilt schema #175771

jpdjere opened this issue Jan 29, 2024 · 4 comments
Labels
Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area release_note:skip Skip the PR/issue when compiling release notes 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.

Comments

@jpdjere
Copy link
Contributor

jpdjere commented Jan 29, 2024 •
edited
Loading

Prebuilt Rule Customization Epic - Milestone 3: #174168
Main Epic: https://github.com/elastic/security-team/issues/1974 (internal)

Additional Material:
- Milestone 3 - Software Design RFC
- Prebuilt Rules Customization Technical Design

Depends on:

Description:

  • Update Prebuilt Rules endpoints as described in the Prebuilt Rules endpoints section of the Software Design RFC to account for the new rule schema, with the new prebuilt top-level object field.
  • Endpoints to update are:
    • (LEGACY) Get Prebuilt Rules and Timeline Status - /rules/prepackaged/_status
    • Get Prebuilt Rules Status - GET /prebuilt_rules/status (Internal)
    • (LEGACY) Install Prebuilt Rules And Timelines - PUT /rules/prepackaged
    • Review Rule Installation - POST /prebuilt_rules/installation/_review (Internal)
    • Perform Rule Installation - POST /prebuilt_rules/installation/_install (Internal)
    • Review Rule Upgrade - POST /prebuilt_rules/upgrade/_review (Internal)
    • Perform Rule Upgrade - POST /prebuilt_rules/upgrade/_perform (Internal)
  • These changes should be backwards-compatible and should be able to be merged into main or a feature branch without making braking changes.
@jpdjere jpdjere added release_note:skip Skip the PR/issue when compiling release notes 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 Jan 29, 2024
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@jpdjere jpdjere mentioned this issue Jan 29, 2024
Open
@jpdjere
Copy link
Contributor Author

jpdjere commented Apr 9, 2024

Closing in favour of new tickets planned: #174168 (comment)

@jpdjere jpdjere closed this as completed Apr 9, 2024
@banderror banderror closed this as not planned Won't fix, can't repro, duplicate, stale Apr 11, 2024
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 area release_note:skip Skip the PR/issue when compiling release notes 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.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jpdjere @banderror @elasticmachine