Home
Remote Control
BigFix Remote Control application helps to communicate between different components, clients, and endpoints within BigFix environment.
Remote Control Installation Guide
By using Remote Control you can remotely support and control thousands of PCs and servers, on an enterprise scale, from a central location or directly, in peer to peer mode.
Federal information processing standard (FIPS 140-2) compliance in Remote Control
The US Federal information processing standard 140-2 (FIPS 140-2) is a cryptographic function validation program that defines security standards for cryptographic modules that are used in IT software.
Enable FIPS compliance on the server
Enabling FIPS compliance on a server installation with a stand-alone WebSphere Application Server

Remote Control
BigFix Remote Control application helps to communicate between different components, clients, and endpoints within BigFix environment.
- Release notes
  A summary of changed or new features and enhancements included in BigFix Remote Control.
- Remote Control Installation Guide
  By using Remote Control you can remotely support and control thousands of PCs and servers, on an enterprise scale, from a central location or directly, in peer to peer mode.
  - Audience
  - Versions
  - Terms used in this guide
  - Overview of the Remote Controlsystem
  - Get started
    Now that you understand the terms and components available in Remote Control, you can identify which components you need to install:
  - Install the Remote Control components
    The Remote Control components can be installed in two ways. If you have access to the BigFix® console, use a deployment fixlet to install the components.
  - Utility for extracting the component installation files
    Remote Control provides a utility that you can use to extract the installation files that are required for each component.
  - Enable secure target registration
    To prevent unauthorized targets from registering with the Remote Control server, you can enable the secure registration feature and use tokens to authenticate the target.
  - Install the driver for smart card authentication
    The BigFix® Remote Control Target provides an installation option to install a virtual smart card reader driver. You can also install the driver by running a fixlet in the BigFix console.
  - Manage the component services
    After you install the Remote Control components, if you change their configuration, you can stop, start, or restart the component services.
  - Enabling email
  - Configure LDAP
  - Configure TLSv1.3
  - Federal information processing standard (FIPS 140-2) compliance in Remote Control
    The US Federal information processing standard 140-2 (FIPS 140-2) is a cryptographic function validation program that defines security standards for cryptographic modules that are used in IT software.
    - Enable FIPS compliance on the server
      - Enabling FIPS compliance on a server installation with a stand-alone WebSphere Application Server
      - Enabling FIPS compliance on an automated server installation
    - Enabling FIPS compliance on the controller
      The Remote Control controller is a Java™ application that requires a FIPS certified cryptographic provider when FIPS compliance is enabled. In FIPS-compliant mode the Remote Control controller supports the BC-FJA (Bouncy Castle FIPS Java API) with the IBM Semeru Runtime Open Edition JRE on Windows, Linux and MacOS.
    - Enable FIPS compliance on the target
    - Enabling FIPS compliance on the gateway
      You can enable FIPS compliance on the gateway component by editing the gateway configuration file that is created when you install gateway support.
    - Enabling FIPS compliance on the broker
      You can enable FIPS compliance on the broker component by editing the broker configuration file that is created when you install broker support.
  - NIST SP800-131A compliance in Remote Control
    Remote Control version 10.0.0 components can be configured for NIST SP800-131A compliance.
  - Verifying the server installation
  - Recover from installation errors
  - Uninstall the components
  - Upgrade from previous versions
  - Maintaining the target installation
  - Properties that can be set in the target configuration
    You can configure target properties either during or after installation. The operating system on the target system determines which properties can be configured. The target properties determine the actions that can be carried out during a peer-to-peer session. If you set a server URL and set the Managed property to Yes, the actions are determined by the policies that are set on the Remote Control server.
- Remote Control Administrators Guide
  This guide is for users who want to administer Remote Control.
- Remote Control Console User Guide
- BigFix Remote Control Controller Users Guide
- Remote Control Target Users Guide
- Remote Control On-demand Target Guide
  Use Remote Control to start remote control sessions over the internet with targets that do not have the target software installed.
- Remote Control V10 Readme

Enabling FIPS compliance on a server installation with a stand-alone WebSphere Application Server

About this task

The BigFix® Remote Control Server uses the middleware infrastructure that is provided by WebSphere® secure HTTP communications. Therefore, to enable FIPS for a manual BigFix® Remote Control Server installation requires that you configure WebSphere® for FIPS-compliant mode. You must also configure the BigFix® Remote Control Server through a setting in the common.properties configuration file.

To enable FIPS compliance for a manual installation, complete the following steps:

Procedure

Configure WebSphere

Note: Running in FIPS mode in IBM® WebSphere® with the IBM® JRE and the IBM® JSSE provider currently does not work when you use an MS SQL database. These options work with MS SQL when FIPS is not enabled in IBM® WebSphere.
Log on to the BigFix® Remote Control Server with a valid admin ID and password.
Click Admin > Edit properties files
In the common.properties file set FIPS.compliance to true.
Click Submit.
Click Admin > Reset Application.

Results

Note: The FIPS enablement changes in WebSphere affect all other applications that are running on the server. Therefore, browser settings for the users who access the other applications must be changed to support Transport Layer Security (TLS), if required by their browser version.

For example, to enable TLS in Internet Explorer complete the following steps:

Click Tools > Internet Options.
On the Advanced tab, select Use TLS 1.0.
Click Apply
Click OK.