---
title: 07.05 Vulnerability Imports and EPSS / KEV Enrichment
description: Core SimpleRisk imports scanner exports into the Vulnerabilities list and looks up EPSS scores and CISA KEV status for their CVEs. Here's what the…
---

[Skip to content](https://support.simplerisk.com/kb/07-05-vulnerability-imports-and-enrichment#main-content)

English

Show submenu for translations

[Customer portal](https://support.simplerisk.com/tickets?hsLang=en)

[![SimpleRisk logo of a man walking a tight rope](https://support.simplerisk.com/hs-fs/hubfs/simplerisk_logo_long_small-4.png?width=377&height=72&name=simplerisk_logo_long_small-4.png)](https://www.simplerisk.com/)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Customer portal](https://support.simplerisk.com/tickets)
- [Contact us](https://www.simplerisk.com/about-us/contact-us)

[Contact us](https://www.simplerisk.com/about-us/contact-us)

 How can we help you?

- There are no suggestions because the search field is empty.

1. [SimpleRisk Knowledge Base](https://support.simplerisk.com/kb?hsLang=en)
2. [Administrator Guide](https://support.simplerisk.com/kb/administrator-guide?hsLang=en)
3. [07 Integrations](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#07-integrations)

# 07.05 Vulnerability Imports and EPSS / KEV Enrichment

## Core SimpleRisk imports scanner exports into the Vulnerabilities list and looks up EPSS scores and CISA KEV status for their CVEs. Here's what the enrichment sends off the server and how to turn it off from its Settings Hub tile, where uploaded files are kept and why systemd PrivateTmp breaks that, the permissions to grant, and the VM settings page.

## Why this matters

The **Vulnerabilities** page is part of Core SimpleRisk. Users import scanner exports (CSV or XLSX) into it, see each vulnerability once across every asset it affects, and triage the ones that matter into the risk register. The Vulnerability Management Extra adds scanner integrations on top, but nothing in this article needs it. What users do on the page is covered in the User Guide, starting with [Importing Scanner Exports](https://support.simplerisk.com/kb/05-05-importing-scanner-exports?hsLang=en). This article is the operator's side, and three parts of it need a decision or a check from you.

First, **SimpleRisk now makes outbound requests on its own, by default.** Once a day, and after imports that bring in new CVEs, it downloads CISA's Known Exploited Vulnerabilities catalog and asks FIRST.org for the EPSS scores of the CVEs your imported vulnerabilities carry. Only CVE IDs leave the server. Some security teams will be fine with that and some won't, and you should know which yours is before the upgrade, not after.

Second, **uploaded files go through a directory on disk, and the web server and the queue worker both have to see it.** On Debian and Ubuntu, Apache runs with a private `/tmp` by default, and the default location sits in `/tmp`. Every import on such a server fails until you move the directory.

Third, **imports run on the queue.** If the queue workers aren't running, an import sits at queued forever and enrichment never happens.

## Before you start

- **Administrator access**, for the permissions, the enrichment switch and `config.php`.
- **Shell access to the SimpleRisk server**, if you need to set the upload directory.
- **The queue workers running.** Imports and enrichment are both queue jobs, picked up by `cron_queue_loader.php` and `cron_queue_worker.php` (see [The Cron Jobs](https://support.simplerisk.com/kb/02-07-the-cron-jobs?hsLang=en)).
- **A plan for the imported text.** Imported titles and descriptions are stored as they appear in the file, and the Encrypted Database Extra does not cover them yet. Built-in encryption for imported text is planned, so until then treat the database and its backups as holding that text in the clear.

## Step-by-step

### 1. Grant the permissions

The Vulnerability Management permissions are defined in Core, and the upgrade that added importing grants all five to every administrator user and administrator role. Nobody else gets them automatically. Grant them on roles the way you would any other permission:

- **Allow Access to Vulnerability Management "Vulnerabilities" Menu** (`vm_vulnerabilities`) — the Vulnerabilities page, read-only.
- **Able to Import Vulnerabilities** (`vm_import`) — importing files, saved column mappings and the import history. It's new, and deliberately narrow: an analyst who loads the monthly export doesn't need to be able to create risks.
- **Able to Approve Vulnerability Triage to Risk** (`vm_triage_approve`) — triaging vulnerabilities into risks. It only works together with **Able to Submit New Risks** and **Able to Modify Risk Details**; attaching to an existing risk also needs **Allow Access to "Risk Management" Menu**.
- **Able to Reject Vulnerability Triage to Risk** (`vm_triage_reject`) — hiding vulnerabilities, and returning hidden ones to triage.
- **Allow Access to Vulnerability Management "Configure" Menu** (`vm_configure`) — the **VM settings** page.

Two neighboring permissions shape what an importer can do. **Allow Access to "Asset Management" Menu** lets an import create assets the file names that SimpleRisk doesn't have yet; without it, those rows are skipped. **Able to Verify Assets** decides whether those new assets start out verified. The assets an import creates and the risks triage creates from an imported vulnerability are filed under the user's own teams, whether or not Team Separation is on, so the ordinary team rules decide who else sees them. An administrator, or a user on no team, creates them with no team. (See [Permission Reference](https://support.simplerisk.com/kb/03-03-permission-reference?hsLang=en).)

### 2. Decide on EPSS and KEV enrichment

Enrichment is on by default. Here's exactly what it does:

- **CISA KEV.** One `GET` of the public catalog at `https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json`. Nothing is sent but the request itself.
- **FIRST.org EPSS.** `GET` requests to `https://api.first.org/data/v1/epss` whose only parameter is a comma-separated list of CVE IDs, up to 100 per request. No finding title, asset name, host name, IP address, credential or anything identifying your install is sent.
- **Which CVEs.** Only the CVEs of vulnerabilities imported from files. Findings synced by the Vulnerability Management Extra's scanner integrations don't carry CVE IDs and aren't looked up.
- **How.** Requests go through the proxy configured on the Settings Hub's **Security** tile (**Proxy Web Requests**), with the same certificate checks as SimpleRisk's other feeds. Redirects aren't followed, so the CVE list can't be forwarded anywhere else. Allow outbound HTTPS to `www.cisa.gov` and `api.first.org`.
- **When.** A daily pass, plus a pass after an import that brings in CVEs it hasn't looked up yet. Out-of-schedule passes are at least 15 minutes apart.
- **How much.** One pass asks about roughly 10,000 CVEs (100 requests of 100, with a short pause between requests) and stops after 10 minutes at most. When there's more to do, it queues a follow-up pass, so an install holding 50,000 CVEs is fully enriched after about five passes. Stalest CVEs go first. Up to 50,000 distinct CVEs are considered; past that, the rest aren't enriched and a notice is logged.
- **When it fails.** A failed pass backs off and retries. If FIRST.org or CISA answers "too many requests," SimpleRisk waits as long as they ask, up to six hours. A KEV catalog that arrives garbled or noticeably incomplete is ignored and clears nothing.

Users see the results in the **EPSS** and **KEV** columns. A vulnerability counts as known exploited when either the imported file or CISA's catalog says so. A fetched EPSS score replaces the one in the file. An air-gapped server that can't reach either host simply shows the values from the files and logs the failures; nothing breaks.

**To turn it off**, open the **Settings cog**, choose the **System** chip and then the **Vulnerability enrichment** tile. The page has one switch, **Enrich vulnerabilities with EPSS scores and CISA KEV status**, with a note under it spelling out what goes to FIRST.org and what comes from CISA. Flip it and the change saves straight away; there's no separate Save button. The **Status** card below shows when the **Last enrichment pass** started (or **Not run yet**), how many CVEs have EPSS or KEV data, how many of those are on the CISA KEV list and, while FIRST.org or CISA has asked SimpleRisk to back off, the time it resumes. Only administrators see the tile or can open the page.

Scripts can do the same thing through the API with an administrator's API key:

```
curl -X PATCH \
  -H "X-API-KEY: {admin-api-key}" \
  -H "Content-Type: application/json" \
  -d '{"enabled": false}' \
  https://{your-simplerisk-host}/api/v2/vulnerabilities/enrichment
```

Send `{"enabled": true}` to turn it back on. Either way, the change is written to the audit trail with the name of whoever made it. `GET /api/v2/vulnerabilities/enrichment` reports the same things the **Status** card shows. The GET needs `vm_vulnerabilities` or an administrator; the PATCH needs an administrator.

The setting behind it is `vuln_enrichment_enabled`, `true` by default. A missing setting also counts as on, so to turn enrichment off from the database, set it to `false` rather than deleting it. The page or the API is the better route, because both record who changed it. Turning it off stops every request on the next pass, and the values already fetched stay where they are.

### 3. Put the upload directory where both processes can reach it

An uploaded file is kept on disk from the moment a user uploads it until the import finishes. By default the directory is `simplerisk_vuln_imports` inside the system temporary directory (usually `/tmp/simplerisk_vuln_imports`). SimpleRisk creates it on the first upload.

The web request that receives the file and the queue worker that imports it both have to see the same directory. **Where Apache runs under systemd with `PrivateTmp=true`, which is the Debian and Ubuntu default, Apache's `/tmp` is a private copy the queue worker can't see.** Every import then fails, and the import's result says "The uploaded file is no longer available." Set the directory explicitly in `simplerisk/includes/config.php`:

```
define('VULN_IMPORT_UPLOAD_DIR', '/var/lib/simplerisk/vuln_imports');
```

Then create it for the web server's user:

```
sudo install -d -m 0700 -o www-data -g www-data /var/lib/simplerisk/vuln_imports
```

The directory has to meet four conditions, and an upload is refused with "The file could not be stored on the server." until it does:

- It's **outside the SimpleRisk directory**, which is the web root.
- It's **owned by the user the web server runs as**.
- Its mode is **0700 or 0750**. SimpleRisk won't loosen or tighten a directory it didn't create; anything else is treated as a configuration error to fix.
- The **queue worker runs as that same user, or as root**, so it can read the files.

Files are stored under random names, never under the name the user uploaded. They're deleted when the import finishes, and anything older than 24 hours is cleaned up by the import job's hourly housekeeping. An import that still hasn't finished by then fails as expired, and a file uploaded but never imported is dropped after about an hour.

Back up nothing here. It's working space, not data.

### 4. Check the size limits and the worker's memory

The import has its own size cap: 50 MB, or PHP's `upload_max_filesize` and `post_max_size` when they're lower. It doesn't use the SimpleRisk **Maximum Upload File Size** setting or MySQL's limits, because the file is never stored in the database. The import page shows users the limit actually in effect. Beyond the size, a file can have up to 100,000 data rows and 200 columns, and an XLSX workbook up to 500,000 cells.

XLSX files are loaded whole, so both the upload request and the queue worker raise PHP's memory limit to 1,024 MB while they read one. They only ever raise it, never lower it. On a container or VM with tight memory, that's the number to plan for; CSV imports need far less.

### 5. Know what the VM settings page does without the Extra

Administrators, and users with `vm_configure`, see a **VM settings** entry under **Vulnerabilities** in the sidebar. Without the Vulnerability Management Extra it has a lock icon and opens a dimmed, read-only preview of the Extra's settings with a banner. The banner offers **Activate** when the Extra is installed and your subscription includes it, says the Extra is required when it isn't installed, and shows the subscription message when the subscription doesn't include it. A non-administrator with `vm_configure` is told that an administrator can set it up. Nothing on the preview can be changed or submitted. With the Extra active, the same entry opens the real settings page. Setting up the integrations is in [The Vulnerability Management Extra](https://support.simplerisk.com/kb/05-03-the-vulnmgmt-extra?hsLang=en).

### 6. Upgrade the Extra right after Core

If you run the Vulnerability Management Extra, upgrade it immediately after you upgrade SimpleRisk; Core always goes first. Between the two steps the new **Vulnerabilities** list works and still shows the older Extra's **View Risks** tab, but the older Extra's untriaged scanner findings aren't in the list, so they can't be triaged, and scheduled syncs pause until the Extra's own upgrade (see [Upgrading Extras](https://support.simplerisk.com/kb/02-04-upgrading-extras?hsLang=en)). Neither upgrade moves or changes data the Extra has already synced.

## Common pitfalls

- **Leaving the upload directory in a private `/tmp`.** The most likely support call after the upgrade on Debian or Ubuntu. Uploads succeed, the column matching works, and then every import fails with "The uploaded file is no longer available." Set `VULN_IMPORT_UPLOAD_DIR` before anyone imports.
- **A queue worker running as a different user.** A worker started from another account's crontab can't read files owned by the web server user. Run it as the web server user, or as root.
- **Imports stuck at queued.** The queue workers aren't running. The same symptom shows up as email that never sends.
- **Turning enrichment off by deleting the setting.** A missing setting means on. Use the **Vulnerability enrichment** page, or set it to `false`.
- **Expecting EPSS and KEV on scanner-synced findings.** Only imported vulnerabilities are enriched. A team that relies on KEV for prioritization and runs only the Extra's integrations sees dashes in those columns.
- **Granting triage without the risk permissions.** `vm_triage_approve` on its own shows no triage buttons. The user also needs **Able to Submit New Risks** and **Able to Modify Risk Details**.

## Related

- [Importing Scanner Exports](https://support.simplerisk.com/kb/05-05-importing-scanner-exports?hsLang=en)
- [Working the Vulnerabilities List](https://support.simplerisk.com/kb/05-06-working-the-vulnerabilities-list?hsLang=en)
- [The Vulnerability Management Extra](https://support.simplerisk.com/kb/05-03-the-vulnmgmt-extra?hsLang=en)
- [Permission Reference](https://support.simplerisk.com/kb/03-03-permission-reference?hsLang=en)
- [The Cron Jobs](https://support.simplerisk.com/kb/02-07-the-cron-jobs?hsLang=en)
- [File Upload Size Limits](https://support.simplerisk.com/kb/12-07-file-upload-size-limits?hsLang=en)
- [Settings Reference](https://support.simplerisk.com/kb/13-01-config-settings-reference?hsLang=en)

- [FAQs](https://support.simplerisk.com/kb/faqs?hsLang=en)
- [SimpleRisk Extras](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#main-content)

    - [Vulnerability Management Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#vulnerability-management-extra)
    - [Team Separation Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#team-separation-extra)
    - [Import-Export Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#import-export-extra)
- [Administrator Guide](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#main-content)

    - [00 About This Guide](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#00-about-this-guide)
    - [01 Installation and Deployment](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#01-installation-and-deployment)
    - [02 Upgrades and Maintenance](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#02-upgrades-and-maintenance)
    - [03 Users and Permissions](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#03-users-and-permissions)
    - [04 Authentication](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#04-authentication)
    - [05 Customization](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#05-customization)
    - [06 Configuring Risk and Compliance](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#06-configuring-risk-and-compliance)
    - [07 Integrations](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#07-integrations)
    - [08 The API](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#08-the-api)
    - [09 Encryption and Data Security](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#09-encryption-and-data-security)
    - [10 Workflows and Automation](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#10-workflows-and-automation)
    - [11 Reporting and Auditing](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#11-reporting-and-auditing)
    - [12 Operations](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#12-operations)
    - [13 Reference](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#13-reference)
- [User Guide](https://support.simplerisk.com/kb/user-guide?hsLang=en#main-content)

    - [00 Foundations of GRC](https://support.simplerisk.com/kb/user-guide?hsLang=en#00-foundations-of-grc)
    - [01 Risk Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#01-risk-management)
    - [02 Compliance Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#02-compliance-management)
    - [03 Governance](https://support.simplerisk.com/kb/user-guide?hsLang=en#03-governance)
    - [04 Asset and Data Inventory](https://support.simplerisk.com/kb/user-guide?hsLang=en#04-asset-and-data-inventory)
    - [05 Threat and Vulnerability Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#05-threat-and-vulnerability-management)
    - [06 Assessments](https://support.simplerisk.com/kb/user-guide?hsLang=en#06-assessments)
    - [07 Incident Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#07-incident-management)
    - [08 Audit and Reporting](https://support.simplerisk.com/kb/user-guide?hsLang=en#08-audit-and-reporting)
    - [09 Day-to-Day SimpleRisk](https://support.simplerisk.com/kb/user-guide?hsLang=en#09-day-to-day-simplerisk)
    - [10 Continuous Improvement](https://support.simplerisk.com/kb/user-guide?hsLang=en#10-continuous-improvement)
    - [11 Business Continuity and Disaster Recovery](https://support.simplerisk.com/kb/user-guide?hsLang=en#11-business-continuity-and-disaster-recovery)
- [SimpleRisk User Guides](https://support.simplerisk.com/kb/simplerisk-user-guides?hsLang=en)
- [Troubleshooting](https://support.simplerisk.com/kb/troubleshooting?hsLang=en)
- [SimpleRisk Hosted](https://support.simplerisk.com/kb/simplerisk-hosted?hsLang=en)
- [How To videos](https://support.simplerisk.com/kb/how-to-videos?hsLang=en)

[![favicon-1](https://support.simplerisk.com/hs-fs/hubfs/favicon-1.png?width=35&height=35&name=favicon-1.png "favicon-1")](https://www.simplerisk.com)

<https://www.facebook.com/simplerisk/> <https://www.twitter.com/simpleriskfree/> <https://www.linkedin.com/company/simplerisk/>

Copyright © 2026, SimpleRisk, Inc.