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.

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

[DOCS] Create Threshold-based Rule type #59

Closed
dontcallmesherryli opened this issue Jul 7, 2020 · 1 comment · Fixed by #70 or #73
Closed

[DOCS] Create Threshold-based Rule type #59

dontcallmesherryli opened this issue Jul 7, 2020 · 1 comment · Fixed by #70 or #73
Assignees
Labels
Team: Docs v7.9.0 Features in the 7.9 Release

Comments

@dontcallmesherryli
Copy link

Description

Meta issue: elastic/kibana#68409
Mocks: https://www.figma.com/file/yNMzeaGvLkyRvra8Bu2fD2/Threshold-Based-Rules?node-id=140%3A31

In 7.9, user will be given a 3rd type of rule to create in the Elastic Security app - Threshold-Based Rule. Threshold rule lets user select fields and set a threshold count to these fields to be alerted on in the SIEM.

Acceptance Test Criteria

Documentation needed to help instruct users on how to create Threshold-Based Rules with some use case examples.

  1. User can select Threshold-Based rule when selecting a type of rule to create.
  2. User will be prompted the steps to enter the Index Pattern, Custom Query, and Field and Count of the threshold rule that it applies to.
  3. Just like the Detection Rule type, user can select configurations around the rule such as Timeline Template used and Schedule of the frequency of the rule to run on the Rule Engine.
  • Use case example: Rule write wants to ensure an alert is generated to detect large number of failed login attempts, so they can select the desired index, query for registry or authorization types of event.type, and designate those fields to a threshold of 100 counts. This way when an end user attempts to log in 100 times within the time of the rule scheduled, the SIEM will receive an alert about the detected activity.

Notes

  • Add the "Team:Docs" label to new issues.
  • Be sure to add any necessary screenshots for clarity.
  • Include any conditions or caveats that may affect customers.
@benskelker
Copy link
Contributor

benskelker commented Jul 21, 2020

Related API PR: #70
Related issue: #71

Related UI PR: #73

This was linked to pull requests Jul 26, 2020
@benskelker benskelker reopened this Jul 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team: Docs v7.9.0 Features in the 7.9 Release
Projects
None yet
3 participants