David Jose Iglesias Lopez

Finally, we implemented a different approach in https://github.com/wazuh/wazuh/issues/14520

This development design is not going to be implemented. We are opting for a solution to check the sinchronization status as stated in 14520

Finally, we implemented a different approach in https://github.com/wazuh/wazuh/issues/14534

Hello @antonisnyc94, First of all, thank you for your contribution. The behavior you indicate is very strange and might be exposing a bug. To further troubleshoot, we can first identify...

Related to #608

Necessary steps: - Review the impact of native GuardDuty logs in the decoders and rules - Do we maintain support for both Kinesis + native GuardDuty? - Generate sample logs...

We should follow an approach similar to https://github.com/wazuh/wazuh/issues/12937

I would like to suggest a few other improvements to ease the user's understanding of the different modules. In this case, I propose we stop using both `manager` and `server`...

The Wazuh API is capturing an OperationalError raised by sqlalchemy when trying to access the RBAC database. There is no way to differentiate between a corrupted database or a no...

We need to investigate if this comes from 4.3, if it does it will be a Known issue for 4.4.