Summit 2011

Welcome
{| cellspacing="0" cellpadding="20" border="0" class="FCK__ShowTableBorders"
 * [[Image:OWASPGlobalSummitLogo-3THISONEHASTHEMOSTVOTESSOFAR.jpg|border|center|462x347px]]
 * [[Image:OWASPGlobalSummitLogo-3THISONEHASTHEMOSTVOTESSOFAR.jpg|border|center|462x347px]]

Dear OWASP Leaders and appsec community,
The Summit will be held February 8th-11th in (Cascais) Lisbon, Portugal. This will be the place where appsec experts meet, discuss, work, socialize, and set the roadmap for OWASP in coming years.

The Summit Activates *You*
Whereas the OWASP AppSec conferences are great places to listen to interesting talks, go for training, and meet with OWASP people, the Global Summit is the place where we all sit down together and take the time to discuss and work out plans, projects and solutions for the appsec future.

Examples of topics:


 * How should we support the OWASP projects?
 * How can we work with browser vendors to enhance security (see "Browser Day" tab above)?
 * How should the community reach out to developers and education institutions?
 * How often should we publish the OWASP Top 10?
 * How can OWASP support your chapter?


 * valign="top" |
 * valign="top" |

Organizing Committee
Lorna Alamri, Brad Causey, Justin Clarke, Paulo Coimbra, Dinis Cruz, Martin Knobloch, Dave Wichers, John Wilander, Jason Li, Tara Causey, Sarah Baso.


 * valign="top" |

Who's Invited?
As an OWASP leader you are automatically invited to the summit, but we also welcome leading experts from industry and academia. Together we can create a more secure web. Check the "How Do I Join?" tab above for more info.


 * }

Operational guidelines
Following the first meeting of the Summit 2011 Organizational team, here are the current proposed operational guidelines:


 * 1) the summit is an annual event
 * 2) outside OWASP conference
 * 3) the summit should take place in January not later then begin of February
 * 4) the summit takes 3 to 4 days
 * 5) budget aim is US$ 150'000 US$ where 50'000 from OWASP and US$100'000 from sponsors
 * 6) attendees targets are:
 * 7) OWASP Funded:
 * 8) Board
 * 9) Committee Members
 * 10) Chapter / sponsor Funded:
 * 11) Chapter Leaders
 * 12) Project Leaders
 * 13) venue / location criteria (no decision on the venue)
 * 14) 1 key organizer in close contact with the venue
 * 15) hosting 30 to 100 people
 * 16) US$2'000 a head (flight/accommodation/food/beers)
 * 17) conference facilities
 * 18) multiple meeting rooms
 * 19) one big meeting room e.g. auditorium
 * 20) hotel with the conference facilities or conference venue within walking distance
 * 21) apartments if possible (to share apartments/rooms and save money)
 * 22) 4 to 5 star hotel
 * 23) local food supplier for apartment crashing
 * 24) has to be negotiated with the hotel
 * 25) max 50 km's form international airport
 * 26) sufficient Internet access!

Success factors (what indicates the summit as success)


 * 1) break even
 * 2) the summits are the place to go to discus about and working on Web Application Security
 * 3) review of the past year
 * 4) working sessions on committees, projects and industry sectors (e.g. browsers and frameworks)
 * 5) universities / education sessions
 * 6) committee member election
 * 7) board election
 * 8) strategic OWASP issues
 * 9) road map and action plans for the next 12 month

Other local Summit(s):


 * The conferences are free to organize small, conference bound summit
 * this are not sponsored by OWASP of OWASP summit budget

Browser Day
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.


 * Sandboxing. Is sandboxing the right way forward? Can sandboxing be harmonized with the origin policies for cookies, scripting, and ajax – i e share the same compartmentalization? How should we apply sandboxing to plugins?
 * Securing plugins. Should browsers ship with default plugins? Should plugins be auto-updated? Can plugins or versions of plugins be blacklisted centrally?
 * Enduser warnings. How should browsers signal invalid SSL certs to the enduser? Are we helping security right now? What to do about 50 % of users clicking through warnings?
 * Blacklisting. Can we cooperate better on blacklisting? Does it work between cultures, i e can we have the same process for reporting throughout the world?
 * OS integration. More and more features in browsers get integrated with the underlying operating system. Processes, fonts, filesystem, 3D graphics. How do we secure this?
 * JavaScript. How do we secure the universally deployed web application language? Much focus has been on execution performance but what about security? Will EcmaScript 5 strict-mode be supported anytime soon (currently no support)? Are (more) secure "dialects" such as FBJS and Caja the way to go? What's happening in EcmaScript Harmony?
 * New HTTP headers. Are new opt-in HTTP headers the right way to add security features? For example Strict Transport Security, x-frame-options, origin and Content Security Policy.

XSS Eradication
We will have a half day working session on Cross Site Scripting - specifically how OWASP can make 2011 the year of XSS... going away. How we help bring this about through contributing our knowledge to cornerstone projects, how we can raise the awareness through advocacy, and what we can do to ensure that OWASP and other freely available resources and made available to the wider community, and that they are aware of them.

