Wazuh VS wazuh-packages

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

found something from GitHub discussions; was able to remove a pre-removal-script first:

Hello u/HerefortheLAN! As a workaround, you can install the agent from sources. The process is a little more involved than installing a package, but you can use this step-by-step guide: https://documentation.wazuh.com/current/deployment-options/wazuh-from-sources/wazuh-agent/index.html Please note that the issue that you mentioned is currently being worked on here, so a fix for this should be available relatively soon. Let us know if you have any problems with this. Regards!

Hello u/zmiramf The error message you are getting is because you are setting the IP value between <>, the IP must be in the format key: value On the other hand, please note that you are posting a public IP address and anyone viewing this post can see it, for security reasons you may want to edit the post to not show a public IP. I have created this issue to improve the config.yml file and avoid the use of such delimiters if it proceeds. As my coworker correctly comments, if you use the -a option it does not fail because the config.yml file is auto-generated, but if you want to use the functionality of generating the certificates independently, you must set the IP values as I have commented.

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

We will investigate this issue, please stay tuned: https://github.com/wazuh/wazuh-packages/issues/2030

Upgrading to Ubuntu 22 includes some upgrades to the GLIBC library and dependencies that trigger an error in the Filebeat module. We included a fix into Filebeat configuration file to avoid seccomp usage in the Filebeat. Take a look at our Filebeat configuration template https://github.com/wazuh/wazuh-packages/blob/v4.3.10/unattended_installer/config/filebeat/filebeat.yml

We are working on creating an installation package for Alpine systems, we estimate that version 4.4.0 of Wazuh will already have this type of installation, you can follow the progress here: https://github.com/wazuh/wazuh-packages/pull/1715

So I created a PR to solve that issue: instead of rolling back whole wazuh-* installations, it just reverts to the backed up default state, then removes the backup.

We have detected this problem. We opened this issue to solve as soon as possible https://github.com/wazuh/wazuh-packages/issues/1694 Meanwhile, you could harden your installation with the proposed solution mentioned in the issue. I hope it helps you, don't hesitate to ask us if you have any doubts.