Prioritization
How to add CISA KEV and EPSS columns to a scan export in Excel or Google Sheets
Add KEV, ransomware, due date and EPSS columns to a Nessus CSV in Excel or Google Sheets with five formulas, then sort so exploited findings come first.
By Brandon Sooknanan, Founder, Varaxon Technologies · · 8 min read
A scan export tells you how severe each finding is. It does not tell you which ones attackers are using today. CISA's Known Exploited Vulnerabilities catalog and FIRST's EPSS scores do, and both are free files you can open in a spreadsheet. This guide adds them to your scan export as extra columns, with no scripts and no command line.
You need Excel, Google Sheets or LibreOffice Calc. We ran every formula on 16 November 2026 in LibreOffice Calc against the live KEV and EPSS files and a 10-row sample scan we built for this guide. The formulas use only functions that Excel and Google Sheets have too. If you would rather use a terminal, checking scan results against CISA KEV from the command line does the same job.
1. Get the three files
| File | Where it comes from |
|---|---|
| Your scan export | A CSV from your scanner. In Nessus: open the scan, choose Export, then CSV, and keep the default columns. |
| The KEV catalog | https://www.cisa.gov/sites/default/files/csv/known_exploited_vulnerabilities.csv |
| Today's EPSS scores | https://epss.empiricalsecurity.com/epss_scores-current.csv.gz |
The EPSS file is compressed. Unzip it first so you have a plain .csv. macOS and Linux open .gz files directly; on Windows, use 7-Zip if File Explorer will not open it. On 16 November 2026 the KEV file had 1,781 rows and the EPSS file had 406,741, which is well inside what Excel and Google Sheets can hold.
2. Put them in one workbook as three sheets
- Open your scan export and name its sheet
Scan. - Add the KEV file as a second sheet and name it
KEV. In Google Sheets, use File, Import, Upload and pick "Insert new sheet(s)". In Excel or Calc, open the CSV and move or copy its sheet into your workbook. - Add the EPSS file the same way and name the sheet
EPSS. - On the
EPSSsheet, delete row 1. It is a comment line that starts with#model_version. After that, row 1 should readcve,epss,percentile.
Check the columns before you go on, because the formulas below depend on them. The letters in this table are the layout of our sample, a default Nessus CSV. Your export may put the same things in other columns, so read your own header row.
| Sheet | Column | What it holds |
|---|---|---|
| Scan | B | CVE (one CVE ID per cell in our sample) |
| Scan | C | CVSS base score |
| KEV | A | cveID |
| KEV | H | dueDate |
| KEV | I | knownRansomwareCampaignUse |
| EPSS | A | cve |
| EPSS | B | epss |
Before the formulas: one CVE per cell
The lookups match the whole cell. A cell that holds two CVE IDs, such as CVE-2021-44228, CVE-2021-45046, matches nothing, so a finding that is on KEV would be left unmarked with no error to warn you. Filter the CVE column for a comma, a semicolon or a space. If any cell holds more than one CVE, fix it before you add the formulas:
- Add a column called
Finding IDand number every row (1, 2, 3 and so on) before you split anything. That number is how you will know which rows came from the same finding. - For each cell with several CVEs, copy the row once per CVE and leave one CVE in each copy. Keep the same Finding ID and the same host, port and plugin details on every copy.
- Later, when you sort and count, treat rows that share a Finding ID as one finding. A finding's band is the best (lowest) band among its rows.
3. Add five columns to the Scan sheet
A default Nessus CSV uses columns A to M, so the first free column is N. Type the headings in row 1, put each formula in row 2, then copy the five cells down to the last row of your scan.
| Column | Heading | Formula in row 2 |
|---|---|---|
| N | KEV | =IF(B2="","",IF(COUNTIF(KEV!$A:$A,B2)>0,"KEV","")) |
| O | Ransomware | =IF(N2="KEV",INDEX(KEV!$I:$I,MATCH(B2,KEV!$A:$A,0)),"") |
| P | KEV due | =IF(N2="KEV",INDEX(KEV!$H:$H,MATCH(B2,KEV!$A:$A,0)),"") |
| Q | EPSS | =IFERROR(INDEX(EPSS!$B:$B,MATCH(B2,EPSS!$A:$A,0)),"") |
| R | Band | =IF(O2="Known",1,IF(N2="KEV",2,IF(C2>=9,3,4))) |
What each one does:
- KEV counts how many times the CVE appears in the KEV list. One or more means attackers are using it.
- Ransomware copies CISA's ransomware field for that CVE:
KnownorUnknown. - KEV due copies the date CISA gave US federal agencies to fix it. If you see a number such as 45401 instead of a date, format the column as a date.
- EPSS looks up the chance, from 0 to 1, that the CVE will be exploited in the next 30 days. With more than 400,000 rows to search, this column can take a few seconds to fill.
- Band turns the other columns into a fix order: 1 is on KEV and used by ransomware, 2 is on KEV, 3 is CVSS 9.0 or higher, 4 is everything else.
Rows with no CVE, such as an untrusted certificate, get blank KEV and EPSS cells, because neither list can say anything about a finding without a CVE ID. The Band formula then goes by the CVSS score alone: band 3 if it is 9.0 or higher, band 4 if not.
4. Sort so the exploited findings come first
Select the whole table and sort by two columns: Band from smallest to largest, then EPSS from largest to smallest. Bands 1 and 2 are your work for this week. Inside bands 3 and 4, EPSS puts the findings most likely to be attacked next at the top.
Here is what our sample looked like after sorting. It had 10 findings: 9 with a CVE and 1 without.
| Band | Findings | What was in it |
|---|---|---|
| 1: KEV, used by ransomware | 3 | CVE-2024-3400 (PAN-OS), CVE-2021-44228 (Log4Shell), CVE-2019-0708 (BlueKeep) |
| 2: KEV | 2 | CVE-2022-22965 (Spring4Shell), CVE-2023-44487 (HTTP/2 Rapid Reset) |
| 3: CVSS 9.0 or higher, not on KEV | 1 | CVE-2023-38408 (OpenSSH) |
| 4: Everything else | 4 | CVE-2024-6387 (OpenSSH), two weak TLS cipher findings and one certificate finding |
Two things stood out. HTTP/2 Rapid Reset is rated High, not Critical (CVSS 7.5), so a list sorted by severity alone would have put it below the Critical OpenSSH finding, even though Rapid Reset is on KEV and that OpenSSH CVE is not. And every KEV due date in the sample had already passed, the oldest in December 2021. A finding like that is not new work; it is overdue work.
5. Count what you found
Three more formulas, placed in any empty cells to the right of the table, give you the numbers for a summary line. Change 5000 if your scan has more rows.
| What it counts | Formula |
|---|---|
| Findings on KEV | =COUNTIF(N2:N5000,"KEV") |
| KEV findings used by ransomware | =COUNTIF(O2:O5000,"Known") |
| Findings with an EPSS score of 0.5 or more | =COUNTIF(Q2:Q5000,">=0.5") |
Start the first count at row 2, not row 1, or the heading "KEV" is counted as a finding. These formulas count rows. If you split any multi-CVE cells in step 2, a finding with three KEV-listed CVEs would be counted three times, so count the distinct Finding IDs instead (filter the KEV column, or use a pivot table on Finding ID). In our sample the first two counts were 5 and 3. One sentence built from them, such as "5 of the 10 findings are being exploited, and 3 of those are used by ransomware groups", tells a client more than a severity chart does.
6. Keep it current
- KEV changes most weeks. CISA added 15 entries in the first two weeks of November 2026. Download the CSV again and replace the
KEVsheet before each review. - EPSS is rescored every day. Replace the
EPSSsheet when you start a new review, and note the date of the file you used. - Keep the sheet names the same and the formulas pick up the new data without any changes.
- A CVE that is not on KEV is not safe. KEV lists confirmed exploitation only. That is why the sort uses EPSS for everything else.
This works well for one scan at a time. It gets harder with several scanners, hundreds of hosts, or when you need to show what changed since last month. For that last part, see how to compare two vulnerability scans.
If you would rather not maintain the spreadsheet
We built Varaxon Scan Hub to do these lookups for you. Upload a scanner export and it checks every finding against CISA KEV, shows the EPSS score, ranks the findings in fixed bands with KEV and ransomware first, and writes an evidence-led report your client can follow. You can see sample reports first, or look up a single CVE with the free CVE checker.
Common questions
Does this work with OpenVAS, Qualys or Rapid7 exports?
Yes, as long as each row has one CVE ID in its own cell and you point the formulas at the right columns. Some exports put several CVEs in one cell, separated by commas. Split those into one CVE per row first, as step 2 describes, or the lookups will not match and a KEV-listed finding can go unmarked.
Can I use VLOOKUP or XLOOKUP instead of INDEX and MATCH?
Yes. XLOOKUP is shorter if your spreadsheet has it. We used INDEX and MATCH because they work the same way in every version of Excel, in Google Sheets and in LibreOffice Calc.
Why sort by band before EPSS?
Because KEV is evidence that a vulnerability is being exploited now, and EPSS is an estimate of what is likely to be exploited soon. Evidence goes first. EPSS then orders the findings that are not on KEV.
How often should I refresh the KEV and EPSS sheets?
Before every review. CISA updates KEV whenever it confirms new exploitation, often several times a week, and EPSS scores are recalculated daily.
Turn your next scan export into a client-ready report.
Run a free pre-flight check