1 / 6

Role-Based Access Control for Publish/Subscribe Middleware Architectures

This paper discusses the implementation of a role-based access control system for publish/subscribe middleware architectures, ensuring security with minimal overhead to pub/sub efficiency. Topics include client connection policy, event type management, advertisement policy, subscription policy, and scalability. The use of hybrid schemes and broker trust is also explored.

pdan
Download Presentation

Role-Based Access Control for Publish/Subscribe Middleware Architectures

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Role-Based Access Control for Publish/Subscribe Middleware Architectures DEBS’03, San Diego, CA, USA, June 2003

  2. Access Control for Pub/Sub • Security with minimal overhead to pub/sub efficiency • Access control checks at • Client connection time Client Connection Policy • Event type management Type Management Policy • Advertisement time Advertisement Policy • Subscription time Subscription Policy • Only local (edge) brokers need to check policy • Take advantage of the pub/sub system • Introduce Restrictions for advertisements and subscriptions • Scalability • Role-based access control

  3. General Architecture • Edge brokers • Perform access control • No overhead at pub time • Subscribe to Policy Evolution Events Generic Restriction Predicate • Black box predicate • May be expensive Pub/Sub Restriction Predicate • Use filters available by pub/sub system • Get access control for “free” Hybrid schemes • Combination of both

  4. Broker Trust • May not want to trust all brokers • Trusted broker sub-graphs with certificate chains • Verify connectivity per sub-graph • Use pub/sub for revocation and policy update

  5. Conclusions • Scalable and efficient access control is needed for publish/subscribe systems • Take advantage of the pub/sub system for restrictions • Policy can be updated via the pub/sub infrastructure • Brokers may not be fully trusted • Future Work • Complete implementation • Tighter integration of roles and event types

  6. Thank You Any Questions?

More Related