Share This:

We all know communication between systems should be kept secure, but the process to implement security can be overwhelming.


Control-M 9.0.18 makes it easier than ever to secure communication between Control-M components, ensuring business critical workloads are running with the highest levels of security.


Join us for a live demo to see how to enable SSL encryption between Control-M clients and Control-M/Enterprise Manager Servers in under 20 minutes.


This webinar will cover:


•    New Control-M/Enterprise Manager security architecture

•    Control-M requirements for obtaining an SSL certificate

•    How to create a keystore and use it with a Control-M Web Server

•    Tips when implementing SSL


In this webinar Eric Epperson will explain and demonstrate the above.


This is the link on YouTube for the recorded session:


Connect With Control-M: Securing Control-M/Enterprise Manager 9.0.18 Client Connectivity - YouTube


Here is the Q&A for this webinar (Connect With Control-M: Securing Control-M/Enterprise Manager 9.0.18 Client Connectivity)




Q: What does SSL stand for?

A: SSL stands for Secure Sockets Layer and is the standard security technology used for encrypting communication between a server and client



Q: Why can I not use the certificates generated on CCM?

A: Because for the certificates generated on CCM, it’s not possible to edit the Common Name in order to make it match with EM’s host name.



Q: Isn't the openssl tool embedded with the Control-M installation?

A: Openssl is included with Control-M



Q: Does the manage_webserver utility back the old config up?

A: It does, you'll see the old file saved in the directory



Q: Where can detailed information on SSL configuration be found?

A: In the Control-M SSL Guide available at



Q: Can I just remove the unsecure connector and keep the secure one instead of removing both?

A: Creating the new secure connector is how the certificate information is associated with the Web Server. Removing the existing connector will insure that users are using the correct secure connection information.



Q: Why is FQDN required?

A: With an FQDN there shouldn't be any issues with DNS etc, you can use a short name also however it's recommended to add it as a subject alternate name. This ultimately depends on the environment.



Q: Could you please provide, which command which we need to use to start Web server

A: You can use start_web_server, we prefer to recycle Control-M Web Server from Configuration Manager when possible.



Q: Do we need to upgrade our environment to 9.0.18 from 9.0.00 to achieve this?

A: You can enable SSL in version 9.0 too but process is different so please review corresponding SSL Guide according to your version.



Q: Do we need to follow the migration/upgradation step to move from 9.0.00 to 9.0.18?

A: Yes, you can check Migration Guide to get familiar with the process. You can also open an AMIGO ticket to assist in reviewing your upgrade plan.