Capitalware Inc. would like to announce the official release of MQ Message Encryption v1.0.0.
MQ Message Encryption (MQME) provides encryption for MQ message data while it resides in a queue and in the MQ logs (i.e. all data at rest). In cryptography, encryption is the process of transforming information into an unreadable form (encrypted data). Decryption is the reverse process. It makes the encrypted information readable again. Only those with the key (PassPhrase) can successfully decrypt the encrypted data. MQME uses Advanced Encryption Standard (AES) to encrypt the data. AES is a data encryption scheme, adopted by the US government, that uses three different key sizes (128-bit, 192-bit, and 256-bit).
One of the features that MQME offers is the ability to control who accesses protected queues. This control is obtained through the use of UserID grouping. The group files are implemented in a similar manner to the way they are implemented in Unix and Linux (i.e. /etc/group file). Normally, the ‘mqm’, ‘QMQM’ or ‘MUSR_MQADMIN’ MQ UserIDs or any UserID in the ‘mqm’ group get full access to all messages in all queues. For queues protected by MQME, those privileged UserIds do not get access to the messages in the protected queues unless they are explicitly added to the authorized list of users or groups.
Another feature of MQME is its ability to generate and validate the message via a digital signature. MQME uses the SHA-2 to create a cryptographic hash function (digital signature) for the message data. The digital signature provides verification that the message data has not been altered.
MQME is an MQ API Exit that operates with WebSphere MQ v5.3, v6.0 or v7.0 in Windows, Unix, IBM i (OS/400) and Linux platforms.
For more information about MQME, please go to:
https://www.capitalware.com/mqme_overview.html
Regards,
Roger Lacroix
Capitalware Inc.
