Issue Verification BaseN 1.0j Issue 2.6: Third party subscriber can be asecurity concern

[Tom Maguire <tmaguire@us.ibm.com>]

Agreed Approach: Describe the additional security risks imposed by the
third party nature of the suscripion mechanism in the Security
Considerations section. Provide examples of how such risks may be averted.

   It should be noted that even though Subscriptions may be done by
   authorized principals, the Notifications may be delivered to
   NotificationConsumers whose identity may be different from the
   Subscriber. Message protection policies as outlined in the previous
   section can be used to ensure that sensitive Notifications are not
   delivered to malicious endpoints. For example, a key may need to be
   specified or generated during the process of Subscription, so that the
   Notifications can be encrypted using the key to ensure confidentiality
   of the messages. The mechanism by which the key is specified is governed
   by the Subscription policy.


While there is a brief description of 3rd party security considerations it
does not seem to in the spirit of the agreed approach.

Tom


Frey’s Law: “Every 5 years the number of architecture components double and
the ability to comprehend them halves”


Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away.   – Antoine de Saint-Exupery


T o m   M a g u i r e


STSM, On Demand Architecture


Poughkeepsie, NY  12601