Enterprise Web Defense Roundtable
How are enterprises defending web applications. Discussion of best practices, effective methods, and new ideas to enhance web application defense. (Session Leader: Michael Coates, Mozilla)

University Outreach
This summit will be the place to bring OWASP Educational Supporters together! What security major and minor educations are out there? How can OWASP participate and influence their curricula? How can the relationship between Universities and OWASP be standardized? What does OWASP have to offer Universities and what can they, in turn, expect from each other?

OWASP Projects
We will have a session on how OWASP should support, grow, and manage projects. This includes: -Assessment criteria -Orphaned projects -Funding -Marketing -Commercial services

OWASP Around the World
OWASP is a fast growing global community. How should we support and manage this growth? During this session we'll look into issues of:


 * Internationalization
 * The global job board
 * New OWASP chapters in parts of the world where we have not spread much yet

More Topics
You know how OWASP works – it's all up to you. Please edit this tab and enter topics we should cover during the Global Summit 2011! If you want you can add your name after each suggestion and we can work out the details with you.


 * Discussion on Douglas Crockford's bold statement that we should stop HTML5 development, fix XSS, and then start over. Is he right? How is OWASP active in the HTML5 development? Check this webcast, jump to 20:50 to hear the XSS part. /John Wilander
 * [Your topic here]

How Do I Join? / Mailing list
As an OWASP leader you are automatically invited to the summit.

The first thing to do is to join the Summit 2011 mailing list.

On the mailing list you'll get first hand information on how to register, exact dates, updates to the agenda, funding for your trip etc.

If you are a leading appsec expert from industry or academia but not yet an OWASP leader you can just contact John.Wilander at owasp.org and we'll try to get you in.

Social Events
It goes without saying – the summit is all about meeting people. So there will be a constant mixture of workshops, dinners, beers and wine. We like to think of the summit as a very social event in itself.

Venue


Below is the link to the Venue of the 2011 OWASP Summit in Lisbon, Portugal.

http://www.camporeal.pt/en/hotel-residences.aspx

The hotel has an Airport Shuttle, Spa, and Golfcourse as well as many other amenities.

A Day in Lisbon, Portugal:

Click this link to see all the City of Lisbon has to offer, which is only a short train ride from the resort. http://www.golisbon.com/portugal/cities/cascais.html or http://www.travel-in-portugal.com/Cascais/ Lisbon - Spreading out along the right bank of the Tagus, its downtown, the Baixa, is located in the 18th-century area around Rossio. East of the arcade Praça do Comércio, are the medieval quarters of Alfama and Mouraria, crowned by the magnificent St. George's Castle. To the west lie Bairro Alto and Madragoa, with their typical streets, and on the western extreme is Belém, with its Belém Tower, (the sentinel over the Tagus river that protects the entrance into Lisbon), the Jerónimos Monastery (masterpieces of Manueline architecture and classified in UNESCO's International Heritage list) and the Cultural Center of Belém.Museums: Ancient Art, Chiado (Contemporary Art), Tile, Archaeology, Ethnology, Coach, Costume, Theater, Maritime, Military, City, Gulbenkian, Modern Art Center, and the Ricardo Espirito Santo Silva Foundation. Palaces open to the public: Ajuda and Fronteira. Churches: Cathedral (with Treasury); São Vicente de Fora; Conceição Velha (Manueline), São Roque and Sacred Art; Madre Deus; Santa Engrácia Pantheon (Baroque), and the Estrela Basilica. Shopping: Downtown; Avenida de Roma, Praça de Londres, Avenida Guerra Junqueiro, and Amoreiras. Nightlife: Bairro Alto and Avenida 24 de Julho. Guided Tours

Sponsoring
We will welcome a few sponsors of this very special event, typically organization that participate in the summit. If you are interested in supporting the global summit, please contact Lorna.Alamri at owasp.org.

'''Attendees that qualify to be sponsored by OWASP Some leaders that are active within OWASP may qualify to have all or partial transportation and lodging paid for by OWASP. To be considered for qualification, you must meet one or more of the following criteria:'''


 * 1) Member of the OWASP Board
 * 2) Active member of a Global Committee (as determined by the OWASP Board)
 * 3) Operational personnel that are necessary for the operation of the Summit

Current sponsorship budget is $50,000 for the Summit.

If you feel you might qualify, please contact Brad Causey or Jason Li. If you do not meet these criteria, and still feel that you should be sponsored, please contact or

Applying for Chapter or Project Sponsorship
Application for OWASP Chapter or Project Funding

Letters and Summit Materials
[[Media:OWASP_summit2011-DC-update.pdf|Summit 2011 Presentation for AppSec DC]] Application for OWASP Chapter or Project Funding Template Letter - 2011 Global Summit Basic Invitation Template Letter - 2011 Global Summit University Outreach Invitation Template Letter - 2011 Global Summit Government Invitation Template Letter - 2011 Global Summit Request for Employer Funding and Sponsorship Template Letter - 2011 Global Summit Request for Employer Funding, Version 2