-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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.
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
[Security Solution] Add a banner to promote prebuilt rule customization in ESS #205594
Comments
Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management) |
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
@approksiu @ARWNightingale Please provide the final design and links. Based on this comment, as far as I understand for the first release in Serverless we're going to link to some docs page. Which one exactly? |
@banderror will update the ticket with links/copy once confirmed. Thanks! |
Had a discussion with @nastasha-solomon, and we will postpone the serverless banner work till the serverless docs links are available. |
@nastasha-solomon could you please check the copy suggestion for this issue? Thank you! |
@banderror this one is ready for dev |
@nikitaindik I pre-assigned you because you worked on #195423, but the ticket is not ready for dev yet. We'll switch to it after releasing Milestone 3 in Serverless. |
Epic: #174168
Related to: #209000, #195423
Summary
We want to promote the prebuilt rules customization feature in ESS (also known as ECH) by adding a callout to the Rule Management page linking to a blog post about it.
User Story/ Problem Statement(s)
ESS/Non-serverless
Designs/Notes
TBD, example:
Copy:
Header: Get more value out of Elastic prebuilt rules!
Body: Learn how to customize prebuilt rules and update them with the latest improvements.
Blog post URL: https://www.elastic.co/blog/security-prebuilt-rules-editing
Subscription Tier (recommendation)
Basic
Design
Figma file (internal)
The text was updated successfully, but these errors were encountered: