How to Host a Conference/Policies and Requirements
These are the requirements imposed on any event using the OWASP brand. All Events must be coordinated with the Foundation and receive pre-approval. Event requests should be submitted via the OWASP Conference Management System (OCMS).
If you have questions or require an exception to any of these please contact the OWASP Staff.
|All content must be vendor neutral||All Events - Core Value|
|All content must be made available to the public after the conference||All Events - Core Value|
|All calls for papers, training and registration must be open and promoted to the public||All Events - Core Value|
|Selecting Committee Members (Training or Papers) must not submit||All Events|
|Use the conference website/wikipage to submit papers. It must supports blind paper submissions.||All Events|
|All events must be conducted in a manner consistent with the OWASP Mission, Principles and Code of Ethics||All Events - Core Value|
|OWASP Event Definitions||All Events|
|OWASP Event Requirements||All Events|
| Local host chapters will share in OWASP event profits under the following schedule. In the case of multiple host chapters, the host chapters will be responsible for determining the division before the event. Policy Document
|All OWASP Events must be coordinated with OWASP Foundation Staff by submitting an events description via OCMS. An approval that the event will be posted on the OWASP Wiki and Event announcement webpage will be sent from the OCMS input. Any request for funding support must follow normal funding request procedures separate from the OCMS submission.||All Events|
|Events must have an OWASP Wiki Page, or a webpage showing the OWASP logo and be linked to the OWASP wiki Events Pages||All Events|
|Only OWASP Board members or their designates may enter into contracts on behalf of the foundation||All Events|
|All finances must be handled by the OWASP Foundation||All Events|
| Complimentary conference admissions are provided to speakers, volunteers, staff, Global Board members and active OWASP Leaders.
A “Leader” is defined as a chapter or project leader that is clearly identified on the chapter or project wiki page AND has been documented as a leader in the Foundation’s records. If a leader registers for a conference complimentary ticket but does not appear for the conference, the chapter will be charged 60% of the retail cost of a conference ticket.
|OWASP individual members in good standing shall receive $50 off admission to all OWASP events charging more than $50 entry fee.||All Events|
|A complete budget must be submitted if the event requires any funds from the OWASP Foundation and funding requests will be reviewed and approved by OWASP Executive Director. Please submit a requests via our Contact Us link on the OWASP Wiki homepage.||Regional/Theme Conferences|
|An OWASP leader should be invited to provide welcome and state of the union.||All Events|
|Global AppSec Conferences must include training||Global AppSec Conferences|
|Global AppSec Conferences must charge an admission fee||Global AppSec Conferences|
|Sessions must be recorded and posted to the public after the conference||Global AppSec Conferences|
|There must be at least one networking event at the conference||Global AppSec Conferences|
|All Training providers are required to sign a Training Instructor Agreement||Training|
|Training revenue will be split 60/40 (OWASP/Training Provider)||Training|
| Each training class allows for two complimentary seats to be made available to OWASP Leaders. This must be included in the Training Instructor Agreement. These are available on a first come basis. Only one training seat per session is allowed per chapter to allow for diversity in distribution of seats.
If a leader registers for a complimentary training seat but does not attend the full training session the chapter will be charged 60% of the retail cost of the training session and the leader will not be given a complimentary ticket (conference or training sessions) for any other Global AppSec events in the following year.
|Speakers must sign a Speaker Agreement||Speakers|
|Speakers will not receive compensation for their speaking engagement||Speakers|
|Event organizers must reach out to the WIA program to assist with the program committee and to help find suitable keynote and invited speakers.||Global AppSec Conferences & Regional Events|
|Event organizers must send an open call for participation for volunteers, papers committee.||Global AppSec Conferences & Regional Events|
|Event organizers should encourage all training and CFP proposals to go through the “Talk bootcamp” process.||Global AppSec Conferences & Regional Events|
|WIA initiative should lead a search for women keynotes, featured, panel speakers.||Global AppSec Conferences & Regional Events|
|Event organizers and WIA initiative should reach out to women speaker lists to encourage training proposals and speakers to submit through the normal CFP process. If there is to be a women in AppSec panels to be organized, the WIA initiative must be involved and feature predominantly women panelists.||Global AppSec Conferences & Regional Events|
| These aren’t quotas, but a goal. Global events organizers are free to exceed these metrics.
*At least 10% of the program committee must be women, and must include the WIA initiative members *At least 50% of keynotes and featured speakers must be women *At least 25% of panel participants must be women. If there are no women participants, the panel should be cancelled. *At least 10% of talks must be women
If these metrics cannot be reached, the organizing committee should reach out to the Conference Manager for assistance, and must apply for an exception if they can’t be reached after all avenues have been exhausted.
|Global AppSec Conferences|
|These aren’t quotas, but an aspiration goal for regional events. Organizers are free to exceed these metrics.
*At least one of the program / papers committee must be a woman, and should include the WIA initiative members *At least one of keynotes, featured and invited speakers must be a woman *At least 25% of panel participants should be women. If a panel has no women participants, it should be cancelled *At least 10% of talks chosen should be women speakers