wazuh-documentation VS Wazuh

First of all, the Wazuh dashboard, created from Kibana, is an individual package, and as so, could be replaced by another package, and this could be not based on Kibana. Depending on the features you are missing in the default Wazuh dashboard, maybe it would be better to use a simpler solution. One options is to just create new visualizations from inside the installed dashboard. Another option would be creating a different package with the modifications you see fit. - For the first option, here you have a tutorial, as it has not yet been added to the documentation: https://github.com/wazuh/wazuh-documentation/issues/5511 - For the second option, all code to create the packages is located in https://github.com/wazuh/wazuh-packages. If none of this solutions is enough for your problem, the APIs you would need to control in your custom dashboards are the ones for the Wazuh server and the Wazuh indexer: - Wazuh API(accessed by port 55000): https://documentation.wazuh.com/current/user-manual/api/index.html#restful-api - Indexer API(accessed by port 9200): https://www.elastic.co/guide/en/elasticsearch/reference/current/rest-apis.html

You can store both alerts and events ( archive logs ) in Wazuh Indexer. (https://github.com/wazuh/wazuh-documentation/issues/4433)

Thank you u/granth515 for your feedback! We have created this issue to add this information.

Yes, now you should create custom alerts for those events according to your needs. I should not recommend activating the logall option in a production environment. This will take up a lot of your disk space with duplicated events. However, if you want to see archives in Elasticsearch is necessary to follow these steps https://github.com/wazuh/wazuh-documentation/issues/4433.

There is currently no feature for excluding specific SCA rules however this feature has been requested here and would be added to the roadmap for future releases.

I use Wazuh instead. Greenbone CE is severely limited and requires payment for anything beyond the very basic. Super simple installation more features.

Seems like something that should be documented somewhere more official than a random reddit post for sure. Added it to https://github.com/wazuh/wazuh/issues/1112 for good measure.

Hmm, I've really been wanting to try Wazuh but since all our endpoints (Win10/11) are running a German locale I've run into https://github.com/wazuh/wazuh/issues/16842 when checking the compliance checks (CIS benchmarks) on a test installation of 4.6.

Monitoring & Active Measures - Exporting firewall events to an external time-series database like I describe above is good to see who is touching your firewall or accessing your web site. Using an Intrusion Detection System / Intrusion Prevention System (IDS/IPS) such as open-source Suricata, which is a free package on pfSense, and deploying file system integrity monitoring, such as the open-source Wazuh on the exposed server are also good approaches to protecting yourself.

We are actively working on enhancing the system to allow users to mark vulnerabilities as "not vulnerable" or hide them. You can track the progress of this enhancement on the following GitHub issue: (Enhancement - Mark Vulnerabilities as Not Vulnerable).

Hello, thanks for using Wazuh, I will try to answer your questions: 1- I am going to check with the team in charge to see if there is a way. 2- Untriaged is a default value that is placed on vulnerabilities that do not have low, medium or high values https://github.com/wazuh/wazuh/issues/12675 3- As in the previous point, the providers of vulnerability lists have not provided the data.

Agents getting frequently pending and disconnecting