AUDIT GUIDE, read 10 Nov 2026
Show the inputs, the rule, the date and the exceptions, and the ranking explains itself
What the auditor is checking
The question behind most audit requests is whether the same input produces the same decision, and whether a person can override it with a reason. That means three artifacts: a written rule, dated inputs and an exception log.
The rule can be short. It lists the signals, the order they are applied and the threshold for each. The inputs are the KEV flag, the EPSS probability and percentile with the score date, and the CVSS vector with its version and source. The exception log lists each override, the person and the date.
Cite each signal to its source
Name the owner of each number so the auditor can check it. CVSS is maintained by FIRST, and the specification defines the metrics and the severity bands. EPSS is published by FIRST daily, and its FAQ defines the score as a 30-day probability. KEV is maintained by CISA, whose FAQ gives the three listing criteria.
Where a platform computes its own rating, label it as the vendor's. Describe it as the vendor's rating, with the vendor's stated scale, and keep a copy of the vendor page you read. Do not present a vendor rating as an industry standard.
| Signal | Owner | Defines | Store with each decision |
|---|---|---|---|
| CVSS | FIRST | Technical severity, 0.0 to 10.0 | Version, full vector, scorer, read date |
| EPSS | FIRST | 30-day exploitation probability | Probability, percentile, score date, model line |
| KEV | CISA | Observed exploitation in the wild | Listing date, due date, ransomware field |
| SSVC | CISA (reference tree) | Decision outcome | Tree version, branch taken |
Show the rule failing safely
An auditor will ask what the rule misses. Answer with data. In the KEV Lag Ledger, 10.4% of additions (33 of 318) had a CVSS base score below 7, so a severity-only rule would have placed them outside the high band. Among the 260 additions with an EPSS score on listing day, 75.8% were below 0.10, so a probability-only rule at 0.10 would have missed most on that day.
The written rule should therefore say that KEV listing overrides the other two. State this as a design choice made because each single signal misses a share of exploited CVEs, and cite the ledger with its date range, 2025-11-10 to 2026-11-09.
Keep the evidence package small
A package that fits in four files gets read. Include the rule document, a dated export of the scored inventory, the exception log and the change history of the thresholds. Add the source pages with the date you read them.
If a federal directive applies, add the directive's reference. BOD 22-01 has been revoked and superseded by BOD 26-04, issued June 10, 2026, so cite the current one and record the date you changed over.
- Inputs: dated exports of KEV, EPSS and CVSS for the review period.
- Rule: version, approver, effective date.
- Thresholds: who set each, when, and the count of CVEs it selected.
- Exceptions: CVE, reason, owner, expiry date.
- Samples: five CVEs traced from input to outcome.
What not to say
Do not tell the auditor the platform decides. The platform computes, and your rule decides. If the platform's score is part of the rule, record the platform's version and the date, since a vendor can change a model without telling you.
Do not quote a threshold you cannot justify. FIRST states there is no universal EPSS threshold, so your number is a policy choice, and the record should say so.
A short script for the meeting
Open with the rule in one sentence: KEV-listed CVEs first, then CVEs at or above the EPSS threshold, then CVSS 9.0 and above on internet-facing assets, then the rest by SLA. Follow with the date range of the evidence behind each step. Then ask which CVEs the auditor wants traced.
Pick the trace yourself if you are asked to. Choose one KEV entry, one EPSS-selected CVE and one CVSS-only CVE, and walk each from the saved input to the outcome and the closure ticket. Three clean traces are better evidence than a dashboard.
Handling vendor scores
If your platform shows a proprietary rating, ask three questions and record the answers: what inputs the vendor says it uses, how often it is recalculated, and whether you can export the history. A platform that cannot export the history cannot support a question about last quarter. The Signal Matrix on this site marks whether each of 13 platforms documents customer weighting. A cell that reads none found on 2026-11-10 is a prompt for you to ask the vendor, since it records the reach of one search on one date.
Sources
- FIRST, EPSS frequently asked questions, read 10 Nov 2026
- FIRST, CVSS v3.1 Specification Document, read 10 Nov 2026
- CISA, BOD 26-04: Prioritizing Security Updates Based on Risk, read 10 Nov 2026
Last reviewed 10 Nov 2026.