- #HOW TO USE NESSUS KEY MANUAL#
- #HOW TO USE NESSUS KEY FULL#
- #HOW TO USE NESSUS KEY PASSWORD#
- #HOW TO USE NESSUS KEY DOWNLOAD#
#HOW TO USE NESSUS KEY DOWNLOAD#
If the data is not finished processing, and we are unable to download the scan report into Kenna after these tries, the connector will automatically fail and will not restart until the next scheduled connector run. Once you've kicked off the connector, Kenna will invoke the scan Export up to 3 times, pausing 1 second in-between each try.Īttempt the scan Download up to 180 times, pausing 60 seconds in-between each try.
#HOW TO USE NESSUS KEY MANUAL#
If you have created any manual tags OR any tags were created off of metadata from other connectors that tag info will be removed and will be refreshed once those other connectors are rerun. Each time the connector is run, ALL tags within Kenna will be removed and the Tenable tag metadata re-created. This setting will assist in keeping your Tenable metadata in sync with Kenna. This setting will allow you to NOT create any Tags within Kenna based on the Tenable.io Scan metadata. This setting will allow you to NOT create any Tags within Kenna based on the Tenable Nessus Scan metadata. If you do not want the asset last seen time in Kenna to be the scanner reported last seen time.
#HOW TO USE NESSUS KEY FULL#
(Note: For the first run of a new connector, we will need to conduct a full import, even if this is enabled.) This will help with connector run time, as we are no longer asking for all data, but rather just the data that has changed since our last run. If you’d like to only import the data that has changed since the last time we’ve run the connector, please ask your CS team or Support to enable incremental imports. To get these settings enabled or for more information, please contact Support, or your Customer Success Engineer. The following settings can be enabled on the backend for Tenable Importer connectors. “Created” within Kenna is the date the vulnerability was first imported to Kenna “Last Seen” within Kenna is the most recent date the Tenable scanner found the vulnerability “Found” within Kenna is when the scanner first found the vulnerability When importing your Tenable data the following criteria are used to populate those date fields. Within Kenna you will notice several dates in the Vulnerabilities tab. These tags can be used during search queries or to create Risk Meter groups. The following metadata from Tenable will be converted into tags within Kenna.
![how to use nessus key how to use nessus key](https://www.shorebreaksecurity.com/wp-content/uploads/2020/01/Screenshot_2020-01-30_10-19-01.png)
What Tenable items are turned into Kenna Tags? *Please note that for the XML Connector, there will not be any Tags imported. Not mapped to a scanner field.Īll of these items are converted to tags within Kenna. We will autoclose any vulnerability not seen on the next connector import (by the same connector).ĭate the vulnerability was first imported to Kenna. What Tenable items are synced with Kenna items? **If you are using Tenable Nessus, please check either “Use Kenna Virtual Tunnel” or “Use Kenna Agent” depending on which is deployed in your environment. Select the frequency at which you want to run your Kenna Nessus Importer connector (The Scan List box will populate after you enter the Access and Secret Keys as well as the Host information. Select which scans you would like to import. When entering the host IP and port, there is no need to prefix with as it is not required (:443)
#HOW TO USE NESSUS KEY PASSWORD#
Once you’ve selected the Nessus Importer from the Connectors page, the following screen will appear.Įnter the Access Key & Secret Key (Username and Password will be deprecated by Tenable as announced around 09/2020) for the service account you wish to leverage.Įnter the Host information for your scanner. *If you are using on-premise Tenable Nessus, you will need to have the Virtual Tunnel or Kenna Agent deployed within your network.Ĭonfiguring the Tenable Importer in Kenna User Prerequisites/Tenable Importer Connector Setup If you currently use the Nessus API Importer connector today and want to migrate to use the Tenable.io connector, please contact your CX representative or Support for recommended approach. During our tests, we have seen the Tenable.io connector run twice as fast as Nessus API Importer connector runs, when running with very similar datasets.įor information on the differences between the two connectors, please see the Nessus API Importer vs Tenable.io Connector Comparison Chart. Individual scan IDs are no longer required. The Tenable.io connector uses the Tenable cumulative DB. The benefits of this connector include the following: Important: We strongly suggest using the Tenable.io connector with Tenable.io data instead of using the Nessus API Importer. The Nessus API Importer is a generic Importer designed to import data from Tenable Nessus, or Tenable.io.
![how to use nessus key how to use nessus key](https://artsskiey.weebly.com/uploads/1/2/3/8/123844778/747948419.jpg)
Use the Nessus API Importer to ingest your Nessus vulnerability scan information into Kenna to assist you in reducing risk across your environment.
![how to use nessus key how to use nessus key](https://docs.tenable.com/nessus/commandlinereference/Content/Resources/Images/RegisterScannerOffline1.png)
![how to use nessus key how to use nessus key](https://docs.tenable.com/nessus/commandlinereference/Content/Resources/Images/RegisterScannerOffline3.png)
Tenable's Nessus is an on premise vulnerability scanner designed to make vulnerability scanning easy and simple.