-
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] [Detections] Improves Cypress EQL test #79014
Conversation
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Pinging @elastic/siem (Team:SIEM) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MadameSheema this looks great, thank you!
@@ -215,7 +215,7 @@ export const machineLearningRule: MachineLearningRule = { | |||
}; | |||
|
|||
export const eqlRule: CustomRule = { | |||
customQuery: 'process where process_name == "explorer.exe"', | |||
customQuery: 'any where process.name == "which"', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems indicative of a data issue and it would be nice to test the event.category functionality, but this is a great improvement!
Thanks for adding this test @MadameSheema! It doesn't have to be included in this PR, but I think it would be nice to also add a test that verifies that the correct number of signals is generated when an EQL query that has a
|
Co-authored-by: Elastic Machine <[email protected]>
Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
Pinging @elastic/security-solution (Team: SecuritySolution) |
Summary
Improves current EQL cypress test in order to check also that the created rule can generate alerts.