Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.4 Administrator Guide > Security enhancements and exceptions in SAM > Enable FIPS in SAM

Enable FIPS in SAM

Table of contents
No headers

Updated: June 6, 2017

You can run your Orion Platform product in FIPS-compliant (Federal Information Processing Standard) mode to comply with computer security and interoperability standards used by non-military US government agencies and contractors.

For the full list of tested Orion products for international standards for computer security, see this site. For a certification letter of Orion FIPS compliance, contact us with your request.

  • If FIPS compliance is required, SolarWinds recommends that you enable FIPS as part of a fresh install instead of as part of an upgrade.
  • Before you enable FIPS ensure that the hardware is FIPS-compliant. See the Microsoft Support knowledge base for more information.
  • Not all Orion Platform products are FIPS-compliant. 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.
  2. Start the SolarWinds FIPS 140-2 Manager (SolarWinds.FipsManager.exe).

    By default, SolarWinds.FipsManager.exe is located in the C:\Program Files (x86)\SolarWinds\Orion folder.

  3. Read the welcome text, and click Next.
    The SolarWinds FIPS 140-2 Manager confirms 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 run the FIPS 140-2 Manager again.
    • If FIPS 140-2 is disabled, select Enable FIPS 140-2, and 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.
        1. Select SNMPv3 as the SNMP Version.
        2. Select FIPS-compliant Authentication and Privacy/Encryption methods, and provide the passwords.
        3. Click Submit.
      • Click the non-compliant network discovery, and edit SNMP credentials to be FIPS-compliant.
        1. Confirm that all SNMP credentials are SNMPv3. Delete or edit any credentials that are not FIPS-compliant SNMPv3.
        2. Confirm that all SNMP credentials use FIPS-compliant Authentication and Privacy/Encryption methods, and provide the passwords.
        3. Complete the Network Sonar Wizard using the updated credentials.
  4. Click Restart now to restart all relevant SolarWinds services.

While the software is FIPS-compliant, you must choose to use FIPS-compliant polling methods, such as SNMPv3, to monitor and discover nodes.

FIPS-Compliant Methods for SNMPv3

Authentication

SHA1
Privacy or encryptionAES128, AES192, AES256
 
Last modified
12:55, 3 Jul 2017

Tags

Classifications

Public