Enabling FIPS compliance on the controller

The Controller installation package includes a FIPS certified JRE which is used to run the application. When the Controller start is triggered from the Remote Control server, the FIPS settings which are set on the server are automatically applied to the application. So in this case once FIPS compliance is enabled no other actions are needed.

However, if the Controller is started manually to establish a peer-to-peer session with a Target, you need to edit the local Controller configuration.

About this task

The local Controller configuration must be changed to enable the FIPS compliance for peer-to-peer sessions.
Note: Only required if you are running the controller locally for establishing peer-to-peer sessions (a Remote Control server is not being used).
To set FIPS compliance on the Controller when operating in peer to peer mode update the local configuration as follows:
Edit the trc_controller.cfg file on the system that the controller is installed on.
Windows® systems
[controller install dir]\trc_controller.cfg

Where [controller install dir] is the installation directory that is chosen when you install the controller.

Linux® / UNIX® systems
/opt/bigfix/trc/controller/trc_controller.cfg

Set the fips.compliance property to True and save the file.

Results

Check to see whether the controller is configured for FIPS by completing the following step during a remote control session.

  • Click Controller tools > Show session information in the controller window.