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

[Security Solution] Recommended Endpoint exceptions cannot close all alerts by default but should #199707

Open
ferullo opened this issue Nov 11, 2024 · 3 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Rule Exceptions Security Solution Detection Rule Exceptions area impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed

Comments

@ferullo
Copy link
Contributor

ferullo commented Nov 11, 2024

Describe the bug:
By default recommended Endpoint Exceptions for Malicious Behavior alerts have a grayed out checkbox for Close all alerts that match this exception and were generated by this rule (Lists and non-ECS fields are not supported) even though they can be closed and there is a simple workaround to make that happen.

Kibana/Elasticsearch Stack version: 8.15.3

Server OS version: N/A

Browser and Browser OS versions: Firefox 132.0.1

Elastic Endpoint version: N/A

Original install method (e.g. download page, yum, from source, etc.): ECH

Functional Area (e.g. Endpoint management, timelines, resolver, etc.): Endpoint Exceptions

Steps to reproduce:

  1. Generate an Endpoint Malicious Behavior alert on Windows
  2. Open the alert and select Take action -> Add Endpoint exception
  3. See the Close all alerts ... option is greyed out (this is the bug)
  4. Change the process.executable.caseless field to process.executable then back to process.executable.caseless
  5. See the Close all alerts ... option is now available and works if clicked

Current behavior: See above

Expected behavior: The option should work without any user edits

Screenshots (if relevant): I hope my explaination is good enough

Errors in browser console (if relevant): N/A

Provide logs and/or server output (if relevant): N/A

Any additional context (logs, chat logs, magical formulas, etc.): N/A

@ferullo ferullo added bug Fixes for quality problems that affect the customer experience Feature:Rule Exceptions Security Solution Detection Rule Exceptions area impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team triage_needed labels Nov 11, 2024
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-engine (Team:Detection Engine)

@elasticmachine
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Rule Exceptions Security Solution Detection Rule Exceptions area impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Detection Engine Security Solution Detection Engine Area Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed
Projects
None yet
Development

No branches or pull requests

3 participants