Supporting NIST Strict Mode in IBM Control Center Monitor

IBM® Sterling Control Center Monitor supports NIST in strict mode with some limitations on some connections. When enabled in strict mode, the connections must support Transport Layer Security (TLS) 1.2.

Before you begin

If you are running IBM Sterling Control Center Monitor in strict mode with a connection to a DB2 database, you must upgrade to DB2 10.1 with Fix Pack 4 or a later version, or DB2 10.5 with Fix Pack 4 or a later version.

About this task

IBM Sterling Control Center Monitor can run in strict mode with the following limitations on some connections:
  • If you are using an Oracle database, the connection from IBM Sterling Control Center Monitor to the Oracle database must not be secured. Oracle 11g and 12c do not support TLS 1.2, which is enforced for secure connections when IBM Sterling Control Center Monitor runs in strict mode.
  • There are no limitations for connections from IBM Sterling Control Center Monitor to the DB2 database when it runs in strict mode. If you are using a DB2 database, the connection from IBM Sterling Control Center Monitor to the DB2 database can be secured or non-secured.

Procedure

  1. In the web console, go to your user ID and then click Menu button () > System Settings > Properties > engine.properties to access the IBM Sterling Control Center Monitor engine properties file.
  2. Add the following property to the file: com.ibm.jsse2.sp800-131=strict, then click Save.
  3. Restart all your IBM Sterling Control Center Monitor event processors.