Over the last 2 months, all of the sudden, I have “where’s the security?” phrase running through my head. Instead of that little old lady from the 80’s Wendy’s commercial saying “Where’s the beef?”, I have her in my head saying “Where’s the security?”.
Back in 2005, when I first starting selling Capitalware’s MQ Authenticate User Security Exit (MQAUSX) and MQ Standard Security Exit (MQSSX) MQ security products, I hit major head winds, because almost all companies were under the impression that MQ was secure by default. These companies assumed that MQ was a complete security solution. It has taken me, T.Rob Watt and many others 7 years to convince companies that they need to do more than simply install MQ. They need to implement SSL or an MQ security exit or both.
With the introduction of WebSphere MQ (MQ) v7.1, all of a sudden, everyone AGAIN thinks that all they need to do is install MQ v7.1 and magically their MQ environment is secure. I am sorry to break everyone’s bubble, but that is not the case.
I am not going to blame IBM, oh wait, yes I am. 🙂 Once again, IBM’s marketing machine is over zealously selling MQ as an “out of the box secure messaging product”. Think of Monty Python and the “nudge, nudge, wink, wink” routine (well, MQ is developed in Hursley, England).
There are some new security features in MQ v7.1 and T.Rob Watt has done a great write up of the new features at http://t-rob.net/2011/10/18/wmq-security-in-v7-1/
Before drawing any conclusions regarding the new security features and/or benefits in MQ v7.1, please take a moment to review the information that is out there.
MQAUSX offers application (or user) authentication of UserID and Password against a native OS system, LDAP server, Microsoft’s Active Directory, Quest Authentication Services (QAS), Centrify’s DirectControl or an encrypted MQAUSX FBA file. If interested, check out MQAUSX at https://www.capitalware.com/mqausx_overview.html
Regards,
Roger Lacroix
Capitalware Inc.
