Your SlideShare is downloading. ×
Oma Drm2 Pki
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Oma Drm2 Pki

657
views

Published on

from vic

from vic


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
657
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. OMA DRM Overview 1 © NOKIA
  • 2. Digital Rights Management • Controlling the usage of digital objects in cyberspace 1. Associate usage rules with digital content 2. Enforce that the rules are followed YYu utnnt oo oo c bb t u ucan t ooy canp cpp.y • What we really want to do is to enable the paid content model pay, . ll a y, • Content owner gets paid when his content is consumed • An alternative for the subsidized advertising model – banners suck • Superdistribution is an important feature • Excellent content propagates from peer to peer like a virus – and the content owner gets paid for each copy 2 © NOKIA
  • 3. Threats and counter- measures The challenge is not to express rights, but to enforce them. 3 © NOKIA
  • 4. Threats Content • A Mickey Mouse screensaver ”You Replace the ”Youca n fooe canppay rights with more f r re e l lay vv r.” loose ones Replace er.” content with Rights illegal one • Enable preview (test drive) <rights> ” Yo u ”Y oo loucaanpla <agreement> nny cn p y lyoo ce lay nn . <asset> ce”” . <uid>mid:mickey_14@disney.com</uid> Extract content </asset> <permission> from the DRM system <play> Modify the <count> 99 </count> 1 existing rights </play> </permission> </agreement> </rights> T Terminal Hack the terminal • Plays the content once and then discards it forever implementation 4 © NOKIA
  • 5. Counter-measures • Protect the confidentiality of Content Extract content • Content encryption from the DRM • In practise hybrid encryption i.e. combination of symmetric system and asymmetric encryption • Protect the integrity and authenticity of Rights Modify the • Digitally signed Rights existing rights • Protect the integrity of the Content-Rights associationrights withthe Replace more • Include hash of the content inside the (signed) Rights loose ones Replace the • Careful implementation inside the terminal content with illegal one • Access control, integrity and confidentiality protection... • Only well behaving applications shall be able to access the bits Hack the terminal implementation 5 © NOKIA
  • 6. Example architecture Rights Rights Certifies RIs Rights Rights Issuer Issuer Issuer PKI Issuer PKI Registers Content Issues Content Rights Content ”You ”Y Server oo loucaanpla nny cn p y Server lyoo ce lay nn . ce”” . Distributes Content Certifies Terminal Terminal T1 Terminals PKI PKI P2P 6 © NOKIA Distribution
  • 7. Implications • Key management infrastructure – actually maybe even two • Terminal PKI – content encryption, device authentication • Rights Issuer PKI – signed rights • Both Terminal and Rights Issuer have a private key to hide • Hiding secrets is difficult – especially in the DRM threat model • The counter-measures are not cheap • Computationally expensive, increased footprint, deployment issues • Overkill for low value content • The market needs something that can be deployed now ! 7 © NOKIA
  • 8. OMA DRM Rel 1 Simplifications 1. Forget the key management infrastructures • No Terminal or Rights Issuer PKIs • No private keys / trust roots in terminals • No private keys / trust roots at Rights Issuers • Big trade-off between security and simplicity / ease of deployment 2. No DRM-specific architectural entities • No DRM-servers • Rights Issuer = Content / rights packaging tool • Easy to deploy • However, an evolution path towards a “real DRM” should exist • Functional requirements: • Object level “forward-lock” semantics • Preview feature 8 © NOKIA
  • 9. OMA DRM Rel 1 ”A simple DRM for low value mobile content” 9 © NOKIA
  • 10. How to deliver content and rights ? • OMA DRM Rel 1 defines three DRM methods Separate delivery Forward-lock Combined delivery & Superdistribution DRM Message DRM Message Content Content Rights Content Rights ”You can play ”You can play only once.” only once.” 2. WAP Push e.g. OMA e.g. OMA 1. e.g. OMA Download Download Download Terminal Terminal Terminal 10 © NOKIA
  • 11. OMA DRM Release 2 11 © NOKIA
  • 12. OMA DRM Rel 2 Requirements • Main requirement for OMA DRM Rel 2: • Need to support more valuable content => more security required • Music and video • The two big assumptions that made life easy in OMA DRM Rel 1 go away • OMA needs to bite the bullet • A key management infrastructure is needed to provide more security • If we do have terminal keys we need to personalize the rights objects on-the-fly • In OMA DRM Rel 1 the same rights object can be sent to any terminal • In OMA DRM Rel 2 the service must encrypt parts of the rights object with a terminal specific key • A real-time back-end solution is needed to do that 12 © NOKIA
  • 13. OMA DRM Release 2 Content Content Rights Rights Issuer Issuer Issuer Issuer Certifies Key Management Rights Issuers Rights Rights Rights Rights Issuer PKI Content Object Object Issuer PKI Device Device PKI PKI Certifies devices Content 13 © NOKIA
  • 14. OMA DRM Release 2 DOMAINS ADDED RECENTLY… Content Content Rights Rights Issuer Issuer Issuer Issuer Certifies Key Management Rights Issuers Rights Rights Rights Rights Issuer PKI Content Object Object Issuer PKI Device Device PKI PKI Certifies devices Content Content Key Device 1 Key Device 2 Key Rights Issuer Key 14 © NOKIA Rights Issuer’s Signature
  • 15. OMA DRM 2.0 Next generation open DRM technology specification Mobile domain Internet Enterprise (media) domain domain Home domain Fulfills security Enables consumers to Convergence of DRM requirements of buy content once and technology across future rich media e.g. consume with his/her Internet, media, mobile music services registered devices and home domains 15 © NOKIA
  • 16. Learnings and summary • Most people conduct payment transactions practically every day and carry a mobile phone, too • It is a strong value proposition for consumers and merchants if some part of these payments could be conducted with a mobile phone • Remote macro payments are increasing – existing credit card infrastructure offers a globally sustainable solution • While today’s technologies offer strong enablers, m-Commerce and mobile payments market is primarily business driven • Practical DRM is needed today • End-use experience is crucial: “easy to find, to use, to pay!” • Sustainable value chains are essential for the expansion of m- Commerce and mobile payments ecosystem • Co-creation of the customer experience is needed 16 © NOKIA
  • 17. 17 © NOKIA