Difference between revisions of "Working Sessions Browser Working Group"

Revision as of 21:01, 6 December 2010

Working Sessions Operational Rules - Please see here the general frame of rules.

WORKING SESSION IDENTIFICATION
Work Session Name	Browser Working Group
Short Work 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.
Related Projects (if any)	Sandboxing, Securing Plugins, Enduser Warnings, Blacklisting, OS Integration, JavaScript, New HTTP Headers
Email Contacts & Roles	Chair	Secretary	Mailing list Subscription Page

WORKING SESSION SPECIFICS
Objectives	Work on and discuss how to enhance enduser security in web applications, Work on and discuss browser-based countermeasures against XSS, CSRF, man-in-the-middle, man-in-the-browser and full remote access exploits.
Venue/Date&Time/Model	Venue OWASP Global Summit Portugal 2011	Date&Time	Discussion Model Open Space, demo-driven discussion, round-table discussions (i e not a PowerPoint race ;)

WORKING SESSION OPERATIONAL RESOURCES
Projector, whiteboards, markers, Internet connectivity, post-it notes, power

WORKING SESSION ADDITIONAL DETAILS
Related resources: OWASP Working Session - Browser Security Letters Browser vendors invited:Apple, Google, Microsoft, Mozilla, Opera

WORKING SESSION OUTCOMES
Statements, Initiatives or Decisions	Proposed by Working Group	Approved by OWASP Board
	Enhanced cooperation between browser vendors.	After the Board Meeting - fill in here.
	Identify points-of-contact for frameworks.	After the Board Meeting - fill in here.

Working Session Participants
	Name	Company	Notes & reason for participating, issues to be discussed/addressed
view edit	John Wilander @	Omegapoint	Session Leader
view edit	Michael Coates @	Mozilla

@@ Line 33: / Line 33: @@
 | align="center" style="width: 15%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | '''Objectives'''
 | align="left" colspan="6" style="width: 85%; background: none repeat scroll 0% 0% rgb(204, 204, 204);" | <font color="black"></font><font color="black"></font><font color="black">
-#Discuss how to enhance enduser security in web applications,
+#Work on and discuss how to enhance enduser security in web applications,
-#Discuss browser-based countermeasures against XSS, CSRF, man-in-the-middle, man-in-the-browser and full remote access exploits.</font>
+#Work on and discuss browser-based countermeasures against XSS, CSRF, man-in-the-middle, man-in-the-browser and full remote access exploits.</font>
 |-
@@ Line 42: / Line 42: @@
 '''Date&amp;Time'''
-| align="center" style="width: 25%; background: none repeat scroll 0% 0% rgb(204, 204, 204);" | '''Discussion Model'''<br>"Open Space, demo-driven discussion, round-table discussions (i e not a PowerPoint race)"
+| align="center" style="width: 25%; background: none repeat scroll 0% 0% rgb(204, 204, 204);" | '''Discussion Model'''<br>Open Space, demo-driven discussion, round-table discussions (i e not a PowerPoint race ;)
 |}