Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Log & Event Manager (LEM) > Nessus connectors

Nessus connectors

Table of contents
Created by Craig O’ Neill, last modified by MindTouch on Jun 23, 2016

Views: 87 Votes: 0 Revisions: 3

Updated

Overview

This article provides information about LEM Nessus connectors

Environment

All LEM versions

Detail

There are a 3 different Nessus connectors available.

  • NessusdMsgLog.xml
  • NessusdReport.xml
  • nessusnbe.xml

 

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 creates alerts based upon the report contents.  The different Nessus connectors support Nessus reports formats from NBE, Nessus Report, Nessus XML Report.

 

 

Last modified
20:17, 22 Jun 2016

Tags

Classifications

Public