Home
Security
After setting up your initial IBM® Sametime® environment, you may want to make additional changes to safeguard information at your site, including limiting user access to certain features, using encryption, and modifying default security settings.
Setting up compliance for FIPS 140-2
IBM® Sametime® supports the U.S. government-defined security requirements for cryptographic modules known as FIPS 140-2 (Federal Information Processing Standard 140-2). If your Sametime deployment must maintain FIPS 140-compliance for all data exchanged between clients and Sametime Community Servers, you must install the FIPS Server on the Sametime Proxy Server to accept data on behalf of Sametime Community Servers.
Enabling TLS on the Sametime® Community Mux
When FIPS 140-2 is enabled in the IBM® Sametime® Community Mux, client connections to the Mux are compliant with FIPS 140-2, without going through the FIPS Proxy Server.

Enabling TLS on the Sametime Community Mux

When FIPS 140-2 is enabled in the IBM® Sametime® Community Mux, client connections to the Mux are compliant with FIPS 140-2, without going through the FIPS Proxy Server.

Procedure

Enable TLS in the Sametime Community Mux, by following the steps in the task Managing client connections, and set the Client encryption mode setting to Strict TLS.
Enable FIPS 140-2 compliance in the Sametime Mux, by setting FIPS 140-2 compliance, according to the procedure Setting up TLS Configuration.