cancel
Showing results for 
Search instead for 
Did you mean: 
Moderator jvredeveld Moderator
Moderator

Re: We Still Want Your Ideas about Software Vulnerability Management Products!

Are they on the current version of the app? The more recent "delta" scan logic might also help with this if they are on an older version. Could see if switching off agent polling helps as well. This was introduced in the R5 release.

https://helpnet.flexerasoftware.com/csionprem/2018R5rn_oct2018/SVM2018_R5_On_Premises_Edition_Releas...

Not 100% sure but they most likely need the R5+ agent as well.

Community Manager RDanailov Community Manager
Community Manager

Re: We Still Want Your Ideas about Software Vulnerability Management Products!

Very Good point, Agent polling can ease up the burden and also the timing of a scan for quicker processing.
Regards,
Rosen
"To understand where a system breaks, one should think like the person who built it"
0 Kudos
Community Manager RDanailov Community Manager
Community Manager

Re: We Still Want Your Ideas about Software Vulnerability Management Products!

Hi @bkelly,

In the SVR product, the ticketing system is not user-specific.
We show the total number of tickets for all users; regardless of their Roles/Groups. Thus, sub-accounts with restricted view to specific queues would anyway see the total number of tickets under root. 

A customer of ours pointed this out and requested us to change this accordingly. 
Ideally, when the user is restricted to a particular view, he should see the ticket count that he has rights to see. 

They have multiple teams who work with different ticket queues. An engineer from one team cannot see the tickets of the other teams by default.  When engineers go to the ticket manager, the number of tickets on the top is very confusing. The ticket number is for all tickets even though the user cannot really see those.

Tagging: @fh_open_ch 



Regards,
Rosen
"To understand where a system breaks, one should think like the person who built it"
0 Kudos
segilbert70
Occasional contributor

Re: We Still Want Your Ideas *SVM Cloud*

@bkelley We migrated to SVM Next last fall and there are some features I really miss from the "on-prem" version. 1. On the Patching Tab, it used to show how many machines/installs were affected by each patch. Now, I have to go back to the Assessment tab or the Dashboard to see that information again. 2. The ability to *see* what paths that the patch would target. How do we know what the cloud version patches are hitting? Do I have to manually add all the paths that come up in Assessment to make sure they are being addressed? 3. DB cleanup was much easier for a large number of hosts. In the cloud, having to manually click and delete thousands of machines at a time (my company does ~3K PC refreshes a month) is a non-starter. (Support has provided me with a script that make it a lot easier, but I can't imagine I am the only one with this issue) Thank you for providing a workaround for the Ideas page missing.
Highlighted
Moderator bkelly Moderator
Moderator

Re: We Still Want Your Ideas *SVM Cloud*

We migrated to SVM Next last fall and there are some features I really miss from the "on-prem" version.

Conversely, would you mind sharing what things about SVM Next encouraged you to move away from SVM 2019 (which is also available in the cloud)?

1. On the Patching Tab, it used to show how many machines/installs were affected by each patch. Now, I have to go back to the Assessment tab or the Dashboard to see that information again.

Some differences in how SVM Next maps patches to assessment make this non-trivial but I understand the request and will consider what might be done to address it. 

2. The ability to *see* what paths that the patch would target. How do we know what the cloud version patches are hitting? Do I have to manually add all the paths that come up in Assessment to make sure they are being addressed?

We automatically include all matching paths, and add default paths too, but as you point out there is no good way to see this in SVM Next.  The Daemon logs have the information, but it is not exposed in the user interface. It can also be found on the WSUS server, but is not easy to see. There are some timing issues in that all paths are not known when a template is created as they are dynamically assigned upon deployment. All this to say it is not as trivial a request as it may seem but will be considered. 

3. DB cleanup was much easier for a large number of hosts. In the cloud, having to manually click and delete thousands of machines at a time (my company does ~3K PC refreshes a month) is a non-starter. (Support has provided me with a script that make it a lot easier, but I can't imagine I am the only one with this issue).

Multi-select would still be onerous, I think a script is the way to go when it comes to large bulk operations. The script is documented and supported. We automatically clean up hosts that have not reported in 90 days, which is the most common ask, beyond this we'll lean on our documented API to handle such operations. 

Thanks again for taking the time to provide this valued input.

0 Kudos