search cancel

Can you import a third party SSL certificate and use it to provide SSL to web services on different CICS regions?

book

Article ID: 53295

calendar_today

Updated On:

Products

Cleanup Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ECOMETER SERVER COMPONENT FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware Top Secret Top Secret - LDAP Top Secret - VSE

Issue/Introduction

Question:

Can a third party SSL certificate (Ex. Verisign...) be imported and the same certificate used to provide SSL to the Web Services on different CICS regions?

If so, does this cause any security concerns?

Answer:

Yes, a third party SSL certificate can be imported and the same certificate used to provide SSL to the Web Services on different CICS regions. The owner of the certificate must be CERTSITE to be able to share the certificate.

  1. The security concerns are:

    The ACIDs involved will need the appropriate permission/access to the IBMFAC(IRR.DIGTCERT.function), where 'function' could be LISTRING, LIST or GENCERT.

  2. If someone steals/copies that certificate, they will be able to get to those systems where they are shared.

Additional Information:

Please see the CA Top Secret Cookbook for more information on digital certificates. 

Environment

Release: TOPSEC00200-15-Top Secret-Security
Component: