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 "OWASP EU Summit 2008 Working Sessions"
(→<font color="white"> OWASP Education Project</font>) |
(→<font color="white"> OWASP Education Project</font>) |
||
Line 98: | Line 98: | ||
* How to create lessons, classes, courses from OWASP project material? | * How to create lessons, classes, courses from OWASP project material? | ||
'''Additional Details:''' | '''Additional Details:''' | ||
+ | There is plenty of knowledge available inside the OWASP community. This is spread via the OWASP AppSec Conferences and the | ||
+ | local chapter meetings, not to forget the books available now. Another, very important way to distribute the available knowledge is | ||
+ | to teach! In plenty presentations knowledge is put into slides to share it. | ||
+ | The next step is to reuse the information of those presentations and create training material. In a Boot Camp for example, it's not only | ||
+ | about telling how to break stuff, but let the attendees break it themselfs. Also let them fix the problems, with guidiance of the experienced! | ||
...<br/> | ...<br/> | ||
'''Projected Outcomes:''' | '''Projected Outcomes:''' |
Revision as of 22:38, 24 September 2008
- 1 THIS IS STILL under heavy UPDATES (i.e. work in progress)
- 2 WORKING SESSIONS - November 3rd, 4th & 5th (Mon, Tue & Wed)
- 3 WORKING SESSIONS - November 4rd & 5th (Tue & Wed) (DETAILS)
- 3.1 OWASP Top 10 2009
- 3.2 OWASP Strategic Planning
- 3.3 OWASP Education Project
- 3.4 Winter Of Code 2009
- 3.5 Enterprise Security API Project
- 3.6 ISWG: Browser Security
- 3.7 ISWG: Web Application Framework Security
- 3.8 OWASP .NET Project
- 3.9 Code Review (next version)
- 3.10 OWASP Awards
- 3.11 OWASP Intra Governmental Affairs
- 3.12 OWASP CD/DVD
- 3.13 OWASP ASDR
- 4 Draft notes
THIS IS STILL under heavy UPDATES (i.e. work in progress)
WORKING SESSIONS - November 3rd, 4th & 5th (Mon, Tue & Wed)
Monday
- OWASP ISWG: Browser Security (part 1) - 4h . . . (ISWG = Intrinsic Security Working Group)
Tuesday
- Working Sessions Operational model - 1h , ALL to attend
- OWASP Strategic Planning for 2009 - 3h
- OWASP Tool's Projects (consolidation action-plan) - 3h
- OWASP ISWG: Web Application Framework Security (part 1) - 3h . . . (ISWG = Intrinsic Security Working Group)
- OWASP Documentation Projects (consolidation action-plan) - 3h
- Winter Of Code 2009 - 4h
- OWASP .NET Project - 2h
- Two-way Internationalization of OWASP Content - 2h
Wednesday
- OWASP Top 10 2009 - 2h
- OWASP Education Project - 2h
- ESAPI Project - 4h
- Code Review (next version) - 2h
- Testing Guide (next version) -2h
- OWASP Certifications - 2h
- OWASP Application Security Desk Reference (ASDR) - 4h
- OWASP Intra Governmental Affairs - 2h
- OWASP Awards - 2h
- OWASP Website -2h
- OWASP Advisory Board (private presentation) - 2h
- OWASP CD/DVD - 2 h
- OWASP Board Meeting (public session) - 3h
WORKING SESSIONS - November 4rd & 5th (Tue & Wed) (DETAILS)
OWASP Top 10 2009 |
---|
Working Session Lead: {name}
Additional Details:
...
|
OWASP Strategic Planning |
---|
Working Session Lead: OWASP Board
Objectives:
Additional Details:
...
|
OWASP Education Project |
---|
Working Session Lead: Sebastien Deleersnyder
Additional Details:
There is plenty of knowledge available inside the OWASP community. This is spread via the OWASP AppSec Conferences and the
local chapter meetings, not to forget the books available now. Another, very important way to distribute the available knowledge is
to teach! In plenty presentations knowledge is put into slides to share it.
The next step is to reuse the information of those presentations and create training material. In a Boot Camp for example, it's not only
about telling how to break stuff, but let the attendees break it themselfs. Also let them fix the problems, with guidiance of the experienced!
...
|
Winter Of Code 2009 |
---|
Working Session Lead: Paulo Coimbra
Additional Details:
...
|
Enterprise Security API Project |
---|
Working Session Lead: Jeff Williams
Additional Details:
...
|
ISWG: Browser Security |
---|
Working Session Lead: Arshan Dabirsiaghi
Additional Details:
ISWG = Intrinsic Security Working Group
|
ISWG: Web Application Framework Security |
---|
Working Session Lead:Arshan Dabirsiaghi
Additional Details:
ISWG = Intrinsic Security Working Group
|
OWASP .NET Project |
---|
Working Session Lead:Mark Roxberry
Additional Details:
Projected Outcomes:
|
Code Review (next version) |
---|
Working Session Lead:Eoin Keary
Additional Details:
|
OWASP Awards |
---|
Working Session Lead:Colin Watson
Additional Details:
|
OWASP Intra Governmental Affairs |
---|
Working Session Lead:Dhruv Soi
Additional Details:
|
OWASP CD/DVD |
---|
Working Session Lead:Matt Tesauro
Additional Details:
|
OWASP ASDR |
---|
Working Session Lead:Leonardo Cavallari Militelli
Additional Details:
...
|
Draft notes
Note: there needs to be a 1h session on the 1st day of working sessions (Tue) to explain the rules of the game, how everything will work and what is expected from each WS (Working Session)
- Working Sessions can meet simultaneously or by some method of time allotment (depends on scheduling and priority)
- Open membership, first order of business is to confirm chair and secretary of group (We can get this setup and discuss on the lists now, so we are running when we get to the Summit)
- Dinis, Paulo suggested that working groups will produce OWASP Initiatives, Statements, Decisions.
- OWASP Initiatives, Statements and Decisions can be distributed in electronic form prior to the Summit or a Working Group assembly.
- Additionally, time should be allocated for anything new at the actual Working Group assembly. (Again, we can get the ball rolling on this now and have discussion and motion at Summit).
- Simple Majority to Pass Motions (I can distribute a Roberts Rules of Order - Lite prior to the meeting to the chair)
- Board Reserves Veto and Tabling Authority at the Summit
- Working Groups:
- OWASP Top 10 2009
- OWASP Governance (e.g. International guidelines, Board member confirmation)
- Projects (e.g. Organize and rate projects, Development plans,Documentation
- Chapter Governance (e.g. Budgets, Activities)
- OWASP Future (e.g. Action Plan for 2009, Investment recommendation, 5 year Outlook)
- Web Vulnerability Assessment (Code Review/Testing)
- Global Community Outreach (PR Issues, Pro Bono opportunities)
- Web Technology (e.g. Browser security wishlist, architectural recommendations, technology recommendations)
Agenda
- Opening Statement
- Motions on the table (1st, 2nd, Vote)
- New Business (new motions, statements for record)
- Closing Statement
- As the first ever of this format, we should invite working group chairs and discuss a potential list of motions to get them started (specifically for
financially related motions, e.g. Dinis mentioned $200K USD investment plan as an example in an earlier e-mail). What kinds of things to start with. Then they can put the ideas to a list or lists for discussion prior to the meeting.
Working Sessions outcomes
- OWASP Initiates: "Spend xyz on Project yyy" , "Plan to organize all OWASP tools / books" , "Stategy to organize and rate ALL OWASP projects", "6 month Development plan for EASPI"
- Public Statements: "Here is the OWASP Top 10 2009", "This is what OWASP's position is on xxx" , "Browser security wish-list for Browsers (IE, Mozilla, Safari and Opera)"
- OWASP Decisions: "Action plan for OWASP in 2009", "Hire x developers to support projects", "next 200k USD investment plan", "OWASP governance and vote of 6th Board Member", "Internaltional OWASP non-profit organizations guidelines",
Summit
- Should a Board Member chair?
- Agenda
- Opening Statement (this is the first Summit, so this is a special thing)
- Overall Summit meeting can be an informational meeting about Working group motions. Board can approve, veto or table motions from Working
Groups. However, if doing this at the Summit, there may be controversial issues where the Board rejects a motion. Each working group has a spot on this agenda.
- OWASP Motions not from Working Groups, allocate time for this.
- Closing Statement