Skip to content
English
  • There are no suggestions because the search field is empty.

05.05 Importing Scanner Exports

Import a CSV or XLSX export from Tenable.io, Nessus or any other scanner into the Vulnerabilities list, match its columns, save the matching for next time, and read the import summary. Covers what an import will never change, and why.

Why this matters

Most teams already have their scanner's output. It sits in a spreadsheet someone exported last Tuesday, and the question is what to do with it. Importing that file turns several hundred rows of "plugin X on host Y" into a list where each vulnerability appears once, with every asset it affects behind it, ready to be triaged into the risk register. No scanner integration and no Extra are needed: importing is part of Core SimpleRisk.

Before you import anything, understand the one rule that shapes everything else. An import only ever adds. SimpleRisk can't tell whether the file in front of it covers your whole environment or one subnet, one business unit, or whatever filter the person exporting it happened to leave on. So when a vulnerability or an asset from an earlier file is missing from a later one, SimpleRisk doesn't read that as "fixed" or "gone." Nothing is closed, hidden, removed or rescored because a file left it out. That's deliberate. The scanner integrations in the Vulnerability Management Extra work differently, because they ask the scanner directly and know which scan found what on which asset. A file doesn't carry that knowledge, and guessing would quietly close real exposure.

Before you start

  • Able to Import Vulnerabilities on your account. It's a permission of its own, so an analyst can import without being able to triage. You also need Allow Access to Vulnerability Management "Vulnerabilities" Menu to reach the page. Administrators hold both after the upgrade that added importing. (See Permission Reference.)
  • Allow Access to "Asset Management" Menu if the file names assets that aren't in SimpleRisk yet. With it, a missing asset is created for you. Without it, rows for unknown assets are skipped and listed in the summary. Assets you create this way are assigned to your teams, and they start out verified only if you also hold Able to Verify Assets.
  • The export itself, as CSV or XLSX. The import page shows the largest file this server accepts, under the Source heading. It's 50 MB at most, and less if the server's own upload limits are lower. A file can have up to 100,000 data rows and 200 columns. An XLSX workbook can hold up to 500,000 cells, and older .xls files aren't accepted; save them as XLSX first. CSV files should be UTF-8.
  • A filtered export, if your scanner allows it. Export open findings only. A row the scanner has marked fixed is still imported as a vulnerability waiting for triage, because the import records the file's state but doesn't act on it.

Step-by-step

  1. Open the import page. Sidebar: Vulnerabilities → Vulnerabilities, then select Import Vulnerabilities at the top of the list. The page has three steps (Source, Upload and match columns, Review and import) and the Import history below them.

  2. Pick the source. Choose one of three options and select Next: - Tenable.io / Nessus — a findings export from Tenable.io or Nessus. Its columns are matched for you, and you can still change them. - Generic CSV / XLSX — an export from any other scanner. Columns with familiar names (Qualys, OpenVAS and Nessus-style headers among them) are matched for you, and you match the rest. - Saved mapping — reuse the column matching you saved during an earlier import. Pick it from Choose a saved mapping.

The source matters more than it looks. SimpleRisk recognizes a vulnerability it has already seen by the source together with the scanner's own finding ID, so the same file imported once under each source creates every vulnerability twice. Pick the source that matches where the file came from, and keep picking it.

  1. Upload the file and check the column matching. Choose the file under File. SimpleRisk reads it and shows Detected source, then a table with each Column in file, a Sample value from it, and what it will be stored as under Import as. Change any match you disagree with, or set a column to Do not import.

The fields you can match to are Finding ID, Title, Description, Severity, CVSS v3 score, CVSS v2 score, CVSS Score, CVEs, Asset Name, Asset ID, State, First seen, Last seen, EPSS and KEV. Two rules apply before you can continue: - Match at least one column to Asset Name. You can match several; for each row, the first of them that has a value is used. That's handy when some rows carry a host name and others only an IP address. - Match a column to Finding ID or to Title. With no finding ID, SimpleRisk derives one from the title and warns you that it has. The same title then always maps to the same vulnerability, which is fine for most scanners and wrong for the ones that reuse a generic title across distinct findings.

A Nessus CSV shows Detected source: Imported (file) even under Tenable.io / Nessus, because only Tenable.io's own export is recognized by its headers. That's expected: keep Tenable.io / Nessus for Nessus files, and every later Nessus import with it.

