We do, we just didn't get around to that yet. We have a long list of stuff to do before we make that

The width of the column "Version Number" is now adjusted, so longer version numbers like "Version 1905 Build 11629.20246" are completely shown. Also the text "Unknown version, please report" is now shown completely. So this suggestion is implemented.

Today I released the Toolbox for VulnDetect. So it would be cool if users see at the entry GetAppDetails that it is replaced by the Toolbox.

This feature has been implemented in the Corporate Version of VulnDetect. Here you see a screen shot, how it looks there: [image: 1707644944118-2024-02-10_18h17_17-1.png] 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: 1707644888083-2024-02-11_10h47_13.png] Therefore, I mark this topic as Implemented.

@OLLI_S This is not exactly what you suggested, but there should be some overlap. In the VulnDetect we have added a new feature which allows us to "flag" Rules, Channels or Products. One of these flags is "Testing". Just to show the concept I've added the "Testing" flag to SecTeer CARMA - the EoL one. If you expand the row you can see that this is "Testing". "Testing" Rules are currently shown for all users, but the idea is to make this configurable. As we go through the rules we will add this flag to Rules / Products that we don't detect correctly yet. This is different from the "Untracked" flag that you unfortunately will see for products such as Opera and Vivaldi who don't release consistent security bulletins. The "Testing" flag is currently being, well, tested, so we may change the concept slightly at some point, but basically this is similar to "Under Review". So this is not a replacement for the "?", which indicates that we need to add a Specific Rule, because we for some reason don't extract a correct version number automatically.

Yes, fantastic, I see it. Thank you for implemented my suggestion. I mark the 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: 1707587821157-2024-02-10_18h17_17.png] Therefore, I mark this topic as Implemented.

@Tom: Glad that you like my idea. If you plan to implement it in the far future then I will move my posting and your reply to a separate topic in Suggestions.

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: 1707651500245-2024-02-11_12h33_53.png] Therefore, I mark this topic as Implemented.

I am using VulnDetect Business for some months now. I added most computers of my family (wife, daughter, brother, girlfriend of brother, Virtual Machine). Soon I will add my father. My "job" is to support them (they have no high computer skills, especially my father, my brother and this girlfriend). So my brother and his girlfriend often call me and ask if their computer is OK (they are used that I call them and tell them to update some applications). But they are not often online: [image: 1593542294141-968ddf5a-069b-4d1b-8508-e13f850d2a23-image.png] So here I can not warn them that there are vulnerabilities on their systems (because I have to wait until they turn their computers on. It would be very helpful if the list of apps is updated even without a scan. So I see available updates and existing vulnerabilities and can actively warn them.

This feature has been implemented in the Corporate Version of VulnDetect. Here you see a screen shot, how it looks there: [image: 1707651331683-2024-02-11_12h33_53.png] Therefore, I mark this topic as Implemented.

The VulnDetect supports this, kind of. 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.

This suggestion is Duplicate to Additional Status for Update Available. Therefore I close it now.