In IBM Cloud Pak for Integration (CP4I) v2021.2, secure communication between the Platform Navigator and other capability modules (such as API Connect, MQ, App Connect, and Event Streams) is essential to maintain data integrity and confidentiality.
The protocol used for secure communications between CP4I modules is Transport Layer Security (TLS).
Encryption: TLS encrypts data during transmission, preventing unauthorized access.
Authentication: TLS ensures that modules communicate securely by verifying identities using certificates.
Data Integrity: TLS protects data from tampering while in transit.
Industry Standard: TLS is the modern, secure successor to SSL and is widely adopted in enterprise security.
Why TLS is Used for Secure Communications in CP4I?By default, CP4I services use TLS 1.2 or higher, ensuring strong encryption for inter-service communication within the OpenShift cluster.
IBM Cloud Pak for Integration enforces TLS-based encryption for internal and external communications.
TLS provides a secure channel for communication between Platform Navigator and other CP4I components.
It is the recommended protocol over SSL due to security vulnerabilities in older SSL versions.
Why Answer D (TLS) is Correct?
A. SSL → Incorrect
SSL (Secure Sockets Layer) is an older protocol that has been deprecated due to security flaws.
CP4I uses TLS, which is the successor to SSL.
B. HTTP → Incorrect
HTTP is not secure for internal communication.
CP4I uses HTTPS (HTTP over TLS) for secure connections.
C. SSH → Incorrect
SSH (Secure Shell) is used for remote administration, not for service-to-service communication within CP4I.
CP4I services do not use SSH for inter-service communication.
Explanation of Incorrect Answers:
IBM Cloud Pak for Integration Security Guide
Transport Layer Security (TLS) in IBM Cloud Paks
IBM Platform Navigator Overview
TLS vs SSL Security Comparison
IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:
