Skip to content

Vulnerability management dashboard builder

Open vulnerabilities by severity and age, remediation against SLA, and where the risk sits. Replace the numbers with your scanner export and download.

New here? — takes 2 minutes.

Vulnerability management dashboard

All scanned assets — Rolling six months to September

Open vulnerabilities

4,812
−11%

Critical open

37
−19

Time to fix critical

11 days
−4 days

Fixed within SLA

82%
+7 pts

Open vulnerabilities by severity

CriticalHighMediumLow
0
2k
4k
6k
8k
Critical: 71High: 812Medium: 2.8kLow: 2.5k
Critical: 64High: 776Medium: 2.7kLow: 2.5k
Critical: 58High: 731Medium: 2.6kLow: 2.4k
Critical: 52High: 684Medium: 2.4kLow: 2.3k
Critical: 56High: 661Medium: 2.4kLow: 2.3k
Critical: 37High: 575Medium: 2.1kLow: 2.1k
AprMayJunJulAugSep

Open vulnerabilities by age

4.8kOpen
0–30 days2.2k 46%
31–60 days1.2k 25%
61–90 days690 14%
Over 90 days732 15%

Critical and high by business unit

Manufacturing238
Retail164
Corporate IT112
Finance61
R&D37

Fixed within SLA by severity

Critical (7 days), warning76%
High (30 days), good81%
Medium (90 days), good84%
Low (180 days), good88%

4 Vulnerability Management Dashboard templates

Every template opens as a finished dashboard. Pick the closest one, then change anything.

Metrics and how to calculate them

The KPIs these templates are built on, with the formula behind each one.

Mean time to remediate
Average days from a vulnerability being detected to it being verified as fixed, by severity.
Remediation SLA compliance
Vulnerabilities fixed within their severity deadline ÷ vulnerabilities due × 100.
Vulnerability age
Days since first detection for each open finding; report the share over 90 days.
Scan coverage
Assets scanned in the last seven days ÷ assets in the inventory × 100.
CVSS
Common Vulnerability Scoring System base score from 0 to 10; 9.0+ is critical and 7.0–8.9 is high.
Known exploited share
Open CVEs listed as exploited in the wild ÷ all open CVEs × 100; fix these first.
Retest closure rate
Pentest findings retested and confirmed fixed ÷ findings raised × 100.

How to make your Vulnerability Management Dashboard

Pick a template, put your numbers in, download — about two minutes. Nothing to install; the PDF and every other format come with a SlideTeam plan.

  1. 1

    Pick your dashboard

    Click Pick Your Dashboard. This dashboard has 4 ready-made layouts, such as Vulnerability management overview and CVE tracker. Each opens finished, with example figures.

  2. 2

    Change the numbers

    Point at any widget (tap it on a phone) and choose Edit to type or paste its numbers and labels — a column copied from Excel pastes straight in. Click the dashboard's title to rename it.

  3. 3

    Use your own data

    Upload CSV or Excel takes a CSV, .xlsx or .xls file and shows exactly what it read: pick the sheet, the label column and how repeated rows are combined (sum, average, count), then Build a new dashboard or Fill this template with your columns. Not sure of the layout? Download the sample CSV and replace the numbers.

  4. 4

    Download PDF, PowerPoint, Excel and more

    Download (right end of the toolbar) lists every format: a PDF (free), PowerPoint with native charts you can still edit (right-click › Edit data), a report pack (summary slide plus one slide per chart) as PowerPoint or PDF, Excel (opens on a Dashboard sheet with live charts) and a CSV for Power BI, Tableau or Google Sheets.

  5. 5

    More options: add widgets, brand it, share

    More options (top right) shows the rest: Add widget puts in a chart, KPI tile, table, funnel or a Text / commentary box; the arrows on a widget move it and ✕ removes it; click the subtitle to edit it. Customise sets the currency, template language, slide size, brand colour and logo. Sheets / Slides shows how to open your file in Google Sheets or Slides; Share copies a link to this exact dashboard.

Common questions

What should a vulnerability management dashboard include?

Open vulnerabilities by severity and age, time to remediate, SLA compliance and scan coverage, with the business units or assets carrying the most risk. The overview template covers all of these.

How do I prioritize CVEs?

Start with CVEs known to be exploited, then weigh CVSS, exploit likelihood and how many exposed hosts are affected. The CVE tracker template lays those side by side.

Can I build this from Wazuh or another scanner?

Yes. Export vulnerability counts to CSV from your scanner or SIEM and upload them; the agent-based scan template matches the fields most agent scanners report.

How should pentest findings be reported?

Show findings by severity and category, then track each critical and high item to retest and closure with an owner and due date, as the pentest template does.

Goes well with this — from our other free tools

The figures in the example dashboards are illustrative and exist so each page shows a finished dashboard rather than an empty grid. Replace them with yours before sharing anything.