Description

When we have an automatic email reports configuration and there are no alerts to be reported that day (e.g the rule or group of rules that we have configured in reports have not triggered during the day), the report will not be sent.

This is not good behavior because it can lead the user to think that the automatic reports are not working.

Let's also say that I have to sen

Description of Problem:CMake Warning (dev) at C:/devel/vcpkg/scripts/buildsystems/vcpkg.cmake:195 (_add_library):

Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target. Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

OpenSCAP Version:1.4.0

Operating Sys

Hi team,

I have noticed that the log examples found in 0610-win-ms_logs_rules.xml don't match their rules.
It is due the fields providerName and channel aren't correct.

https://github.com/wazuh/wazuh-ruleset/blob/725a0155cfde0a849729d9d174f03e1453e31242/rules/0610-win-ms_logs_rules.xml#L37-L63

To match rules 63103, 63104 and 63105, the logs must have matched before rules `60

Hello folks,

I think it'd be great if every ENV VAR used in the images would be explained in the README.md, and also it can be included in the Wazuh official documentation once they're ready.

Feel free to share your thoughts on this here.

Regards

Hi team,

In our purpose to divide the app into alerts and states, we're going to unify all the alerts into global dashboards.

To do this we're going to have to unify all the current dashboards in one place, and we should be able to switch between them, as well as switch between agent view and overview in a simple and agile way.

Dynamic display loading has already been implemented using JS

Hello team!

According to https://www.elastic.co/guide/en/elasticsearch/reference/7.2/security-api-put-user.html it's possible to manage Elastic users by using API like the following example:

curl -X POST "localhost:9200/_security/user/jacknich" -H 'Content-Type: application/json' -d' 

Elastic tasks can be enhanced by allowing to create users and manage their attributes and pas

The section, referring to the hotfixes option, This option is enabled by default but no included in the initial configuration. is misspelt (no -> not)

Documentation link: https://documentation.wazuh.com/3.12/user-manual/reference/ossec-conf/wodle-syscollector.html#hotfixes

Hello team,

We've detected a non-intuitive behavior on the following command specified on the install from sources page in our documentation:

curl -s -o install_api.sh https://raw.githubusercontent.com/wazuh/wazuh-api/v3.7.2/install_api.sh && bash ./install_api.sh download

This command, which is specified to download the API in all versions of our documentation (in this c

Description
Documentation link to Wazuh Splunk in the README.md is broken:

Steps to reproduce

1. Go to README.md
2. Click on Documentation link (which redirects to https://documentation.wazuh.com/current/installing-splunk/index.html)
3. You can see the redirect is broken

Best regards,

Jose

Hello,

Since we're setting up xpack security in Kibana, we don't need the NGINX component anymore.

• Remove NGINX from Kibana instance.

Regards

The local_ip parameter in the remote section of the manager config is not exposed in this puppet module.

https://documentation.wazuh.com/3.12/user-manual/reference/ossec-conf/remote.html

For that matter neither are allowed-ips, denied-ips and ipv6. But I do not have a good way to test these so I have left them out of my patch.