Wondering why you may be seeing different risk meter scores, asset counts and vulnerability counts for the same risk meter between the Explore page, Dashboard page and Reporting page? The reason is due to certain pages being cached nightly and not updated in real time.
Explore Page (Live View)
Important: The Explore page will always display the “live” or “real-time” view of a risk meter score, asset counts and vulnerability counts. This live view will always represent the most up to date information that was brought in via your connector sources.
In the below example, we edited an existing risk meter in the Explore page. You’ll see the risk meter score displayed as well as the Asset/Vulnerability/Fix counts listed. This represents the “live” counts and score based on the changes we made to the risk group.
Dashboard Page (Cached View)
Important: The Dashboard page will display the risk meter score, asset counts and vulnerability counts from the previous days' cache. The numbers are refreshed each night during Cisco Vulnerability Management’s nightly processing jobs.
When you initially create a risk meter, you will see the current “live” score, “live” asset counts and “live vulnerability counts” that existed upon your initial save of the risk meter. If you edit the risk meter and any of these numbers change, the Dashboard will display the cached values until the nightly job completes.
Using the example risk meter from above, you’ll notice the Dashboard page displays the cached values for the Risk Meter Score, Asset Counts and Vulnerability Counts. These will all be updated during the next nightly cache update.
Reporting Page (Cached View)
Important: The Reporting page also displays the risk meter score, asset counts and vulnerability counts from the previous days' cache. These numbers will be refreshed each night during Cisco Vulnerability Management’s nightly processing jobs.
Again in the picture below, you’ll see that the Reporting page also displays the cached values. These will all be updated in the next nightly cache update.