IBM WebSphere V5.0 Security - CGISecurity

►
►
Data integrity service describes more about unauthorized modification of the
data. Such a modification of data is possible in two different cases, through
hardware and transmission errors or because of deliberate attack.
Many hardware products and transmission protocols now have mechanism to
detect and correct hardware and transmission errors. So, for our messaging
security this may not be a threat or concern. But this is not the same with
deliberate attacks.
Access control mechanism can contribute to data integrity to an extend as
data cannot be modified if access is denied. So Data Integrity service can be
used to detect whether the contents of the message have been modified
while it was travelling over the network. This can also be helpful while
messages are stored in a local queue; the access control mechanism
provided by WebSphere MQ might be sufficient to prevent deliberate
modification of the contents of the message. However, for a greater level of
security, a data integrity service can be used to detect whether the contents of
a message have been deliberately modified between the time the message
was 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 the
message was sent by one particular individual and providing a proof of
delivery that can provide the sender with undeniable evidence that the
message was received by that particular individual.
For implementation, neither IBM WebSphere MQ nor Tivoli Policy Director for
MQSeries provides non-repudiation as part of its base function. However, this
can be achieved by writing your own exit programs within the WebSphere MQ
environment.
7.2.2 Messaging support for WebSphere Application Server
Messaging provider support for WebSphere Application Server V5.0 can be
achieved mainly in three ways.
1. Using Embedded JMS Provider
2. External JMS provider WebSphere MQ V5.3
3. External Generic JMS providers
Embedded JMS provider does not have the same level of security support as
compared to what we have in WebSphere MQ V5.3. The rest of this section will
explore the security features for these two JMS Provider options with
WebSphere Application Server.
Chapter 7. Securing Enterprise Integration components 161