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

Feature request: Exclude vulnerability analysis and FIM events from "Security events" module #5864

Open
1 task
zbalkan opened this issue Sep 8, 2023 · 3 comments
Assignees
Labels
level/task Task issue reporter/community Issue reported by the community request/operational Operational requests type/troubleshooting

Comments

@zbalkan
Copy link

zbalkan commented Sep 8, 2023

Description

The Integrity module and vulnerability modules have their own dashboards for further analysis. But many times we find that the security events and alerts are bombarded by FIM events and vulnerability checks. The first thing we do on "Security events" module, is to exclude these events to have a clear and concise view.

For the sake of clarity an ease of use, please filter these out of Security Events module by default, so that we don't need to do it every single time.

Tasks

The steps that have to be completed in order to close the issue.

  • Exclude Vulnerability analysis and Integrity events on Security Events module by default

Additional information

image

@zbalkan zbalkan changed the title Feature request: Exclude vulnerability analysis and FIM events from security events tab Feature request: Exclude vulnerability analysis and FIM events from "Security events" module Sep 8, 2023
@AlexRuiz7 AlexRuiz7 added the reporter/community Issue reported by the community label Sep 12, 2023
@gdiazlo gdiazlo self-assigned this Sep 15, 2023
@gdiazlo
Copy link
Member

gdiazlo commented Sep 15, 2023

I understand your situation. Every Wazuh installation can have more events of one module than others. And those can mean noise in certain circumstances, like the one you describe. I think it is not possible to balance out all the possibilities a deployment can have for all users.

A possible solution would be to be able to save those filters, so a user can customize the dashboard just once, changing the default applied filters. But AFAIK, OpenSearch does not support this globally. We will need further research to reach a viable solution.

In the meantime, you can either add the filters, or create a custom dashboard for the indexed data.

@zbalkan
Copy link
Author

zbalkan commented Sep 15, 2023

Hi @gdiazlo,

Since Integrity Module and Vulnerabilities have their own dashboards, the suggested segregation might be reasonable. A FIM event is yet another log but it does not add value to the security events. When it comes to detailed investigation, we use Discovery module already. Tailoring by default or being able to tailor globally are our options to minimize the inconveniences. It's not a bug but a papercuts in this case.

@gdiazlo gdiazlo added the request/operational Operational requests label Sep 18, 2023
@gdiazlo
Copy link
Member

gdiazlo commented Sep 21, 2023

We're working on new dashboards, due to Wazuh 4.8.0 hopefully, we will consider this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue reporter/community Issue reported by the community request/operational Operational requests type/troubleshooting
Projects
None yet
Development

No branches or pull requests

3 participants