configuration assessment alerts are too many
|
|
|
|
|
|
I want ‘recommendations’ I can search and consult online on a periodic basis to create my remediation action plan; I don’t like ‘alerts’ that look like reactive incidents, and get in the way of my operational routine
|
|
|
|
|
|
configuration assessment new machine-generated ‘recommendations’ I see in search are too many
|
|
|
|
|
|
I find it difficult to understand the priority of alerts and recommendations and understand what should I remediate first
|
|
|
|
|
|
I find it difficult to understand what the resulting impact/improvement would be to my infrastructure if I apply a specific recommendation, I am not sure how much it will benefit my operations
|
|
|
|
|
|
I and my manager need to understand how much improvement we will get, and in which area, if we apply a specific recommendation
|
|
|
|
|
|
Configuration assessment scans are too frequent, alerts get repeated too often - I don't have time to patch, my cycles are longer
|
|
|
|
|
|
Configuration assessment scans are too frequent, I think they consume un-necessary resources on my agents every day
|
|
|
|
|
|
I would like to be able to schedule the configuration assessment scans to run less frequently (i.e. once a month or once a week) so I have time to plan for remediation activities in my operational cycles
|
|
|
|
|
|
a single list of alerts and recommendation is too broad; I need to more easily pivot on each vertical technology (i.e. SQL or Active Directory), so I can involve the experts in my organization to remediate each of their specific areas
|
|
|
|
|
|