This section lists the changes in version 4.0.0. More details about these changes are provided in the changelog of each component:
The agent enrollment is now performed on the main daemon initialization. There is no need to request a key using an external CLI anymore. Agents are now able to request a key to the manager on their own if no key was defined on startup or if the manager has rejected the connection (Agents in
3.xversion are still 100% compatible with
Wazuh API RBAC: Configure users, roles, and policies to manage access permissions. Wazuh WUI now permits granular control over access to resources depending on user roles, this will allow enterprises to manage user accounts that fulfill different functions in the security of the environment.
Wazuh API is now embedded in the Wazuh manager.
Wazuh manager and agents will use TCP as the default communication protocol.
The Windows agent MSI installer is now signed using DigiCert instead of GlobalSign. DigiCert is known for being present on more Windows versions including the oldest ones.
FIM implements now a set of settings to control the module temporal files disk usage. This means that now we can choose the amount of disk space used by the report change utility. The diff option reports changes in the monitored files, to do so, it creates a compressed copy of the file and checks if it changes. This method may use a lot of disk space. Wazuh 4.0 introduces new capabilities to limit the space used.
The agent-auth tool starts the deprecation cycle (to be deprecated in v5.0.0). The agent registration on demand will still be available using CLI.
The API is now embedded in the Wazuh manager, no wazuh-api package will be installed anymore.
Wazuh manager and agents are no longer using UDP as the default communication protocol. TCP is enabled by default.
OpenSCAP policies removed from RPM and DEB packages. Folder present policies in the agent installation will be removed.
Embedded Wazuh API with Wazuh Manager, there is no need to install Wazuh API.
Migrated Wazuh API server from NodeJS to Python.
aiohttpserver for the Wazuh API.
The new Wazuh API is approximately 5 times faster on average.
Added OpenAPI based Wazuh API specification.
Improved Wazuh API reference documentation based on OpenAPI spec using redoc.
Added a new yaml Wazuh API configuration file.
Added new endpoints to manage API configuration and deprecated
Added RBAC support to Wazuh API.
Added new endpoints for Wazuh API security management.
Added SQLAlchemy ORM based database for RBAC.
Added a new JWT authentication method.
Wazuh API up and running by default in all nodes for a clustered environment.
Added new and improved error handling.
Added tavern and docker based Wazuh API integration tests.
Added new and unified Wazuh API response structure.
Added new endpoints for Wazuh API users management.
Added a new endpoint to restart agents that belong to a node.
Added and improved
qfilter in several endpoints.
Tested and improved Wazuh API security.
Added DDOS blocking system.
Added brute force attack blocking system.
Added content-type validation.
Added and updated framework unit tests to increase coverage.
Added improved support for monitoring paths from environment variables.
Added auto-enrollment capability. Agents are now able to request a key from the manager if the current key is missing or wrong.
Redhat vulnerabilities are now fetched from OVAL benchmarks.
Debian vulnerable packages are now fetched from the Security Tracker.
The Debian Security Tracker feed can be loaded from a custom location.
Allow compressed feeds for offline updates.
The manager now updates the MSU feed automatically.
CVEs with no affected version defined in all the feeds are now reported.
CVEs vulnerable for the vendor and missing in the NVD are now reported.
Changed multiple Wazuh API endpoints.
Refactored framework module in SDK and core.
FIM Windows events handling refactored.
Changed framework to access
agent-infosynchronization task in Wazuh cluster.
Fixed an error with the last scan time in syscheck endpoints.
Added support for monitoring directories that contain commas.
Fixed a bug where configuring a directory to be monitored as realtime and whodata resulted in realtime prevailing.
Fixed using an incorrect mutex while deleting inotify watches.
Fixed a bug that could cause multiple FIM threads to request the same temporary file.
Fixed a bug where deleting a file permanently in Windows would not trigger an alert.
Fixed a typo in the file monitoring options log entry.
Fixed an error where monitoring a drive in Windows under scheduled or realtime mode would generate alerts from the recycle bin.
When monitoring a drive in Windows in the format
U:, it will monitor
U:\instead of the agent’s working directory.
Fixed a bug where monitoring a drive in Windows with recursion_level set to 0 would trigger alerts from files inside its subdirectories.
Fixed an Azure wodle dependency error. The package azure-storage-blob>12.0.0 does not include a component used.
Vulnerabilities of Windows Server 2019 which do not affect to Windows 10 were not being reported.
Vulnerabilities patched by a Microsoft update with no supersedence were not being reported.
Vulnerabilities patched by more than one Microsoft update were not being evaluated against all the patches.
Duplicated alerts in Windows 10.
Syscollector now discards hotfixes that are not fully installed.
Syscollector now collects hotfixes that were not being parsed.
Support for Wazuh v4.0.0.
Support for Kibana v7.9.1 and v7.9.2.
Support for Open Distro 1.10.1.
Added a RBAC security layer integrated with Open Distro and X-Pack.
Added remoted and analysisd statistics.
Expand supported deployment variables.
Added new configuration view settings for GCP integration.
Added logic to change the
metafieldsconfiguration of Kibana.
Migrated the default index-pattern to
Security Events dashboard redesigned.
Redesigned the app settings configuration with categories.
Moved the wazuh-registry file to Kibana optimize folder.
Format options in
wazuh-alertsindex-pattern are not overwritten now.
Prevent blank page in detail agent view.
Navigable agents name in Events.
Index pattern is not being refreshed.
Reporting fails when agent is pinned and compliance controls are visited.
Reload rule detail does not work properly with the related rules.
Fix search bar filter in Manage agent of group.
Changed compliance rules groups and removed
alert_by_emailoption by default.
Let the Ruleset update tool pick up the current version branch by default.
Wazuh services are no longer enabled nor started in a fresh install.
Wazuh services will be restarted on upgrade if they were running before upgrading them.
Wazuh API and Wazuh Manager services are unified in a single wazuh-manager service.
Wazuh plugin for Kibana package has been renamed.
Wazuh VM now uses Wazuh and Open Distro for Elasticsearch.
Unit files for systemd are now installed on
Improved the upgrade of unit files.
ossec-init.conffile now shows the build date for any system.
Fixed an error setting SCA file permissions on
Added instructions to install Wazuh along with Open Distro for Elasticsearch.
Added scripts, created by the Wazuh team, that allow the user to install Wazuh and Elastic Stack automatically.
Added tabs in the installation guide to ease the navigation through the different options available.
Added a ‘More installation alternatives’ section that provides instructions on how to install Wazuh along with commercial options like Elastic Stack basic license or Splunk. This section also includes instructions on how to install Wazuh from sources.