Difference between revisions of "ESAPI Summit"

From OWASP
Jump to: navigation, search
 
(9 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Summit 2011 ==
+
== Summit 2011 ==
  
=== Summit Overview ===
+
=== Summit Overview ===
  
The ESAPI Summit will be held on  
+
The ESAPI Summit will be held on September 21, 2011 at [http://www.appsecusa.org OWASP AppSec USA 2011] in Minneapolis, Minnesota.
  
=== Agenda ===
+
=== Agenda ===
  
* 09:00 - 09:30 Mission Briefing
+
{| cellspacing="2" cellpadding="2" style="border: 2px solid black;"
** Review Project Definition and Mission Statement (update if necc.)
+
|- style="background-color: navy;"
* 09:30 - 10:30 Brain Dump
+
! style="color: white;" | Start
** Get everyones "big-picture" ideas up on the board
+
! style="color: white;" | End
** Brief statement about each, this should be a fast-paced Mind-Mapping Exercise aimed to get as many ideas as we can on the board as quickly as possible
+
! style="color: white;" | Topic
* 10:30 - 10:45 Break time
+
! style="color: white;" | Description
** Good job, get some coffee and some air and get prepared for the real work.
+
! style="color: white;" | Deliverables
* 10:45 - 12:00 Bug Hunt
+
|- style="background-color: lightgray;"
** Review the list of existing ESAPI Bugs, assign a champion to them, and prioritize per champion
+
| 0900
* 12:00 - 13:00 Lunch - Open Conversation
+
| 0930
** Lunch to be provided by OWASP/ESAPI
+
| Mission Briefing
* 13:00 - 15:00 Where do we go now?
+
| Brief summary of where we've been, administrative changes, and outlining the goals and purpose of the Summit
** Now that the bugs are fresh in our heads, let's revisit our master wish-list from earlier and prioritize future enhancements, lay them out into a version roadmap (not a calendar roadmap). Some of these enhancements will likely jump out as high-priority and others as nice-to-haves. It should also be remembered, that a version roadmap is a organic document, it will constantly change and evolve to meet the demands of our users. This is just a first step in getting such a roadmap in place.
+
| n/a
* 15:00 - 15:15 Break time
+
|-
** Get some air, there is sure to be some great debate to reflect on
+
| 0930
* 15:15 - 16:00 Formally define the following policies
+
| 1030
** Becoming a Committer
+
| The ESAPI Specification 1.0
** Submitting Contributed Components
+
| Review the high level API and determine what methods should remain as '''core''' API's and what should be moved upstream to higher level API's (ie ESAPI-Web, ESAPI-Mobile, etc)
** Reporting Security Vulnerabilities
+
|
* 16:00 - 18:00 Aligning the ESAPI Projects
+
*[[ESAPI Specification Overview]]
** How do we bring all of the implementations into alignment as far as the API is concerned
+
** How do we ensure that all implements adhere to the contract of the API
+
** What level of adherement to the specification do we enforce to "sign off" on various implementations
+
  
=== Deliverables ===
+
|- style="background-color: lightblue;"
 +
| 1030
 +
| 1045
 +
| colspan="3" | Coffee Break
 +
|- style="background-color: lightgray;"
 +
| 1045
 +
| 1200
 +
| The ESAPI Roadmap
 +
| Take a look at the existing Roadmap, create the roadmap for the next several release cycles.
 +
|
 +
*[[ESAPI Roadmap]]
 +
|- style="background-color: lightblue;"
 +
| 1200
 +
| 1300
 +
| colspan="3" | Lunch Break and Open Conversation (Provided by OWASP/ESAPI)
 +
|- style="background-color: lightgray;"
 +
| 1300
 +
| 1400
 +
| ESAPI Policies
 +
| Formally define how to processes for contributers, community, sponsors, submitting issues, reporting security vulnerabilities
 +
|
 +
*[[ESAPI How To Contribute]]
 +
*[[ESAPI Community Contributions]]
 +
*[[ESAPI Sponsoring]]
 +
*[[ESAPI Submitting Issues]]
 +
*[[ESAPI Vulnerability Reporting]]
 +
|- style="background-color: lightgray;"
 +
| 1400
 +
| 1500
 +
| ESTAPI Framework
 +
| How do we test and ensure that implementations meet the specifications defined in the API in a cross-platform and demonstratible manner?
 +
|
 +
*[[ESAPI Testing Framework]]
 +
|- style="background-color: lightblue;"
 +
| 1500
 +
| 1515
 +
| colspan="3" | Coffee Break
 +
|-
 +
| 1515
 +
| 1615
 +
| Documentation
 +
| Identify a Roadmap for ESAPI Documentation. Elect someone to champion this cause and find resources to address the documentation needs. Determine funding levels and budget needed for documentation to happen.
 +
|
 +
*[[ESAPI Documentation Roadmap]]
 +
*[[ESAPI Documentation Sub-Project]]
 +
*[[ESAPI Documentation Sub-Project Budget]]
  
* [[ESAPI Roadmap]]
+
|- style="background-color: lightgray;"
* [[How to become a committer]]
+
| 1615
* [[How to submit contributions]]
+
| 1630
* [[How to report security vulnerabilities]]
+
| Mission De-Briefing
* [[ESAPI Cross Platform Specification]]
+
| We have accomplished a lot in the last 3 years as a team. This will be a quick wrap-up by Chris on the 2nd ESAPI Summit Day.
 +
| n/a
 +
|- style="background-color: lightblue;"
 +
| 2100
 +
| ????
 +
| ESAPI 2.0GA Release Celebration
 +
| Celebrate the release of ESAPI 2.0GA (and beyond) with beers with the ESAPI Team (Sponsors/Location: TBA)
 +
| n/a
 +
|}
  
 +
<noinclude>
 
=== Attending the ESAPI Summit ===
 
=== Attending the ESAPI Summit ===
  
If you are planning to attend this summit, please list your name below so that we can ensure that we have adequate space and materials for everyone.
+
If you are planning to attend this summit, please [https://docs.google.com/a/owasp.org/spreadsheet/viewform?formkey=dHBEQ1YtVlcyWHp1RTZ6cHJHdENDc1E6MQ add your name here] so that we can ensure that we have adequate space and materials for everyone.
 +
 
 +
* [[User:Chris Schmidt|Chris Schmidt]] - Meeting Leader
 +
* [[User:jmanico|Jim Manico]] - ESAPI Project Manager
 +
* [[User:John Steven|jOHN Steven]] - Cigital Principal, ESAPI Malcontent
 +
* [[User:Kevin W. Wall|Kevin Wall]] - CenturyLink; ESAPI crypto guy
  
[[User:Chris Schmidt|Chris Schmidt]] - Meeting Leader
+
<noinclude>
  
 
== Summit 2008 ==
 
== Summit 2008 ==
Line 112: Line 168:
 
__NOTOC__
 
__NOTOC__
 
[[Category:OWASP Enterprise Security API]]
 
[[Category:OWASP Enterprise Security API]]
 +
</noinclude>

Latest revision as of 00:45, 24 August 2011

Summit 2011

Summit Overview

The ESAPI Summit will be held on September 21, 2011 at OWASP AppSec USA 2011 in Minneapolis, Minnesota.

Agenda

Start End Topic Description Deliverables
0900 0930 Mission Briefing Brief summary of where we've been, administrative changes, and outlining the goals and purpose of the Summit n/a
0930 1030 The ESAPI Specification 1.0 Review the high level API and determine what methods should remain as core API's and what should be moved upstream to higher level API's (ie ESAPI-Web, ESAPI-Mobile, etc)
1030 1045 Coffee Break
1045 1200 The ESAPI Roadmap Take a look at the existing Roadmap, create the roadmap for the next several release cycles.
1200 1300 Lunch Break and Open Conversation (Provided by OWASP/ESAPI)
1300 1400 ESAPI Policies Formally define how to processes for contributers, community, sponsors, submitting issues, reporting security vulnerabilities
1400 1500 ESTAPI Framework How do we test and ensure that implementations meet the specifications defined in the API in a cross-platform and demonstratible manner?
1500 1515 Coffee Break
1515 1615 Documentation Identify a Roadmap for ESAPI Documentation. Elect someone to champion this cause and find resources to address the documentation needs. Determine funding levels and budget needed for documentation to happen.
1615 1630 Mission De-Briefing We have accomplished a lot in the last 3 years as a team. This will be a quick wrap-up by Chris on the 2nd ESAPI Summit Day. n/a
2100  ???? ESAPI 2.0GA Release Celebration Celebrate the release of ESAPI 2.0GA (and beyond) with beers with the ESAPI Team (Sponsors/Location: TBA) n/a


Attending the ESAPI Summit

If you are planning to attend this summit, please add your name here so that we can ensure that we have adequate space and materials for everyone.


Summit 2008

Summit Overview

The first OWASP ESAPI Summit was held December 9-11, 2008. It was hosted by Aspect Security in their Columbia, MD office.

The following were the attendees of the Summit:

The following pages contain our thoughts/results from the summit.

Summary: TODO

Links

Design

Features