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][Timeline] #181122

Open
stevengoossensB opened this issue Apr 18, 2024 · 9 comments
Open

[Security Solution][Timeline] #181122

stevengoossensB opened this issue Apr 18, 2024 · 9 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team

Comments

@stevengoossensB
Copy link

Summary

Timeline does not include the NOT Exceptions filter, depending on where it's launched from the quick button next to the alert.

Steps to reproduce:

  1. Open Kibana -> Security Solution -> Alerts
  2. Click on the timeline button in the alert overview
    image
  3. This opens a timeline without NOT Exceptions filter, showing all excluded events
  4. Click on the view details button and Take action -> Investigate in Timeline
    image
    image
  5. This opens a timeline with NOT Exceptions filter, hiding all excluded events

Expected behavior

Both ways to access the timeline have the same behavior, including the NOT Exceptions filter

@stevengoossensB stevengoossensB added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. triage_needed labels Apr 18, 2024
@elasticmachine
Copy link
Contributor

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

@MadameSheema MadameSheema added Team:Threat Hunting Security Solution Threat Hunting Team Team:Threat Hunting:Investigations Security Solution Investigations Team labels Apr 18, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

@michaelolo24
Copy link
Contributor

Thanks for opening this issue @stevengoossensB ! We'll take a look into why this inconsistency is happening, thanks!

@PhilippeOberti
Copy link
Contributor

@stevengoossensB thanks for opening this ticket! In order to help here we would need some more information. Could you answer the following questions when you get a chance:

  • which version of Kibana you are using?
  • what do you mean by NOT exceptions filter? Could you provide a screenshot of the timeline opened from the alert table and another one from the alert details flyout so we can compare? When trying locally both look exactly the same for me
  • can you tell us if this behavior is happening for alerts generated by a specific rule or are you seeing the problem across multiple rules?
    • if it is happening for a specific rule, could you give us details about this rule?

Thanks!

@stevengoossensB
Copy link
Author

@PhilippeOberti

  • I've noticed the issue in version 8.12 and 8.13, so I assume it always has been present and is present everywhere

  • The not exceptions filter, is a filter that gets added automatically. It contains all exceptions that are configured as part of the rule, so you need an alert for a rule with exceptions to possibly see the difference. In the below screenshots you can see the difference.

    • From the flyout: image
    • From the alert table:
      image
  • It happens for all rules that have exceptions configured

@PhilippeOberti
Copy link
Contributor

@stevengoossensB thanks for the details. At the moment I'm unable to reproduce the issue locally, on 8.12, 8.13 or current state of our main branch. I asked a colleague and she was also unable to reproduce this. For us, the NOT Exceptions filter is never added to Timeline, independently from where we open it. I tried for a rule that has a single or multiple exceptions set up.

I'm pinging the rule management team to see if they have an idea. We'll get back to you as soon as we know more!

@stevengoossensB
Copy link
Author

@PhilippeOberti Thanks, let me know if you need any more detail...

btw, maybe it wasn't clear from the message, but the prefered behavior would be to have all of the exclusions always excluded when pivoting toward the timeline. Without that, too much irrelevant data is shown to analysts.

@PhilippeOberti
Copy link
Contributor

@PhilippeOberti Thanks, let me know if you need any more detail...

btw, maybe it wasn't clear from the message, but the prefered behavior would be to have all of the exclusions always excluded when pivoting toward the timeline. Without that, too much irrelevant data is shown to analysts.

Agreed on the preferred behavior!

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 Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team Team:Threat Hunting Security Solution Threat Hunting Team
Projects
None yet
Development

No branches or pull requests

5 participants