Security Compliance

Nessus connectors in SEM

Typically, an agent will be installed on the system hosting Nessus, then within the connector configuration on that agent, you enable the appropriate Nessus connector and provide the directory name where the Nessus reports are written. The connector then scans for new reports, parses them, and then creates alerts based upon the report contents. The different Nessus connectors support NBE, Nessus Message, Nessus Report, and Nessus XML Report reports formats.

First published date

10/15/2018 4:58 PM

Last published date

4/25/2019 2:45 PM

Overview

This article applies to Security Event Manager (formerly Log & Event Manager).
This article provides information about Nessus connectors.

Product section

Security Event Manager

Resolution

There are four different Nessus connectors available.

Typically, an agent will be installed on the system hosting Nessus, then within the connector configuration on that agent, you enable the appropriate Nessus connector and provide the directory name where the Nessus reports are written.

The connector then scans for new reports, parses them, and then creates alerts based upon the report contents. The different Nessus connectors support NBE, Nessus Message, Nessus Report, and Nessus XML Report reports formats.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.