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] Innacurate generic timeline template #123370

Closed
MadameSheema opened this issue Jan 19, 2022 · 7 comments · Fixed by #123333
Closed

[Security Solution] Innacurate generic timeline template #123370

MadameSheema opened this issue Jan 19, 2022 · 7 comments · Fixed by #123333
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

Comments

@MadameSheema
Copy link
Member

MadameSheema commented Jan 19, 2022

Describe the bug:

  • When an alert generated by a rule without a specific timeline template, is investigated on the timeline, the timeline displayed is not the expected one.

Kibana/Elasticsearch Stack version:

  • 8.0

Steps to reproduce:

  1. Create a rule without using a timeline template
  2. Generate alerts for the created rule
  3. Investigate one of the generated alerts on the timeline

Current behavior:

Screenshot 2022-01-19 at 15 46 06

  • The alert is filtered using a predefined filter

Expected behavior:

  • The alert is filtered using the alert id on the data providers

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

  • This is happening for all the rule types except for Threshold rules that is working fine.
@MadameSheema MadameSheema added bug Fixes for quality problems that affect the customer experience triage_needed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Investigations Security Solution Investigations Team labels Jan 19, 2022
@elasticmachine
Copy link
Contributor

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

@MadameSheema
Copy link
Member Author

Tested on 8.0RC1 and is working properly there, so the issue must be introduced after 8.0rc1 was released.

@kqualters-elastic
Copy link
Contributor

@MadameSheema I believe the id being populated as part of the description is only for threshold alerts, other types do not have it filled out.

@andrew-goldstein
Copy link
Contributor

@MadameSheema I believe the id being populated as part of the description is only for threshold alerts, other types do not have it filled out.

While desk testing the fix, I also couldn't replicate _id being populated in the description in older releases (for non-threshold alerts) in 7.16, 7.14, and 7.10

@MadameSheema
Copy link
Member Author

I updated the ticket accordingly, thanks

@MadameSheema
Copy link
Member Author

@deepikakeshav-qasource @manishgupta-qasource can you please help to coordinate the testing of this on 8.0 latest branch? This is top priority, thanks :)

@ghost
Copy link

ghost commented Jan 25, 2022

Hi @MadameSheema,

We have validated above issue on 8.0 main branch and it's fixed. ✅

Build Details:

Version: 8.0.0 branch
Build:9007199254740991

Screenshots:

image

image

image

image

image

image

Please let us know if we missed something !!

Thanks !

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
Projects
None yet
5 participants