A security dashboard full of green KPIs can sit on top of a growing pile of risk. “98% of critical vulnerabilities closed within SLA” is a good KPI; it says nothing about the one internet-facing server with a vulnerability attackers are exploiting today. That second fact is a key risk indicator (KRI). KPIs measure the performance of controls. KRIs measure the exposure the controls are supposed to reduce, and they are tied to risk appetite: each one has a threshold above which someone must act.
This page extends Cybersecurity KPIs, which covers performance metrics and the MTTD/MTTR clocks.
1 · KPI vs KRI in One Table
| KPI | KRI | |
|---|---|---|
| Question | Are we doing the work well? | How exposed are we right now? |
| Typical form | Rate, coverage %, time to complete | Count of open exposures, age of the worst ones |
| Time sense | Mostly lagging — what got done | Leading — what could go wrong next |
| Anchored to | Team targets and SLAs | Board-approved risk appetite |
| When it turns red | Fix the process | Escalate the risk to its owner |
| Example | EDR coverage across managed endpoints: 97% | Endpoints with no active protection: 41 |
▸ The pair often measures the same thing from opposite ends. 97% coverage and 41 unprotected endpoints can be the same fact — but only the KRI tells you the 41 includes three domain controllers.
2 · 24 Pairs Across 12 Domains
Two KPIs and two KRIs per domain. Read across a row: the KPI is the effort, the KRI is what that effort is supposed to drive down.
| Domain | KPIs (performance) | KRIs (exposure) |
|---|---|---|
| Identity | Phishing-resistant MFA coverage · privileged-access review completion | Privileged accounts without strong MFA · stale or orphaned accounts still active |
| Attack surface | Internet-facing asset inventory coverage · exposed-service remediation time | Unknown internet-facing assets found · critical services exposed to the internet |
| Vulnerabilities | Known-exploited vulnerability remediation time · critical vulnerability closure rate | Known-exploited vulnerabilities open · ageing critical backlog |
| Configuration | Critical configuration compliance rate · high-risk misconfiguration closure rate | High-risk misconfigurations outstanding · unauthorised configuration drift |
| Endpoint | EDR coverage · endpoint isolation response time | Endpoints without active protection · malware containment delays |
| Email & social | Reported-phish triage time · malicious email blocking rate | Confirmed credential-phishing incidents · business email compromise attempts |
| Network | Segmentation control coverage · time to close unapproved inbound exposure | Unsegmented paths to critical systems · unauthorised open ports or services |
| Application & API | Secure code review completion · API security test coverage | Critical application flaws in production · unauthenticated or weakly protected APIs |
| Cloud | Cloud finding remediation time · least-privilege access review completion | Publicly exposed cloud resources · excessive cloud privileges outstanding |
| Data | Sensitive-data discovery coverage · data-loss alert resolution time | Sensitive data exposed or misrouted · unencrypted critical data stores |
| Detection & response | Mean time to detect · mean time to contain | High-severity alerts past SLA · confirmed incidents growing in scope |
| Resilience | Backup restore-test success rate · recovery exercise completion | Restore failures during testing · recovery objectives (RTO/RPO) missed |
3 · Thresholds Turn Numbers into Decisions
A KRI without a threshold is just another number. Each one needs three bands, an owner, and a named action when it crosses into amber or red. The values below are illustrative starting points for a mid-sized organisation; your own should come from your risk appetite statement.
| KRI | Green | Amber | Red — escalate |
|---|---|---|---|
| Known-exploited vulns open on internet-facing systems | 0 | 1–2, under 7 days old | Any older than 14 days |
| Privileged accounts without phishing-resistant MFA | 0 | 1–3 with an approved exception | Any without an exception |
| Unknown internet-facing assets found this month | 0–2 | 3–10 | More than 10, or any hosting data |
| Publicly exposed cloud storage | 0 | — | Any not on the approved public list |
| High-severity alerts past SLA | Under 2% | 2–5% | Over 5%, or any on a crown-jewel system |
| Restore failures in last quarter’s tests | 0 | 1 non-critical system | Any critical system |
▸ Notice how many reds are “any”. For exposures that attackers actively hunt, the right threshold is often zero, with a documented exception process — not a percentage that hides the one that matters.
4 · The KEV Clocks
Most organisations cannot patch everything, so the vulnerability KRIs should count what is actually being exploited, not everything a scanner reports. The public reference is CISA’s Known Exploited Vulnerabilities (KEV) catalog. Its operating directive for US federal agencies, BOD 22-01, sets two remediation clocks that work well as a benchmark anywhere:
| Vulnerability | BOD 22-01 deadline | Use it as |
|---|---|---|
| KEV entry, CVE assigned 2021 or later | 2 weeks | The red line for internet-facing systems |
| KEV entry, older CVE | 6 months | An outer limit — most teams should be far faster |
| Not in KEV, high exploit probability | No federal clock | Rank with FIRST’s EPSS score plus asset criticality |
CISA can set a shorter deadline for an individual entry. EPSS (Exploit Prediction Scoring System, from FIRST) estimates the probability a vulnerability will be exploited in the next 30 days — a useful second sort after KEV.
5 · What Goes to the Board
The board does not need 48 numbers. It needs to know whether exposure is inside appetite, which KRIs are red, who owns them and by when they will be green.
- Pick 6–8 KRIs tied to your top risks — typically KEV exposure, privileged MFA gaps, unknown external assets, public cloud exposure, alerts past SLA and restore failures.
- Show the trend over the last four quarters, not just today’s value.
- Every red gets an owner and a date — or a formally accepted risk signed by that owner.
- Pair with two KPIs — MTTD and MTTR — so the board also sees whether the team is getting faster.
Bottom line
- KPIs measure effort, KRIs measure exposure — you need both, and boards need mostly the second.
- Pair them — every KPI should drive a KRI down; if it doesn’t, question the KPI.
- Thresholds or it isn’t a KRI — green, amber, red, an owner and an action.
- Zero is a valid threshold for what attackers actively hunt.
- Sort by exploitation — KEV first, then EPSS and asset criticality.
Sources & method. Domains and metric names reflect common security-metrics practice. KEV deadlines from CISA Binding Operational Directive 22-01 (November 2021); EPSS from FIRST. Threshold values are illustrative, not a standard, and should be set from your own risk appetite. Original analysis; no third-party graphics or text reproduced.
← Back to Cyber security