Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

How do I enable or disable FIPS mode on the SMS?

    • Updated:
    • 24 Aug 2017
    • Product/Version:
    • TippingPoint SMS All
    • TippingPoint Virtual SMS
    • Platform:
Summary
The Federal Information Processing Standard (FIPS) Publication 140-2, is a U.S. government computer security standard used to accredit cryptographic modules. The FIPS 140-2 publication coordinates requirements and standards for cryptography modules that include both hardware and software components. United States federal agencies and departments may require its software, including the SMS, to comply with the 140-2 standards.
Details
Public

The SMS supports three levels of FIPS operation:

Disabled: No FIPS compliance actions or restrictions are activated in the SMS server.

Crypto Only: The only SMS functionality affected by this mode is the connection between an SSH client and the SMS server. When a connection is made from an SSH client to the SMS server, the SSH client negotiates connections using only FIPS 140-2 approved algorithms.

Full-FIPS: SMS operates in a manner that is compliant with the FIPS 140-2 publication.

Transitioning an SMS server to operate in Full-FIPS mode implements changes to core elements of the SMS server.

The transition:

  • Deletes all existing SMS users.
  • Removes all SMS backup and device snapshots stored on the SMS server.
  • Deletes all custom responder action's
  • Regenerates SSH server and HTTPS web security keys.

The transition process reboots the SMS server and requires you to upload a new SMS key package to the SMS server. Placing the SMS server into one of the FIPS modes does not necessarily mean the SMS server is operating in compliance with FIPS 140-2. In order to operate in compliance with FIPS 140-2, you must place the SMS server into Full-FIPS mode and satisfy the following conditions:

  • The external database replication feature cannot be enabled.
  • The failed-lockout attempts counter must remain activated for all users.
  • The password security level setting for each SMS user should remain at or above level 1.

Note: An SMS server operating in Full-FIPS mode cannot be configured as part of an SMS HA cluster. It must operate as a standalone SMS server.

Because security must be tightened while the SMS server is operating in Full-FIPS mode, the following restrictions are in effect:

  • The SMS will perform software integrity self-test each time the SMS boots. If this test fails the SMS server will not be operational.
  • The SSH terminal will negotiate connections using only FIPS 140-2 approved algorithms.
  • You are not permitted to restore SMS backups that were created when SMS was not in Full-FIPS mode.
  • You cannot import or execute custom Responder Actions.
  • The SMS user password security is restricted to a minimum level of 1.
  • You cannot perform password recovery.
  • You are not permitted to use custom web security SSL certificates.
  • The SMS hardware appliance must have a BIOS password enabled and set.
  • It is recommended that the boot device section of the BIOS in the SMS hardware appliance be configured such that the only device configured as a boot device is the main hard drive.

Warning: In order to activate FIPS mode on the SMS, you will require a FIPS mode specific license file from TippingPoint. In order to receive this file contact TippingPoint support.


How To: Common Task

  1. Log in to the SMS from a client.
  2. On the SMS toolbar, navigate to the Admin->Server Properties tab.
  3. Select the Management tab.

How To: Place the SMS Server into FIPS Crypto-Only Mode

  1. In the FIPS mode area, click Edit.
  2. Select Crypto Only as the Requested State.
  3. Click OK.
  4. On the SMS server, the SSH daemon (service) restarts, which terminates all existing SSH client connections. Depending on the SSH software used to create the connection with the SMS server, the terminated connections may be automatically retried, or you may be required to manually initiate a new connection.

How To: Prepare for Placing the SMS Server into FIPS Full-FIPS Mode

  1. Verify that the version and patch level of your SMS server is fully FIPS by checking the Certification Status field in the FIPS-mode area, located in the Admin -> Management tab. Operating in Full-FIPS mode does not guarantee the SMS server is in compliance with FIPS 140-2. The SMS software itself, including the SMS server, the SMS client, and installed SMS patches, must all be certified as complying with the FIPS 140-2 publication. As well, certain configuration changes to the SMS server after the transition to Full-FIPS mode may rescind the server compliance with FIPS140-2.
  2. Document all existing SMS users. All existing SMS accounts will be removed as part of the transition to Full-FIPS mode. After the transition completes, you should recreate the user accounts, however, for security purposes you should not use the exact same usernames and passwords.
  3. SMS backup stored on the SMS server, as well as device snapshots, should be moved off the SMS server and onto a secure storage system. All backup files and device snapshots that are stored on the SMS server are deleted as part of the transition to Full-FIPS mode.
  4. Verify you have access to FIPS keys that are available for download from the TMC. You need to enter these FIPS keys as part of the transition to Full-FIPS mode.
  5. Verify the browsers and SSH clients you use to connect to the SMS server support the Transport Layer Security (TLS) 1.0 protocol, sometimes referred to as SSL 3.1. TLS 1.0 support is required to connect to an SMS server running in Full-FIPS mode.

How To: Place the SMS Server into FIPS Full-FIPS Mode

  1. In the FIPS Mode area, click Edit.
  2. Select Full-FIPS as the Requested State.
  3. Create a new SMS user account, which will be the only active account after the transition to Full-FIPS mode. This user account and password should NOT match the credentials of any SMS account that existed prior to enabling Full-FIPS mode.
  4. Click OK. The SMS server reboots and begins the process of becoming FIPS 140-2 compliant. The process includes deleting all existing SMS users, removing all SMS backups and device snapshots stored on the SMS server, deleting custom responder actions, and regenerating all SSH server and HTTPS web security keys and certificates.
  5. Enter the SMS FIPS key package by connecting to the SMS server via a web browser and uploading the key to the SMS server
  6. After the SMS server finishes its reboots, the transition to Full-FIPS mode is incomplete until the SMS FIPS key package is loaded. If you have not already downloaded the FIPS key package, download it from the TMC. Next, open a web browser and connect to the SMS server by entering its hostname or IP address in the address bar. Follow the SMS server prompts to upload the SMS FIPS key package.
  7. After the new key is entered, the SMS server again reboots. When it completes the reboot, the transition to Full-FIPS mode is complete and you can connect to the SMS server through the command-line interface, web browser, SSH client, and SMS client.

How To: Take the SMS Server out of FIPS Mode

Disabling FIPS mode invokes significant changes to the SMS server, including removing all existing user accounts, removing all backups and device snapshots that are currently stored on the SMS server, and restores the original SMS keys.

  1. In the FIPS mode area, click Edit.
  2. Select Disabled as the Requested State.
  3. When prompted create a new SuperUser account. Note that user accounts that existed prior to disabling FIPS mode will be deleted.

 

Reference: SMS User Guide

Premium
Internal
Rating:
Category:
Configure; Troubleshoot; Deploy
Solution Id:
TP000086238
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.