Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Running firmware vulnerability reports through a proxy

Running firmware vulnerability reports through a proxy

 

Overview

 

The Firmware Vulnerability resource cannot connect to the National Vulnerability Database, and the resource is empty.

 

Environment

  • NCM 7.4
  • server that connects to the Internet through a proxy

 

Cause

Firmware vulnerability reporting uses a separate configuration file than the SolarWinds Webconsole, 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. Backup 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

You can now access the National Vulnerability Database.

  1. Open the SolarWinds Orion Web Console.
  2. Click Settings > NCM Settings > Firmware Vulnerability Settings.
  3. Click Run Now.

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

Last modified

Tags

Classifications

Public