The intention is that after an installation users get a warning when there are known vulnerabilities. No matter how this is implemented. Think about the following scenario: A user installs the current version of an application (like web browser), but the application has vulnerabilities. The daily VulnDetect will start in some hours. Now the user browses in the web and gets infected or hacked (the vulnerability is abused). And after that he can see in the list of installed applications (in VulnDetect) that this software has vulnerabilities. So the user will be very upset, because VulnDetect does already know about the vulnerability but did not warn him in time! This could really be a problem for VulnDetect.

This feature has been implemented in the Corporate Version of VulnDetect. Here you see a screen shot, how it looks there: [image: 1707658091190-2024-02-11_14h22_54.png] You can select one or more apps from a very long list of applications and then install them (deploy them) on your computers (to a group of computers). Therefore, I mark this topic as Implemented.

This feature has been implemented in the Corporate Version of VulnDetect. Here you see a screen shot, how it looks there: [image: 1707585590417-c7942578-c615-4c54-90cc-e0adb99db7ab-image.png] The first icon downloads the recommended version. The second icon copies the download link of the recommended version to the clipboard. Therefore, I mark this topic as Implemented.