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.
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.