The Vulnerability Detection module generates alerts upon the detection of new vulnerabilities or the resolution of existing vulnerabilities, such as through package updates, removals, or system upgrades. However, while these conditions are necessary, they are not always enough for alert generation, which depends on specific detection scenarios.
Operating System Alerts Operating system alerts are not generated during the initial inventory scan. Upon the first sync of a Wazuh agent with the Wazuh manager, changes to the operating system version or recent patches are not seen as new events. Alerts are triggered only in later scans upon detection of such changes.
Package Alerts Alerts about package changes are generated only when a vulnerability is added to or removed from the inventory due to package installation or removal. This requires that the event be captured during a scheduled Syscollector scan. No alerts will be generated if changes occur while the Wazuh agent is stopped or if they are detected right after an agent restart.
Additional Considerations
Yes, that's exactly right—new CVEs added monthly won't trigger "Active" alerts on an unpatched system since the package inventory hasn't changed (and content updates don't generate alerts). Patching would detect the resolution during the next Syscollector scan, triggering a "Solved" alert.
For more details, you can refer to this. https://documentation.wazuh.com/current/user-manual/capabilities/vulnerability-detection/how-it-works.html Let me know if you have more questions!