Import a Scan
Required Tenable.io Vulnerability Management User Role: Basic, Scan Operator, Standard, Scan Manager, or Administrator
You can import scan results into Tenable.io. You cannot import results from scans run more than 15 months ago.
Imported scans always belong to the default network. For more information, see Networks.
Note: Tenable.io supports scan imports up to 4GB in size.
To import a scan in the new interface:
-
In the upper-left corner, click the
button.
The left navigation plane appears.
-
In the left navigation plane, click Scans.
The Scans page appears.
-
In the upper-right corner of the page, click the Tools button.
A menu appears.
-
Click Import Scan.
Your file directory appears.
-
Browse to and select the scan file you want to import.
If the scan file is a .nessus or .db file, the Import plane appears.
If the scan file is any other file type, the Scan Import window appears.
- Do one of the following:
- If the scan file is a .nessus or .db file:
- In the Password box, type the password to allow Tenable.io to view the scan.
- (Optional) To show the scan results in dashboards, select the Show in Dashboard? check box.
- Click Import.
- If the scan file is any other file type, specify if you want the scan results to appear in dashboards:
- Click Yes to show the scan results in dashboards.
- Click No to prevent the scan results from appearing in dashboards.
Note: Clicking Cancel cancels the import.
The Scans page appears, and the imported scan appears in the scans table.
Tenable.io begins processing the imported scan results. Once this process is complete, the imported data appears in the individual scan details and aggregated data views (such as dashboards). This process can take up to 30 minutes, depending on the size of the import file.
Tip: If the imported data does not appear in the individual scan results or aggregated data views after a reasonable processing time, verify that you are assigned adequate permissions for the imported targets in access groups.
- If the scan file is a .nessus or .db file: