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 "ESAPI Summit"
From OWASP
Sarah Baso (talk | contribs) m |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | == Summit 2011 == | + | == Summit 2011 == |
| − | === Summit Overview === | + | === Summit Overview === |
| − | The ESAPI Summit will be held on September 21, 2011 at [http://www.appsecusa.org OWASP AppSec USA 2011] in Minneapolis, Minnesota. | + | The ESAPI Summit will be held on September 21, 2011 at [http://www.appsecusa.org OWASP AppSec USA 2011] in Minneapolis, Minnesota. |
| − | === Agenda === | + | === Agenda === |
| − | {| | + | {| cellspacing="2" cellpadding="2" style="border: 2px solid black;" |
|- style="background-color: navy;" | |- style="background-color: navy;" | ||
| − | ! style="color: white;" | Start | + | ! style="color: white;" | Start |
| − | ! style="color: white;" | End | + | ! style="color: white;" | End |
| − | ! style="color: white;" | Topic | + | ! style="color: white;" | Topic |
| − | ! style="color: white;" | Description | + | ! style="color: white;" | Description |
! style="color: white;" | Deliverables | ! style="color: white;" | Deliverables | ||
| − | |-style="background-color: lightgray;" | + | |- style="background-color: lightgray;" |
| − | | 0900 | + | | 0900 |
| − | | 0930 | + | | 0930 |
| − | | Mission Briefing | + | | Mission Briefing |
| − | | Brief summary of where we've been, administrative changes, and outlining the goals and purpose of the Summit | + | | Brief summary of where we've been, administrative changes, and outlining the goals and purpose of the Summit |
| n/a | | n/a | ||
| − | |- | + | |- |
| − | | 0930 | + | | 0930 |
| − | | 1030 | + | | 1030 |
| − | | The ESAPI Specification 1.0 | + | | 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) | + | | 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) |
| | | | ||
| − | * [[ESAPI Specification Overview]] | + | *[[ESAPI Specification Overview]] |
| + | |||
|- style="background-color: lightblue;" | |- style="background-color: lightblue;" | ||
| − | | 1030 | + | | 1030 |
| − | | 1045 | + | | 1045 |
| colspan="3" | Coffee Break | | colspan="3" | Coffee Break | ||
|- style="background-color: lightgray;" | |- style="background-color: lightgray;" | ||
| − | | 1045 | + | | 1045 |
| − | | 1200 | + | | 1200 |
| − | | The ESAPI | + | | 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;" | |- style="background-color: lightblue;" | ||
| − | | 1200 | + | | 1200 |
| − | | 1300 | + | | 1300 |
| colspan="3" | Lunch Break and Open Conversation (Provided by OWASP/ESAPI) | | colspan="3" | Lunch Break and Open Conversation (Provided by OWASP/ESAPI) | ||
|- style="background-color: lightgray;" | |- style="background-color: lightgray;" | ||
| − | | 1300 | + | | 1300 |
| − | | 1400 | + | | 1400 |
| − | + | | ESAPI Policies | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | | ESAPI Policies | ||
| Formally define how to processes for contributers, community, sponsors, submitting issues, reporting security vulnerabilities | | Formally define how to processes for contributers, community, sponsors, submitting issues, reporting security vulnerabilities | ||
| | | | ||
| − | * [[ESAPI How To Contribute]] | + | *[[ESAPI How To Contribute]] |
| − | * [[ESAPI Community Contributions]] | + | *[[ESAPI Community Contributions]] |
| − | * [[ESAPI Sponsoring]] | + | *[[ESAPI Sponsoring]] |
| − | * [[ESAPI Submitting Issues]] | + | *[[ESAPI Submitting Issues]] |
| − | * [[ESAPI Vulnerability Reporting]] | + | *[[ESAPI Vulnerability Reporting]] |
|- style="background-color: lightgray;" | |- style="background-color: lightgray;" | ||
| − | | | + | | 1400 |
| − | | | + | | 1500 |
| − | | ESTAPI Framework | + | | ESTAPI Framework |
| − | | How do we test and ensure that implementations meet the specifications defined in the API in a cross-platform and demonstratible manner? | + | | 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]] | + | *[[ESAPI Testing Framework]] |
|- style="background-color: lightblue;" | |- style="background-color: lightblue;" | ||
| − | | | + | | 1500 |
| − | | | + | | 1515 |
| colspan="3" | Coffee Break | | colspan="3" | Coffee Break | ||
| − | |- | + | |- |
| − | | | + | | 1515 |
| − | | | + | | 1615 |
| − | | Documentation | + | | 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. | + | | 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 Roadmap]] |
| − | * [[ESAPI Documentation Sub-Project]] | + | *[[ESAPI Documentation Sub-Project]] |
| − | * [[ESAPI Documentation Sub-Project Budget]] | + | *[[ESAPI Documentation Sub-Project Budget]] |
| + | |||
|- style="background-color: lightgray;" | |- style="background-color: lightgray;" | ||
| − | | | + | | 1615 |
| − | | | + | | 1630 |
| − | | Mission De-Briefing | + | | 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. | + | | 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 | | n/a | ||
|- style="background-color: lightblue;" | |- style="background-color: lightblue;" | ||
| − | | | + | | 2100 |
| − | | ???? | + | | ???? |
| − | | ESAPI 2.0GA Release Celebration | + | | ESAPI 2.0GA Release Celebration |
| − | | Celebrate the release of ESAPI 2.0GA (and beyond) with beers with the ESAPI Team (Sponsors: TBA) | + | | Celebrate the release of ESAPI 2.0GA (and beyond) with beers with the ESAPI Team (Sponsors/Location: TBA) |
| n/a | | n/a | ||
|} | |} | ||
| + | |||
<noinclude> | <noinclude> | ||
=== Attending the ESAPI Summit === | === Attending the ESAPI Summit === | ||
| − | If you are planning to attend this summit, please | + | 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:Chris Schmidt|Chris Schmidt]] - Meeting Leader | ||
| Line 102: | Line 100: | ||
<noinclude> | <noinclude> | ||
| + | |||
== Summit 2008 == | == Summit 2008 == | ||
Latest revision as of 05: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.
- Chris Schmidt - Meeting Leader
- Jim Manico - ESAPI Project Manager
- jOHN Steven - Cigital Principal, ESAPI Malcontent
- Kevin Wall - CenturyLink; ESAPI crypto guy
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:
- Jeff Williams, Aspect Security - ESAPI Project Lead
- Dave Wichers, Aspect Security - ESAPI Java Committer
- Ron Monzillo, Sun Microsystems - Java EE Security Architect
- Arshan Dabirsiaghi, Aspect Security - OWASP Intrisic Security Working Group Chair
- Jerry Hoff, Aspect Security
- Mike Fauzy, Aspect Security
- Kevin Fealey, Aspect Security - ESAPI Swingset Lead
- Jim Manico, Aspect Security - ESAPI Java Committer
- Steve Lavenhar, Booz Allen Hamilton
- Lian Jin, Booz Allen Hamilton
- John Steven, Cigital, Technical Director
- Joel Winstead, Cigital
- Alex Smolen, Foundstone - ESAPI .NET Lead
- Andy Miller, Lockheed Martin
- John Munsch, Lockheed Martin
- Steve Christey, MITRE - CVE/CWE Project Lead
The following pages contain our thoughts/results from the summit.
Summary: TODO
Links
- ESAPI Charter
- ESAPI Roadmap
- ESAPI Adoption Strategy
- ESAPI Framework Strategy
- ESAPI Assurance
- ESAPI Documentation
- ESAPI Marketing
- ESAPI Tooling
- ESAPI Static Analysis Support
- ESAPI Performance
- ESAPI Internationalization
- ESAPI Installation
