This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Summit 2011 Working Sessions/Session001"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
−
<noinclude>{{:Category:Summit_2011_Browser_Security_Track}}</noinclude>
+
{{Template:<includeonly>{{{1}}}</includeonly><noinclude>Summit 2011 Working Sessions test tab</noinclude>
−
<includeonly>{{Template:{{{1}}}
 
 
|-
 
|-
  
Line 104: Line 103:
  
 
|-
 
|-
−
| summit_session_name = Browser Security Working Group
+
| summit_track_logo = [[Image:T._browser_security.jpg]]
 +
| summit_ws_logo = [[Image:WS._browser_security.jpg]]
 +
| summit_session_name = DOM Sandboxing
 
| summit_session_url = http://www.owasp.org/index.php/Summit_2011_Working_Sessions/Session001
 
| summit_session_url = http://www.owasp.org/index.php/Summit_2011_Working_Sessions/Session001
−
| mailing_list =
+
| mailing_list = https://groups.google.com/group/owasp-summit-browsersec
 
|-
 
|-
  
−
| short_working_session_description= One of the great challenges of application security is browser security. The browser is becoming our de facto runtime platform for applications and it comprises a whole ecosystem of plug-ins and web technologies. Therefore we will spend a full day working together with the leading browser vendors to penetrate current problems, new ideas, and how security fits in alongside other requirements from developers and end-users. Do not miss this chance to influence what's important in browser security in the coming years.
+
| short_working_session_description= Virtualization and Sandboxing for Secure Multi-Domain Web Apps
−
 
 
 
|-
 
|-
  
−
| related_project_name1 =  
+
| related_project_name1 = Browser Security Track - main page
−
| related_project_url_1 =  
+
| related_project_url_1 = http://www.owasp.org/index.php/Category:Summit_2011_Browser_Security_Track
  
−
| related_project_name2 =  
+
| related_project_name2 = Google Group for the Browser Security Track
−
| related_project_url_2 =  
+
| related_project_url_2 = https://groups.google.com/group/owasp-summit-browsersec
  
 
| related_project_name3 =  
 
| related_project_name3 =  
Line 130: Line 130:
 
|-
 
|-
  
−
| summit_session_objective_name1= Work on and discuss how to enhance enduser security in web applications,  
+
| summit_session_objective_name1= '''Attenuated versions of existing apis to sandboxed code'''. How should browsers introduce new apis into the sandbox or allow the sandbox to provide attenuated versions of existing apis to sandboxed code? For example, lets say the sandbox wants to provide an attenuated "alert" function to sandboxed code which does something slightly different than the real "alert". What kind of apis could the browser provide to safely allow such extensions/apis? Do these need to be standardized such that different sandbox vendors can interoperate.
  
−
| summit_session_objective_name2 = Work on and discuss browser-based countermeasures against XSS, CSRF, man-in-the-middle, man-in-the-browser and full remote access exploits
+
| summit_session_objective_name2 = '''Client side sandboxed apps maintaining state and authentication'''. For example if a user is created in a sandboxed app how is it determined what that user can do?
  
−
| summit_session_objective_name3 =  
+
| summit_session_objective_name3 = '''Create a standard for modifying a sandboxed environment'''
  
−
| summit_session_objective_name4 =  
+
| summit_session_objective_name4 = '''Deprecate and discourage standards''' which ambiently or undeniably pass credentials.
  
−
| summit_session_objective_name5 =
+
| summit_session_objective_name5 =   '''Create a standard for authentication within a sandboxed environment''' (maybe interfacing with existing auth without passing creds like 0Auth works)
  
 
|-
 
|-
Line 146: Line 146:
 
|-
 
|-
  
−
| discussion_model = participants and attendees
+
| discussion_model = The working form will most probably be short presentations to frame the topic and then round table discussions. Depending on number of attendees we'll break into groups.
  
 
|-
 
|-
Line 154: Line 154:
 
|-
 
|-
  
−
| working_session_additional_details = *'''Related resources:''' [[OWASP Working Session - Browser Security Letters]] <br> *'''Browser vendors invited: '''Apple, Google, Microsoft, Mozilla, Opera
+
| working_session_additional_details = <br>
 +
 
 +
===Co-chair Dr Jasvir Nagra===
 +
Jasvir Nagra is a researcher and software engineer at Google. He is the designer of [http://code.google.com/p/google-caja/ Caja] - a secure subset of HTML, CSS and JavaScript; co-author of [http://www.amazon.com/Surreptitious-Software-Obfuscation-Watermarking-Tamperproofing/dp/0321549252 Surreptitious Software] - a book on obfuscation, software watermarking and tamper-proofing, contributer to [http://shindig.apache.org/ Shindig] - the reference implementation of OpenSocial.
 +
 
 +
===Co-chair Gareth Heyes===
 +
Gareth "Gaz" Heyes calls himself Chief Conspiracy theorist and is affiliated with Microsoft. He is the designer and developer behind [http://www.owasp.org/index.php/OWASP_JavaScript_Sandboxes#tab=JSReg JSReg] – a Javascript sandbox which converts code using regular expressions; [http://www.owasp.org/index.php/OWASP_JavaScript_Sandboxes#tab=HTMLReg HTMLReg] & [http://www.owasp.org/index.php/OWASP_JavaScript_Sandboxes#tab=CSSReg CSSReg] – converters of malicious HTML/CSS into a safe form of HTML. He is also one of the co-authors of [http://www.amazon.com/Web-Application-Obfuscation-WAFs-Evasion-Filters-alert/dp/1597496049 Web Application Obfuscation: '-/WAFs..Evasion..Filters//alert(/Obfuscation/)-'] – a book on how an attacker would bypass different types of security controls including IDS/IPS.
  
 
|-
 
|-
  
−
|summit_session_deliverable_name1 = Enhanced cooperation between browser vendors.
+
|summit_session_deliverable_name1 =
 
|summit_session_deliverable_url_1 =  
 
|summit_session_deliverable_url_1 =  
  
−
|summit_session_deliverable_name2 = A new role for OWASP in this area.
+
|summit_session_deliverable_name2 =  
 
|summit_session_deliverable_url_2 =  
 
|summit_session_deliverable_url_2 =  
  
Line 175: Line 181:
 
|-
 
|-
  
−
| summit_session_leader_name1 = John Wilander
+
| summit_session_leader_name1 = Dr. Jasvir Nagra
−
| summit_session_leader_email1 = [email protected]
+
| summit_session_leader_email1 =  
  
−
| summit_session_leader_name2 =  
+
| summit_session_leader_name2 = Gareth Heyes
 
| summit_session_leader_email2 =  
 
| summit_session_leader_email2 =  
  
−
| summit_session_leader_name3 =  
+
| summit_session_leader_name3 = John Wilander
−
| summit_session_leader_email3 =  
+
| summit_session_leader_email3 = [email protected]
  
 
|-
 
|-
  
−
| operational_leader_name1 =
+
| operational_leader_name1 = John Wilander
−
| operational_leader_email1 =
+
| operational_leader_email1 = [email protected]
  
 
|-
 
|-

Revision as of 00:47, 25 January 2011

Global Summit 2011 Home Page
Global Summit 2011 Tracks

WS. browser security.jpg DOM Sandboxing
Please see/use the 'discussion' page for more details about this Working Session
Working Sessions Operational Rules - Please see here the general frame of rules.
WORKING SESSION IDENTIFICATION
Short Work Session Description Virtualization and Sandboxing for Secure Multi-Domain Web Apps
Related Projects (if any)


Email Contacts & Roles Chair
Dr. Jasvir Nagra
Gareth Heyes
John Wilander @ 		Operational Manager
John Wilander @ 		Mailing list
https://groups.google.com/group/owasp-summit-browsersec
WORKING SESSION SPECIFICS
Objectives
  1. Attenuated versions of existing apis to sandboxed code. How should browsers introduce new apis into the sandbox or allow the sandbox to provide attenuated versions of existing apis to sandboxed code? For example, lets say the sandbox wants to provide an attenuated "alert" function to sandboxed code which does something slightly different than the real "alert". What kind of apis could the browser provide to safely allow such extensions/apis? Do these need to be standardized such that different sandbox vendors can interoperate.
  2. Client side sandboxed apps maintaining state and authentication. For example if a user is created in a sandboxed app how is it determined what that user can do?
  3. Create a standard for modifying a sandboxed environment
  4. Deprecate and discourage standards which ambiently or undeniably pass credentials.
  5. Create a standard for authentication within a sandboxed environment (maybe interfacing with existing auth without passing creds like 0Auth works)

Venue/Date&Time/Model Venue/Room
OWASP Global Summit Portugal 2011 		Date & Time


 Discussion Model
The working form will most probably be short presentations to frame the topic and then round table discussions. Depending on number of attendees we'll break into groups.

WORKING SESSION OPERATIONAL RESOURCES
Projector, whiteboards, markers, Internet connectivity, power

WORKING SESSION ADDITIONAL DETAILS

Co-chair Dr Jasvir Nagra

Jasvir Nagra is a researcher and software engineer at Google. He is the designer of Caja - a secure subset of HTML, CSS and JavaScript; co-author of Surreptitious Software - a book on obfuscation, software watermarking and tamper-proofing, contributer to Shindig - the reference implementation of OpenSocial.

Co-chair Gareth Heyes

Gareth "Gaz" Heyes calls himself Chief Conspiracy theorist and is affiliated with Microsoft. He is the designer and developer behind JSReg – a Javascript sandbox which converts code using regular expressions; HTMLReg & CSSReg – converters of malicious HTML/CSS into a safe form of HTML. He is also one of the co-authors of Web Application Obfuscation: '-/WAFs..Evasion..Filters//alert(/Obfuscation/)-' – a book on how an attacker would bypass different types of security controls including IDS/IPS.

WORKING SESSION OUTCOMES / DELIVERABLES
Proposed by Working Group Approved by OWASP Board

After the Board Meeting - fill in here.

After the Board Meeting - fill in here.

After the Board Meeting - fill in here.

After the Board Meeting - fill in here.

After the Board Meeting - fill in here.

{{{summit_session_deliverable_name6}}}

After the Board Meeting - fill in here.

{{{summit_session_deliverable_name7}}}

After the Board Meeting - fill in here.

{{{summit_session_deliverable_name8}}}

After the Board Meeting - fill in here.

Working Session Participants

(Add you name by clicking "edit" on the tab on the upper left side of this page)

WORKING SESSION PARTICIPANTS
Name Company Notes & reason for participating, issues to be discussed/addressed
Email John Wilander if you are unable to edit the Wiki and would like to sign up! @


Michael Coates


Colin Watson





















































</includeonly>

Retrieved from "https://wiki.owasp.org/index.php?title=Summit_2011_Working_Sessions/Session001&oldid=101779"