Dashboards
Dashboards summarize what is happening on your watchlists: how many action plans are still open, which vulnerabilities need attention, and how remediation is moving.
Open Dashboards from the sidebar, or go to Dashboards. The Cockpit is the place to act on a short list of priorities. Dashboards are the place to measure the same perimeter over a period you choose.
Counts follow the watchlists you can view. Organization administrators see every watchlist in the organization. Other members see the watchlists they have access to.
Numbers are refreshed on a schedule, typically every few minutes. A watchlist you just created can stay empty until VulnPilot finishes matching it. See Why is a card empty?.
What your plan includes
Every plan that can open Dashboards includes a period filter, the Ingested vulnerabilities chart, and Latest news.
Plans with personalized dashboards add the rest:
- Filters for watchlist, vendor, priority, and remediation status.
- KPI cards, distribution charts, and lists scoped to your watchlists.
- Several dashboards, each with its own cards. You can add, hide, resize, and reorder those cards.
The layout is saved on your user account and follows you the next time you sign in.
Filters
The filter bar stays at the top of the page. The same filters apply to every card on the dashboard you are viewing, and they stay in place when you switch dashboards.
The period defaults to the last 30 days. Presets include the last 7 or 90 days, this month, last month, this quarter, last quarter, and year to date. You can also pick a custom range. There is no all-time option: every view covers a bounded window.
Most cards compare the selected period with the window of the same length immediately before it. The percentage sits beside the number.
- An increase that means more exposure (open action plans, exploited vulnerabilities, a longer time to remediate) is shown in amber.
- An increase that is an improvement is shown in green. That applies to Fixed action plans and to Avg hours to exploit published (a longer delay before an exploit is published).
- No change means the two periods match.
- A dash means the previous period was zero, so a percentage cannot be computed. Hover the dash to see that explanation.
On a personalized dashboard you can also narrow the perimeter:
| Filter | What it keeps |
|---|---|
| Watchlist | One watchlist, or All for every watchlist you can view. |
| Vendor | Vulnerabilities that affect a product from that vendor inside the selected watchlists. |
| Priority | A BeeScore band: Immediate, Out-of-Cycle, Scheduled, or Defer. |
| Status | Action plans in New, Pending, Ongoing, Completed, or Dismissed. |
Priority bands use the personalized BeeScore:
| Priority | BeeScore |
|---|---|
| Defer | Below 2.0 |
| Scheduled | 2.0 up to, but not including, 4.5 |
| Out-of-Cycle | 4.5 up to, but not including, 6.5 |
| Immediate | 6.5 and above |
A few cards ignore part of the filter bar. Those exceptions are called out in the sections below.
The first dashboard
The first time you open Dashboards on a personalized plan, you get one dashboard named Dashboard. It contains:
- Four KPI cards: Action plans fixed vs not fixed, High priority, Mean-Time-To-Remediate (MTTR), and Exploited vulnerabilities.
- Vulnerabilities over time and Ingested vulnerabilities, each on its own row.
- By remediation status and Vulnerabilities by priority level, side by side.
- Most affected vendors.
- Latest news affecting perimeter and Hot / trending, side by side.
Add card restores anything you hide and adds the cards that are not on this layout yet.
KPI cards
Several numbers are links. They open action plans, the monitor, or the products catalog with filters that match the card.
| Card | What it counts |
|---|---|
| Action plans fixed vs not fixed | Distinct action plans as of the end of the period. Fixed is Completed. Not fixed is New, Pending, or Ongoing. Dismissed plans are in neither count. Each number opens the matching action plans. |
| High priority | Vulnerabilities on action plans created in the period whose personalized BeeScore is Out-of-Cycle or Immediate (4.5 and above). Opens the monitor. |
| Mean-Time-To-Remediate (MTTR) | Average time from action-plan creation to the first time the plan was marked Completed, for plans completed in the period. The line under the value shows the 25th percentile, the median, and the 75th percentile. Durations under 24 hours are shown in hours. Longer durations are shown in days. |
| Exploited vulnerabilities | Vulnerabilities on action plans created in the period that are tagged as actively exploited or known exploited. Opens the monitor. |
| Vulnerabilities added to the watchlists | Distinct vulnerabilities on your watchlists whose publication date falls in the period. Opens the monitor. |
| Affected products | Products on the selected watchlists that are affected by vulnerabilities on action plans created in the period. The second number is the total products configured on those watchlists. The affected count opens the products catalog. |
| PoC / weaponized | Vulnerabilities on action plans created in the period that have a public proof of concept. Opens the monitor. |
| Avg vulns released / day | Vulnerabilities added to the watchlists, divided by the length of the period. |
| Avg hours to exploit published | Average time from publication to the earliest exploit, proof-of-concept, or known-exploited date, for action plans created in the period where that date is on or after publication. |
| Vulnerabilities in new | Vulnerabilities whose action plan is still New at the end of the period. Opens action plans filtered to New. |
MTTR stays on Insufficient data until at least three action plans in the filter have a completion time. The card then shows how many samples it has. It does not display a zero in place of a mean.
Charts
Vulnerabilities over time
This chart follows your watchlists and the other filters.
Each point is the stock of vulnerabilities at that moment, taken from action-plan status history:
- Affecting perimeter — status is New, Pending, or Ongoing.
- Completed — status is Completed.
- Dismissed — status is Dismissed.
Buckets are days when the period is 90 days or shorter, and weeks when it is longer. The subtitle under the title states which one is in use.
Ingested vulnerabilities
This chart counts vulnerabilities published in VulnPilot during the period, across the whole platform. Watchlist, vendor, priority, and status filters leave it unchanged. It is available on every plan.
- Daily shows how many vulnerabilities were published in each bucket.
- Cumulative adds those buckets to the number of vulnerabilities already published before the period started.
Buckets follow the same day-or-week rule as Vulnerabilities over time.
Distributions
These three charts follow the full filter bar.
- Most affected vendors — the ten vendors with the most distinct vulnerabilities on action plans created in the period.
- By remediation status — distinct vulnerabilities on your watchlists, grouped by status at the end of the period: New, Pending, Ongoing, Completed, and Dismissed.
- Vulnerabilities by priority level — distinct vulnerabilities on action plans created in the period, grouped into Immediate, Out-of-Cycle, Scheduled, Defer, and Not available (no personalized BeeScore).
Small slices are drawn large enough to stay visible. The legend shows the real count.
Lists
A list at the default width shows 10 rows. Expand it to show 20.
Latest news
Articles published in the period. On a personalized dashboard the title is Latest news affecting perimeter: an article is listed when it cites a vulnerability that appears on the selected watchlists. On a basic dashboard the title is Latest news and the list includes every article in the period.
Each row links to the article source and shows the source name and publication date when VulnPilot has them.
Hot / trending
Vulnerabilities currently marked trending on the selected watchlists, ordered by personalized BeeScore. Each row links to the vulnerability and lists the watchlists it appears on.
The period, vendor, priority, and status filters do not change this list. It always reflects the current trending set for the watchlists you selected.
WatchLists with no activity
Watchlists you can view that had no displayed action plan created during the period. Editing an existing action plan, or changing its status, does not count as activity. Each name opens that watchlist.
The watchlist filter and the period apply. Vendor, priority, and status do not.
Arrange dashboards
These controls are available on plans with personalized dashboards.
Add, rename, and delete a dashboard
Add dashboard creates an empty dashboard and selects its name so you can rename it immediately. A new dashboard starts with no cards. Use Add card to choose what belongs on it.
You can keep up to 12 dashboards. The Add dashboard button is disabled at that limit.
Rename a dashboard from its ⋯ menu, or double-click the name. Press Enter to save, or Escape to keep the previous name. A name can be up to 80 characters. A blank name is ignored.
Delete is in the same menu. Confirm with Delete dashboard. The last remaining dashboard cannot be deleted.
Add, move, resize, and hide cards
Add card lists every card that is not already on the open dashboard. Choosing one appends it at the end.
Hover a card to use its controls:
- Drag the grip to reorder cards.
- Expand widens a chart or a list to the full row. Shrink returns it to its previous width. KPI cards stay a fixed size.
- Hide removes the card from this dashboard. Add card puts it back. Hiding a card does not delete its data.
An empty dashboard shows: “This dashboard has no cards. Use Add card to choose the metrics you want to follow.”
Frequently asked questions
Why is a card empty?
Perimeter cards stay empty until your watchlists have action plans in the selected period. Matching starts in the background after you create or edit a watchlist and covers vulnerability events from the last 30 days. See Creating and maintaining a watchlist.
A filter can also hide every row. Set the watchlist back to All, widen the period, and clear vendor, priority, and status.
Ingested vulnerabilities and Latest news on a basic plan depend only on the period. If those are empty, no vulnerability or article was published in that window.
Why does the trend show a dash?
The previous period of the same length had a value of zero. VulnPilot does not invent a percentage for that case. The tooltip on the dash says so.
Why does MTTR say “Insufficient data”?
Fewer than three action plans in the current filters were completed in the period, so a mean and quartiles would not be meaningful. Widen the period or include more watchlists. The card reports the sample size it does have.
Why does “Ingested vulnerabilities” ignore my watchlist?
That chart is the volume VulnPilot published for everyone, grouped by publication date. Use Vulnerabilities over time and Vulnerabilities added to the watchlists for counts limited to your perimeter.