13.07.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

►►Data integrity service describes more about unauthorized modification of thedata. Such a modification of data is possible in two different cases, throughhardware and transmission errors or because of deliberate attack.Many hardware products and transmission protocols now have mechanism todetect and correct hardware and transmission errors. So, for our messagingsecurity this may not be a threat or concern. But this is not the same withdeliberate attacks.Access control mechanism can contribute to data integrity to an extend asdata cannot be modified if access is denied. So Data Integrity service can beused to detect whether the contents of the message have been modifiedwhile it was travelling over the network. This can also be helpful whilemessages are stored in a local queue; the access control mechanismprovided by <strong>WebSphere</strong> MQ might be sufficient to prevent deliberatemodification of the contents of the message. However, for a greater level ofsecurity, a data integrity service can be used to detect whether the contents ofa message have been deliberately modified between the time the messagewas put on the queue and the time it was retrieved from the queue.Non-repudiation is more about providing with a proof of origin that themessage was sent by one particular individual and providing a proof ofdelivery that can provide the sender with undeniable evidence that themessage was received by that particular individual.For implementation, neither <strong>IBM</strong> <strong>WebSphere</strong> MQ nor Tivoli Policy Director forMQSeries provides non-repudiation as part of its base function. However, thiscan be achieved by writing your own exit programs within the <strong>WebSphere</strong> MQenvironment.7.2.2 Messaging support for <strong>WebSphere</strong> Application ServerMessaging provider support for <strong>WebSphere</strong> Application Server <strong>V5.0</strong> can beachieved mainly in three ways.1. Using Embedded JMS Provider2. External JMS provider <strong>WebSphere</strong> MQ V5.33. External Generic JMS providersEmbedded JMS provider does not have the same level of security support ascompared to what we have in <strong>WebSphere</strong> MQ V5.3. The rest of this section willexplore the security features for these two JMS Provider options with<strong>WebSphere</strong> Application Server.Chapter 7. Securing Enterprise Integration components 161

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!