
Cybersecurity dashboard
How many alerts are real, and how fast are incidents handled?
- Incidents
- Mean time to detect (hours)
- Mean time to respond (hours)
- False positive rate
Cybersecurity dashboards
Three dashboards for a security team: alerts, incidents, patching and phishing tests by asset group, the uptime and tickets beside them, and how fast a fix can reach production. Open any of them to see it in full, then use it as a template for your own data.



All figures are sample data.
The examples
Click a board to see all of it. Click Use template to start your own copy in Mammoth. All figures are sample data.

How many alerts are real, and how fast are incidents handled?

Are the services up while security does its work?

How quickly can a fix reach production?
Definition
A cybersecurity dashboard is one screen that shows how well an organisation detects and handles threats: how many alerts fire and how many are real, how long incidents take to detect and to contain, whether vulnerabilities are patched within their deadlines, and how many people click a phishing test. The data usually comes from the SIEM, the vulnerability scanner, the ticketing system and the phishing platform.
False positives beside the alert count.
Within SLA by severity and asset group.
Phishing test click rates week by week.
The metrics
Eight numbers. Most depend on a definition agreed first, such as when an alert becomes an incident.
How many real security events were there?
Alerts confirmed as incidents, by severity and asset group. Agree when an alert becomes an incident, or the count means nothing.
How long does a threat go unnoticed?
When the activity started and when it was detected. The start is often estimated after the fact; record how.
How long does containment take?
Detection and containment times per incident, by severity.
How much of the alert volume is noise?
Alerts and the ones closed as false positives. A rising rate means analysts' time is going on tuning, not threats.
Are known weaknesses fixed in time?
Vulnerabilities with severity, due date and patch date. Read by asset group: the critical servers matter more than the laptops.
How many people click a fake phishing email?
Test emails sent and clicked per campaign. Report-rate beside click-rate shows whether people are learning to flag it.
How much is the SOC handling?
Alerts by week and source. A drop after tuning is good; a drop after a sensor failed is not.
How much serious exposure is still open?
Unpatched critical and high findings by asset group, with their age.
How to build one
From one of the examples above to a live dashboard on your own data.
Start from any of the three boards above.
Upload a spreadsheet, or connect one of 100+ tested connectors.
Fix and combine your data once. Mammoth repeats those steps for you.
The dashboard updates on a schedule and flags data that fails a check.
Public, password-protected or sign-in only, on every plan.
14-day Pro trial · No credit card
FAQ
Last reviewed against the template catalogue.
Start from one of these templates or your own spreadsheet. Share it with as many people as you like, free.
More dashboard examples