Network Management

Running firmware vulnerability reports through a proxy in NCM

The firmware vulnerability resource in Network Configuration Manager (NCM) cannot connect to the National Vulnerability Database, and the resource is empty.

First published date

10/11/2018 5:37 PM

Last published date

6/5/2019 9:02 PM

Overview

The firmware vulnerability resource cannot connect to the National Vulnerability Database, which results in the resource displaying as empty.

Product section

Network Configuration Manager

Cause

Firmware vulnerability reporting uses a separate configuration file than the SolarWinds Web Console, so proxy access must be enabled in both locations.

Resolution

  1. Use the following procedure to set up proxy access to the National Vulnerability Database.
  2. On your NCM server, navigate to C:\Program Files (x86)\SolarWinds\Orion\NCM.
  3. Back up the SolarWinds.NCM.VulnLib.dll.config file.
  4. Open the SolarWinds.NCM.VulnLib.dll.config file in a text editor.
  5. Add the following between <appsettings> and </appsettings>, and enter the appropriate entries for the values. 
    <add key="proxyAvailable" value="true" />
<add key="username" value="username" />
<add key="password" value="password " />
<add key="proxyAddress" value="IP of the proxy server" />
<add key="proxyPort" value="port of the proxy server" />
  6. Save the file.
  7. Restart the SolarWinds Orion Module Engine service.

Outcome 

Open the SolarWinds Orion Web Console. You can now access the National Vulnerability Database.

  1. Click Settings > NCM Settings > Firmware Vulnerability Settings.
  2. Click Run Now.

NCM tries to match your devices to entries in the database, and the Firmware Vulnerability resource is not empty.