If the file looks like a Tenable.io export but you chose a different source, a warning says so. The warning only runs in that direction. A Qualys file imported under Tenable.io / Nessus gets no warning, and its rows are stored as Tenable.io findings, so importing the same file later under Generic CSV / XLSX creates them all again.

  1. Save the matching, if you'll import this kind of file again. Type a name under Save this mapping as and select Save mapping. A saved mapping keeps the source and the column matches, so next month's export from the same scanner is two clicks. Each user can keep up to 100 mappings, and names can be up to 100 characters. Mappings are yours; administrators can also see and use other users' mappings, which are labeled "(another user)."

  2. Review and start the import. Select Next to reach Review and import, which summarizes the file, the source and the mapped columns. Read the note on that step, which says the same thing as the start of this article: importing only adds data. Select Start import.

The import runs in the background, so you can leave the page. The upload is kept for an hour between the upload step and Start import; after that you'll be asked to upload it again.

  1. Watch it finish. The result panel shows Import in progress and a count of rows processed. If a batch fails, the import shows Retrying and tries again on its own; rows that were already imported are never duplicated by a retry. When it's done, the panel lists: - Vulnerabilities created and Vulnerabilities already in SimpleRisk - Assets created, Existing assets matched and Asset links created - Rows skipped, with a Skipped rows by reason table - Rows with no CVSS score or known severity (given the lowest score)

  2. Deal with skipped rows. Select Download skipped rows (CSV) for a list of every skipped row: its row number in your file (row 1 is the first row after the header), a reason code, and the reason. It deliberately contains nothing from the file itself, so open your original export next to it. The usual reasons are a row with no asset name, a row with neither a finding ID nor a title, and an asset that doesn't exist and that you don't have permission to create. Fix the file, or ask someone who can create assets, and import it again. Rows that came in the first time are left alone.

  3. Find earlier imports in the history. Import history lists each import with its Date, File Name, Source, Status, how many vulnerabilities it Created and how many rows it Skipped. Select Details to reopen an import's result panel and its skipped-rows download. You see your own imports; administrators see everyone's.

  4. Go to the list. Select View vulnerabilities. The new vulnerabilities are waiting under the default Untriaged filter. Working that list is covered in Working the Vulnerabilities List.

What an import changes, and what it never does

An import adds the vulnerabilities, assets and asset links it hasn't seen before. Everything it has seen is left exactly as it was. Importing the same file twice changes nothing the second time, and importing a file that overlaps an earlier one only adds what's new.

That also means a later file doesn't refresh anything. If a vulnerability's description, CVSS score, severity or last-seen date changed at the scanner, the values from the first import are the ones SimpleRisk keeps. A new link between an existing vulnerability and an asset the file names for the first time is added, because it only adds what the file says.

An import never:

  • closes, hides or deletes a vulnerability, including one that's missing from the newer file;
  • removes an asset from a vulnerability or from a risk;
  • changes a risk's score, text or status;
  • merges findings across sources. A finding imported from a Tenable.io file and the same finding synced by the Extra's Tenable.io integration are two rows, as is one CVE reported by two different scanners.

When a vulnerability really is fixed, deal with it on the risk side: close or update the risk it was triaged into, and remove the asset from that risk yourself if it's no longer affected. SimpleRisk won't do either on a file's say-so.

Imported titles and descriptions are stored as they appear in the file. The Encrypted Database Extra does not cover them yet; built-in encryption for imported text is planned.

Common pitfalls

  • Re-importing under a different source. This is the one that produces a list with every vulnerability in it twice. Generic and Tenable.io / Nessus imports are separate sources, and so are scanner integrations in the Extra. Save a mapping per scanner and always import that scanner's files with it.
  • Two different scanners imported as Generic. Every Generic import shares one source, so finding IDs from two scanners are matched against each other. If both number their findings the same way, a Qualys QID and an unrelated finding from another tool with the same number become one vulnerability. Keep to one Generic scanner, or match its ID column to something unique to that scanner.
  • Numeric severities. Severity is read as a word: Critical, High, Medium (or Moderate), Low, Info (or Informational, None, Log). A scale of 1 to 5 isn't recognized. Match the CVSS column too, or those rows end up with the lowest score and are counted under Rows with no CVSS score or known severity.
  • Expecting a later file to close what's fixed. It won't, by design. Plan the closing step into your remediation process, on the risk.
  • Importing a raw, unfiltered export. Informational findings and rows already marked fixed come in as vulnerabilities waiting for triage. Filter at the scanner. The list's Hide action works, but it's one row at a time.
  • Asset names that don't match. Assets are matched to SimpleRisk assets by name, ignoring case and surrounding spaces and nothing else. "web01" and "web01.example.com" are two assets. If your scanner reports FQDNs and your asset inventory uses short names, decide which wins before the first import, because an import never renames or merges assets afterward.

Related