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.
IE/Windows, Chrome, Firefox are using different proxy settings. Sometimes the proxy which should be used by browsers restricts the access to the internet (company policy). In this case applications has to use another proxy.
So this feature is useful.
Some Rules has been updated and does show a "Recommended" version, even if the version you got isn't flagged as insecure or EoL.
Right now we use the word "Recommended" in both cases.
This will be changed, so that Insecure and EoL triggers "Recommended".
And a different installed version than the latest known version from the vendor, will say "Suggested".
When you see that the version we "Suggest" or "Recommend" is older or different from the one you just installed or updated to, then you are most welcome to send us a chat message, write a short message here on the forum or simply wait a day.
We are (in most cases) "alerted" automatically when you have a newer version and it ends up on our automatic "to do list". Normally, these new or unknown versions are updated / added within a day, but feel free to ping us if you are impatient to have a Rule updated.