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] Security Solution tag is not displayed when creating a dashboard from Security Solution Dashboards page #201922

Closed
MadameSheema opened this issue Nov 27, 2024 · 8 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:Explore Team:Threat Hunting Security Solution Threat Hunting Team triage_needed

Comments

@MadameSheema
Copy link
Member

Describe the bug:

  • Security Solution tag is not displayed when creating a dashboard from Security Solution Dashboards

Kibana/Elasticsearch Stack version:

  • 8.17.0 - BC1

Initial setup:

  • To have some data ingested in the instance

Steps to reproduce:

  1. Navigate to Dashboards page
  2. Click Create Dahsboard button
  3. Click Create visualization
  4. Add one of the available fields
  5. Click Save and return
  6. Click Save

Current behavior:

Image

  • Security Solution tag is not displayed

Expected behavior:

  • Security Solution tag should be displayed so the user can use it.
@MadameSheema MadameSheema added 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 Security Solution Threat Hunting Team Team:Threat Hunting:Explore triage_needed labels Nov 27, 2024
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@agusruidiazgd agusruidiazgd self-assigned this Nov 28, 2024
@agusruidiazgd
Copy link
Contributor

agusruidiazgd commented Nov 28, 2024

Hi @MadameSheema,

I’ve reproduced this behavior and investigated why the Security Solution tag is not being rendered. It turns out that the Security Solution tag has been intentionally excluded from the TagSelector because it is a managed tag in Elastic.
This change was introduced in the following PR: elastic/kibana#177089.

Relevant issues associated with this PR:

elastic/kibana#172388
elastic/kibana#172389
elastic/kibana#172390

@MadameSheema
Copy link
Member Author

Thanks for the clarification @agusruidiazgd! I was not aware about that change :)

Closing the ticket as the described behavior is the expected one.

@semd
Copy link
Contributor

semd commented Nov 28, 2024

@paulewing This is the expected behavior now, Elastic-managed tags do not appear in the tag dropdown when saving a custom dashboard, so our Security Solution tag can not be selected here. This behavior broke the pre-selection we have implemented.

@agusruidiazgd
Copy link
Contributor

@paulewing @MadameSheema The Security Solution tag is implicitly pre-selected by default. However, if the user adds a custom tag and then removes it, the dashboard is saved without the Security Solution tag, causing it to no longer appear on the Dashboards page.
Attached is the observed behavior:

Screen.Recording.2024-12-02.at.14.05.13.mov

Image
Image

@MadameSheema
Copy link
Member Author

This new behaviour is also introducing issues in some upgrade paths: #202280

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:Explore Team:Threat Hunting Security Solution Threat Hunting Team triage_needed
Projects
None yet
Development

No branches or pull requests

4 participants