Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > User Device Tracker (UDT) > User Device Tracker (UDT) Documentation > UDT Administrator Guide > Prepare a SolarWinds User Device Tracker installation > Enable FIPS

Enable FIPS

Table of contents
No headers
Created by Steven Bansil_ret, last modified by Steven Bansil_ret on Jan 13, 2017

Views: 192 Votes: 0 Revisions: 2

FIPS (Federal Information Processing Standard) defines security and interoperability standards for computers used by the U.S. Federal Government.

Monitored nodes and network discoveries must use FIPS-compliant authentication and privacy or encryption methods.

FIPS can also be enabled as part of Group Policy.

FIPS-COMPLIANT METHODS
Authentication SHA1
Privacy or encryption AES128, AES192, AES256

Solarwinds recommends that you install all FIPS-compliant SolarWinds software on FIPS-compliant servers and maintain all non-compliant SolarWinds software on non-compliant servers.

1. Configure the Orion server for FIPS compliance. See the Microsoft Support knowledge base for more information.

2. Start the SolarWinds FIPS 140-2 Manager (SolarWinds.FipsManager.exe).

By default, SolarWinds.FipsManager.exe is located in the Install_Volume:\ProgramFiles (x86)\SolarWinds\Orion folder.

3. Read the welcome text, and click Next.

The SolarWinds FIPS 140-2 Manager will confirm that the current configuration of your SolarWinds products is FIPS-compliant.

  • If an installed product is not FIPS-compliant, click Close, remove any non-compliant Orion Platform products from the FIPS-compliant server, and then run the FIPS 140-2 Manager again.
  • If FIPS 140-2 is disabled, select Enable FIPS 140-2, and then click Next.
  • If the FIPS Manager provides a list of objects or saved network discovery definitions that are not FIPS-enabled, complete the following steps.
  • To refresh the list of non-compliant objects after editing the credentials, restart the FIPS 140-2 Manager.

    • Click the non-compliant monitored node, and edit its Polling Method to be FIPS-compliant.

      a. Select SNMPv3 as the SNMP Version.

      b. Select FIPS-compliant Authentication and Privacy/Encryption methods, and provide the passwords.

      c. Click Submit.

    • Click the non-compliant network discovery, and edit SNMP credentials to be FIPS-compliant.

      a. Confirm that all SNMP credentials are SNMPv3. Delete or edit any credentials that are not FIPS-compliant SNMPv3.

      b. Confirm that all SNMP credentials use FIPS-compliant Authentication and Privacy/Encryption methods, and provide the passwords.

      c. Complete the Network Sonar Wizard using the updated credentials.

4. Click Restart now to restart all relevant SolarWinds services.

 
Last modified

Tags

Classifications

Public