1 / 11

A Framework for Fine Grained Origins

Vaibhav Rastogi and Yi Yang. A Framework for Fine Grained Origins. Motivation. Web 2.0 – rich applications A website hosts content it may not be responsible for Third party gadgets Third party libraries 2 websites want to enable sharing of a script

lucas
Download Presentation

A Framework for Fine Grained Origins

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. VaibhavRastogi and Yi Yang A Framework for Fine Grained Origins

  2. Motivation • Web 2.0 – rich applications • A website hosts content it may not be responsible for • Third party gadgets • Third party libraries • 2 websites want to enable sharing of a script • Allow a script hosted on one site access other scripts

  3. Objective • SOP is outdated • Netscape introduced this policy when most content on the Internet was static • Differences amongst different resources leads to vulnerabilities • Design a new framework to capture finer grained origins and sharing

  4. Objective • The mechanism for sharing should • Same for all resources • Extensible to new resources • Current consideration of resources • DOM objects • Cookies • Network access – AJAX • JavaScript functionality • Others such as display, clipboard, history

  5. Approach • Origins depicted by • <proto, domain, port, originID> • Allow origins to be specified at arbitrary levels of granularity • In HTML, originID may be included as attributes <div originID=“…”>…</div> • With each origin is a policy file associated with a server

  6. Approach • If no origins are specified the default is the prevalent Same Origin Policy • Current websites do not break • An origin is inherited from the parent if no origin is specified

  7. Resource types • Server side resources • HTML, CSS, JavaScript • Server supplies the originIDs and policies • Generated resources • DOM and JS objects • AJAX • Origins normally inherited from server side resources • More finer grained policies may still be specified

  8. Advantages • Finer grained origins • No XSS • The default policies of not associating any origin with a script makes XSS impossible

  9. Securing Origins • Tamper proof • Non forgeable • Attacker should not be able to change or add origins • Non repudiation • Host cannot repudiate setting up of origins • May not be required

  10. Securing Origins: Current Idea • Public Key Infrastructure • Similar to SSL • MAC(resource|originID) specifies the actual origin • Heavy weight • Requires every website to use SSL type PKI

  11. Questions • What makes a good string representation of a resource? • Do policy files themselves need to be secured?

More Related