Hello Davide,
Let's see if we can address all these issues one by one.
First, I would like to know the situation with your agent 2 which is not showing vulnerabilities (we can talk about the time zone later).
- Since all the agents have the same OS (Windows 10) something that may be affecting the number of vulnerabilities on each should be related to the hotfixes installed.
Please let me know what you get from these command. (execute them in your manager)
sqlite3 /var/ossec/queue/db/001.db 'select * from sys_hotfixes'
sqlite3 /var/ossec/queue/db/002.db 'select * from sys_hotfixes'
sqlite3 /var/ossec/queue/db/003.db 'select * from sys_hotfixes'
I would say that we expect to have 0 vulnerabilities if all the patches have been installed on a Windows machine.
We have three sources to construct the list of vulnerabilities of Windows systems. First, we have the NVD with the CVE information, then we have the Microsoft API where we get the relation between certain CVE and the patch that fixes it, and finally the Microsoft catalog with information about supersedence KB. Sometimes the information from those places is not accurate and let us without so many options to correlate the information and we have to wait for those sites to update their information.
One last thing we can try is to install a well-known vulnerable package like Wireshark 2.4.5 in agent 2 to see if it really getting the vulnerabilities it should.
We can talk about the FIM issue later, but I would like to clarify something in case this is the issue. The configuration you mentioned is correct, but it should be in the
ossec.conf file on the agent side, and then you should restart the wazuh agent service.
Putting that setting in your manager won't work since the Linux manager doesn't have a path like that.
I hope we can solve all this. Regards!