This issue is a weekly reminder to check for new versions of the operating systems supported by Wazuh. In this way, we will be attentive to the new betas to check that there is no problem with the packages and the operation of Wazuh.
Frequency is estimated based on previous release dates. Use it just as a guideline.
Priority is based upon release notes content & minor/major released. Release notes should be read and based on the changes informed, a criticality level should be chosen to better adjust the testing level to be performed.
If there is a new beta or release that has not been tested, it will be necessary to build an environment with that new version of the OS in question and test it with an updated Wazuh package. Basic tests to be performed should include agent installation, server installation (for server OSs), and checking every module in Wazuh. For this purpose, we must open a specific issue for each new minor/major version found, and test the following points, making sure that Wazuh works correctly:
Agent and server (if possible) installations.
O.S. reporting in the interface.
WPK installation/upgrade / uninstall/upgrade.
Enrollment and connectivity with the manager.
FIM: Real-time and who-data engines (if available).
SCA: Policy support.
Vulnerability Detector: Vulnerability support.
Syscollector: Complete inventory.
Active Response: port blocking.
Log capture (Eventchannel for Windows and ULS for macOS).
Each OS must have one of the following check statuses:
Description
This issue is a weekly reminder to check for new versions of the operating systems supported by Wazuh. In this way, we will be attentive to the new betas to check that there is no problem with the packages and the operation of Wazuh.
Frequency is estimated based on previous release dates. Use it just as a guideline.
Priority is based upon release notes content & minor/major released. Release notes should be read and based on the changes informed, a criticality level should be chosen to better adjust the testing level to be performed.
If there is a new beta or release that has not been tested, it will be necessary to build an environment with that new version of the OS in question and test it with an updated Wazuh package. Basic tests to be performed should include agent installation, server installation (for server OSs), and checking every module in Wazuh. For this purpose, we must open a specific issue for each new minor/major version found, and test the following points, making sure that Wazuh works correctly:
Agent and server (if possible) installations. O.S. reporting in the interface. WPK installation/upgrade / uninstall/upgrade. Enrollment and connectivity with the manager. FIM: Real-time and who-data engines (if available). SCA: Policy support. Vulnerability Detector: Vulnerability support. Syscollector: Complete inventory. Active Response: port blocking. Log capture (Eventchannel for Windows and ULS for macOS).
Each OS must have one of the following check statuses:
Check the current table: