21.7 Reverting Sentinel to Non-FIPS Mode

This section provides information about how to revert Sentinel and its components to non-FIPS mode.

21.7.1 Reverting Sentinel Server to Non-FIPS mode

You can revert a Sentinel server running in FIPS 140-2 mode to non-FIPS mode only if you have taken a backup of your Sentinel server before converting it to run in FIPS 140-2 mode.

NOTE:When you revert a Sentinel server to non-FIPS mode, you will lose the events, incident data, and configuration changes made to your Sentinel server after converting to run FIPS 140-2 mode. The sentinel system will be restored back to the last restoration point of non-FIPS mode. You should take a backup of the current system before reverting to non-FIPS mode for future use.

To revert your Sentinel server to non-FIPS mode:

  1. Log in to the Sentinel server as the root user.

  2. Switch to the novell user.

  3. Browse to the Sentinel bin directory. The default location is /opt/novell/sentinel/bin.

  4. Run the following command to revert your Sentinel server to non-FIPS mode, and follow the on-screen instructions:

    ./backup_util.sh -f <backup_file_name.tar.gz> -m 'restore'

    For example, if non-fips2013012419111359034887.tar.gz is the backup file, run the following command:

    ./backup_util.sh -f non-fips2013012419111359034887.tar.gz -m 'restore'

  5. Restart the Sentinel server.

21.7.2 Reverting Remote Collector Managers or Remote Correlation Engines to Non-FIPS mode

You can revert remote Collector Managers or remote Correlation Engines to non-FIPS mode.

To revert a remote Collector Managers or a remote Correlation Engine to non-FIPS mode:

  1. Login to the remote Collector Manager or remote Correlation Engine system.

  2. Switch to novell user (su novell).

  3. Browse to the bin directory. The default location is /opt/novell/sentinel/bin.

  4. Run the revert_to_nonfips.sh script and follow the on-screen instructions.

  5. Restart the remote Collector Manager or remote Correlation Engine.