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

Inconsistent wazuh.cluster.name filter #6654

Closed
Rebits opened this issue May 8, 2024 · 0 comments · Fixed by #6658
Closed

Inconsistent wazuh.cluster.name filter #6654

Rebits opened this issue May 8, 2024 · 0 comments · Fixed by #6658
Assignees
Labels
level/task Task issue type/bug Bug issue

Comments

@Rebits
Copy link
Member

Rebits commented May 8, 2024

Wazuh Rev Browser
4.8.0 RC1 Any

Description

The default setting for the vulnerability detection dashboard incorporates a filter labeled wazuh.cluster.name set to the value "wazuh1". Initially, it appears this filter is not intended for modification. However, it is possible to deactivate this filter and apply negation by accessing the "Change all filters" menu.

Preconditions

  1. Full environment with Vulnerability detection enabled

Steps to reproduce

  1. Go to Vulnerability Detection > Inventory
  2. Using "Change all filters" negate the wazuh.cluster.name filter
  3. Go to Vulnerability Deteciton > Dashboard
  4. Check that dashboard is not working as expected. In addition, cluster filter now is not negated.

Expected Result

  1. Use should not be able to edit wazuh.cluster.name filter

Actual Result

  1. Wazuh.cluster.name filter can be edit, leading into inconsistent dashboard

Screenshots
image

Video

filter_inconsistent.webm
@davidjiglesias davidjiglesias added type/bug Bug issue level/task Task issue labels May 9, 2024
@wazuhci wazuhci moved this to Triage in Release 4.8.0 May 9, 2024
@asteriscos asteriscos self-assigned this May 9, 2024
@wazuhci wazuhci moved this from Triage to Backlog in Release 4.8.0 May 9, 2024
@wazuhci wazuhci moved this from Backlog to In progress in Release 4.8.0 May 9, 2024
@asteriscos asteriscos linked a pull request May 9, 2024 that will close this issue
6 tasks
@wazuhci wazuhci moved this from In progress to Pending review in Release 4.8.0 May 9, 2024
@wazuhci wazuhci moved this from Pending review to Done in Release 4.8.0 May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue type/bug Bug issue
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants