Importing data from NBE or XML files

Since EventSentry does not ship with Nessus or contain any Nessus code you will need to import output files (.nbe or .xml) generated by Nessus into the EventSentry database with the es_db_nessus_import.exe command-line application. This utility ships with the product and is located in the EventSentry installation directory.

The utility takes two command-line arguments - a connection string/action name pointing to an EventSentry database, and a path to either the .nbe or .xml file generated by Nessus.

If you are automatically scheduling your Nessus scans, then you can include the es_db_nessus_import.exe utility in your script to automatically import the generated data into the EventSentry database.

es_db_nessus_import.exe <CONNSTRING>|<ACTION> <NBE FILE>|<XML FILE>

Options

A connection string pointing to the EventSentry database, the connection string needs to include a username and password.

or,

if EventSentry is installed on the same machine where you are running es_db_nessus_import.exe then you can also specify the name of the EventSentry action

A path to the Nessus .nbe or .xml file that needs to be imported into the database

It is recommended that you do not import the same Nessus scan more than once, as it will otherwise show up in the reports multiple times. If you do accidentally import the same Nessus report multiple times, then you can remove the duplicate scans using the maintenance wizard and then re-import it.

A typical output from the command-line utility will look similar to the screenshot shown below. The utility will indicate how many scans were found, how long the scans took and how many lines were processed.

clip0336