wazuh-documentation
wazuh-packages
wazuh-documentation | wazuh-packages | |
---|---|---|
5 | 11 | |
164 | 90 | |
3.0% | - | |
9.9 | 9.7 | |
2 days ago | 6 days ago | |
JavaScript | Shell | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wazuh-documentation
- wazuh-archive* index not found in Stack Management / Index Patterns.
-
Custom dashboard with custom visualization to completely replace wazuh dashboard?
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
-
About the log retention management
You can store both alerts and events ( archive logs ) in Wazuh Indexer. (https://github.com/wazuh/wazuh-documentation/issues/4433)
-
What's the default login ID / password for the (self-served) Wazuh dashboard?
Thank you u/granth515 for your feedback! We have created this issue to add this information.
-
Decoders for Watchguard firewalls
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.
wazuh-packages
-
Help: Dashboard installation failing with "can't read etc/opensearch_dashboards.yml no such file or directory"
found something from GitHub discussions; was able to remove a pre-removal-script first:
-
Is there a work around for the Wazuh-agent installer issue with Debian 12?
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!
-
Wazuh installation assistant - Indexer installation
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.
- "INFO: Could not connect to API id [default]: 3099 - ERROR3099 - Invalid credentials" after fresh install
-
Custom dashboard with custom visualization to completely replace wazuh dashboard?
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
-
Wazuh-indexer and wazuh-manager fails with timeout after launching VM
We will investigate this issue, please stay tuned: https://github.com/wazuh/wazuh-packages/issues/2030
-
Wazuh all-in-one with Ubuntu 22.04.1
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
-
Wazuh Agent build on alpine linux
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
-
Stuck at indexer cluster start
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.
-
9200 /9300 weak ssl encryption on wazuh indexers
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.
What are some alternatives?
howtheysre - A curated collection of publicly available resources on how technology and tech-savvy organizations around the world practice Site Reliability Engineering (SRE)
wazuh-ansible - Wazuh - Ansible playbook
Wazuh - Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
alpine-pkg-glibc - A glibc compatibility layer package for Alpine Linux
OSSEC - OSSEC is an Open Source Host-based Intrusion Detection System that performs log analysis, file integrity checking, policy monitoring, rootkit detection, real-time alerting and active response.
wazuh-docker - Wazuh - Docker containers
sysmon - Sysmon and wazuh integration with Sigma sysmon rules [updated]
wazuh-ruleset - Wazuh - Ruleset
lynis - Lynis - Security auditing tool for Linux, macOS, and UNIX-based systems. Assists with compliance testing (HIPAA/ISO27001/PCI DSS) and system hardening. Agentless, and installation optional.
wazuh-dashboard-plugins - Plugins for Wazuh Dashboard