Support for JWE Payload(entire/individual elements) Encryption in z/OS Connect as specified by Mastercard

1. Overview
   This Request for enhancement (RFE) proposes the implementation of JWE payload(entire/individual elements)  encryption support in IBM z/OS Connect, as specified by Mastercard under the following URL: Mastercard Payload Encryption Documentation.
    
2. Background
   Mastercard has outlined a method for securing sensitive data using payload(entire/individual elements)  encryption. This method ensures that sensitive information is encrypted before being transmitted over the network, providing an additional layer of security. Currently, z/OS Connect does not natively support this form of payload encryption, which is essential for compliance with Mastercard's security requirements.
    
3. Objectives
   1. Implement support for payload(entire/individual elements)  encryption in z/OS Connect.
   2. Ensure compliance with Mastercard's payload(entire/individual elements)  encryption specifications.
   3. Enhance the security of data transmitted through z/OS Connect.
4. Scope
   The scope of this RFC includes:
   1. Adding support for payload(entire/individual elements)  encryption and decryption in z/OS Connect.
   2. Providing configuration options to enable and manage payload encryption.
   3. Ensuring compatibility with existing z/OS Connect features and configurations.
5. Requirements
   1. Functional Requirements
      1. Encryption and Decryption
         • Implement methods to encrypt and decrypt payloads(entire/individual elements)  as specified by Mastercard.
         • Support for both symmetric and asymmetric encryption algorithms.
      2. Configuration:
         • Provide configuration options in the “server.xml” file to enable and manage payload encryption.
         • Allow users to specify encryption keys, algorithms, and other relevant parameters.
      3. Compatibility:
         • Ensure that the payload(entire/individual elements)  encryption feature is compatible with existing z/OS Connect configurations and features.
   2. Non-Functional Requirements
      1. Performance:
         • Ensure that the implementation of payload(entire/individual elements)  encryption does not significantly impact the performance of z/OS Connect.
      2. Security:
         • Ensure that the encryption keys and other sensitive information are securely managed and stored.

 Conclusion
Implementing support for payload(entire/individual elements)  encryption in z/OS Connect will enhance the security of data transmitted through the platform and ensure compliance with Mastercard's security requirements. This RFC outlines the necessary steps and considerations for implementing this feature.