1 / 12

Scenarios and Requirements for Business-Oriented Multicast Security

Scenarios and Requirements for Business-Oriented Multicast Security. Amit Kleinmann NDS Israel. IRTF - SMuG Second Meeting (Orlando) December 1998. Motivation. Solve the most common problems Handle issues that are most attractive to businesses. Anticipating Future Applications.

mahina
Download Presentation

Scenarios and Requirements for Business-Oriented Multicast Security

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. Scenarios and Requirements for Business-Oriented Multicast Security Amit Kleinmann NDS Israel IRTF - SMuG Second Meeting (Orlando) December 1998

  2. Motivation • Solve the most common problems • Handle issues that are most attractive to businesses

  3. Anticipating Future Applications • Multicast applications - practically don’t exist - chicken & egg problem • Why use multicast? • Save bandwidth • Save time • Save computational resources • When is multicast use justified? • Many users • High traffic volume

  4. Multicast Applications Application Many ParticipantsHigh traffic volume • Shared whiteboards 88 • Not (yet) well defined applications ? ? • Distributed interactive games/simulation • Distance learning • Communicating with unknown/dynamic group • Multi-party audiovisual conferencing 84 • Multimedia streaming/Pay Per View 44 • Data distribution 44 • Software distribution • Content (sports, weather, etc.) • Finance (stock tickers) • News/USENET • E-mail distribution • Push applications • Network synchronization 44 • DNS, Routing updates • Advertising and locating servers • Data link switching (DLSw)

  5. Scenario Requirements Two main scenarios: • File transfer • Data streaming Application Many High traffic File Data participantsvolumetransferstreaming • Multimedia streaming/Pay Per View 4 4 8 4 • Data distribution 4 4 4 4 • Software distribution • Content (sports, weather, etc.) • Finance (stock tickers) • News/USENET • E-mail distribution, push app. • Network synchronization 4 4 4 4 • DNS, Routing updates • Advertising and locating servers • Data link switching (DLSw)

  6. Business Models • One to Many vs. Many(few) to Many(few) • Free vs. Monitored • Free Multicast: • Channels (Public, Previews) • Content (Shareware, Program Guides, Ads) • Monitored Multicast: • Subscription (Streaming Video, Audio, Data) • Packages (Software, Games, Audio/Video clips) • Volume (bits/packets sent and/or consumed) • Time (Feeds, Conferences, Lectures)

  7. File Transfer • Static (closed) group • Reliable • Business models: • Subscription • Packages

  8. Data Streaming • Most common • Multimedia streaming • Non-reliable • Business model • Subscription • Packages • Volume • Time • Dynamic (open) group • Monitoring group members’ behavior • Key management • SMuG decision: should be separated from the actual securing of the traffic. • Synchronization between keys and content • Real time => Symmetric keys for traffic • Key period

  9. Multicast Conditional Access => Contents + Users • Content management • C.A. attributes for content • Multicast content authenticated and encrypted • Users should be aware of content descriptions and schedule. • User/Client management • Users are known/registered • User has an authenticator • User has C.A. attributes • Hierarchy

  10. Multicast Conditional Access: User/Client Authentication & Encryption • Each user authenticates to the Multicast server • Key exchange between user/server • Security entitlements • Content usage monitoring

  11. Trust in User/Client • Software protection • Server • Client • Subject to attacks (e.g., viruses) • Can be replicated • Hardware tokens • Features: • Tamper-resistant • Cannot be replicated easily • Advantages: • Distributed solution • Portability

  12. Benefits of Smart Cards • Physical security (VLSI, OS, Memory) • Portable (identity, rights) • Secure storage (keys, certificates, entitlements) • Secure processing (crypto functions) • Non Repudiation (transactions, signatures)

More Related