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 "Working Sessions Browser Working Group"

From OWASP
Jump to: navigation, search
m
Line 17: Line 17:
 
|-
 
|-
 
| align="center" style="width: 15%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | '''Short Work Session Description'''  
 
| align="center" style="width: 15%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | '''Short Work Session Description'''  
−
| align="left" colspan="6" style="width: 85%; background: none repeat scroll 0% 0% rgb(204, 204, 204);" | 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 plugins 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 endusers.Do not miss this chance to influence what's important in browser security in the coming years. <br>
+
| align="left" colspan="6" style="width: 85%; background: none repeat scroll 0% 0% rgb(204, 204, 204);" | 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. <br>
 
|-
 
|-
 
| align="center" style="width: 15%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | '''Related Projects (if any)'''  
 
| align="center" style="width: 15%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | '''Related Projects (if any)'''  
Line 88: Line 88:
 
|-
 
|-
 
| align="center" style="width: 7%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | <br>
 
| align="center" style="width: 7%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | <br>
−
| align="center" style="width: 46%; background: none repeat scroll 0% 0% rgb(194, 194, 194);" | Actionable advice for each individual frameworks .  
+
| align="center" style="width: 46%; background: none repeat scroll 0% 0% rgb(194, 194, 194);" | Actionable advice for each individual frameworks.  
 
| align="center" style="width: 47%; background: none repeat scroll 0% 0% rgb(194, 194, 194);" | After the Board Meeting - fill in here.
 
| align="center" style="width: 47%; background: none repeat scroll 0% 0% rgb(194, 194, 194);" | After the Board Meeting - fill in here.
 
|-
 
|-

Revision as of 20:27, 22 November 2010

FocusonBrowserSecurityOWASPlogo.png

Return to the Global Summit 2011 Home Page
Return to the Global Summit 2011 Schedule


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)
Email Contacts & Roles Chair
 Secretary
 Mailing list
Subscription Page
WORKING SESSION SPECIFICS
Objectives
  1. Discuss gaps and patterns in gaps in security coverage across frameworks,
  2. Discuss possible solutions for security areas.
Venue/Date&Time/Model Venue
OWASP Global Summit Portugal 2011

Date&Time

February 9, 2011
Time 9:00AM

Discussion Model
"Participants + Attendees"

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

WORKING SESSION ADDITIONAL DETAILS
  • Related resources: OWASP Working Session - Browser Security Letters
  • Frameworks to invite: .NET, J2EE, Spring, Struts, ASP.NET MVC, RoR, PHP, etc.
    • 10 Oct: "Open Letter to Frameworks (version for open mailing lists)" sent to
      • Ruby-on-Rails Core mailing list
      • Springnet Developer mailing list
      • Struts Dev mailing list
WORKING SESSION OUTCOMES
Statements, Initiatives or Decisions Proposed by Working Group Approved by OWASP Board

Actionable advice for each individual frameworks. After the Board Meeting - fill in here.

Identify points-of-contact for frameworks. After the Board Meeting - fill in here.

Working Session Participants

(Add you name by editing this table. On your the right, just above the this frame, you have the option to edit)


WORKING SESSION PARTICIPANTS

Name Company Notes & reason for participating, issues to be discussed/addressed




























































If needed add here more lines.

Retrieved from "https://wiki.owasp.org/index.php?title=Working_Sessions_Browser_Working_Group&oldid=93596"