Skip to main content

The dashboard was working great however over the last couple of days it is showing that I have more patches to apply than I really need. For example it shows I have 23 new patches that are critical but when I click on the 23 then go to open up devices needing any of these patches the lists are empty. It’s been this way for a couple of days now. Is there something that updates the dashboard that is separate from the device scans? With the devices showing they do not need this patch but the dashboard showing the 23 critical updates for different devices something is obviously not in synch. 

Thanks

I have the same issue, I was wondering if there is a way to force dashboard to refresh? My dashboard doesn’t reflect what I have at all and take (days+) to refresh. I also had the same patch list issue where you click on a pending patch and it’s empty. We are using automox to make sure we are up to date, this made security very unreliable.

Same issue here, I have a LOT of machines that when I tell it to scan, its not updating the list of patches needing installed.  Further, I am getting an instant failure when my install policies run, on the majority of my systems.

We are seeing this same problem as well. Difficult to know where we need to focus when you dive down into the data from the dashboards just to learn it’s not accurate. 

Did you ever find a fix for this? We’re having the same issue, and the support team has been zero help. They are basically saying that there is no issue. If we can’t get proper dashboard metrics and the vendor hasn’t been able to fix the issue for 2 months, then it’s clear we need to be moving to another product. So that’s exactly what we’re going to do.

I’ve been doing vuln management as my primary role for 10+ years now. Bad data is a real moral killer. 

 

From my experience, and I’ve used a lot of the tools in the industry. Don’t rely on any one tools dashboard to create an outcome. If something isn’t working, sure support will need to iterate, and even engaging them will take up your valuable time. Be prepared to put in the sweat to help them reproduce it and have the receipts to back it up. At the end of the day, one still needs to find a way.

Here is my journey:

 

First I’m collecting data

Set my expectations

  • These CMDB assets should show fully patched within X days

Analyze the data and alert

  • For each asset in CMDB have code answer the following:
    • Does the pre-patch report show any pending patches
    • Does the vulnerability data show any pending patches (vuln classification is key here)

If the answer to either question above is true, build a list of impacted devices for further investigation.

 

Getting better

This eventually led to taking that output list, and applying known “fixes” by manipulating tags in Automox to run worklets that replay the steps any engineer would take manually that we could code.

 

After that, we find the exact assets that truly need attention. This has worked great. Over time that list becomes less. You discover ways to improve overall configuration management. 

 

 

Reply


Terms & ConditionsCookie settings