Difference between revisions of "Front Range OWASP Conference 2013/CFP"

Revision as of 19:36, 17 January 2013

Call for Presentations

Please direct all interested practitioners and colleagues to this site.

Submission process

Potential speakers may submit abstracts of proposed presentations here.

Abstracts will be formatted automatically during the submission process. However, all uploaded materials must adhere to the following requirements:

• Only Microsoft Word documents, PDFs, rich-text format documents, and text files will be reviewed.
• Author names, affiliations, email addresses, and other personally-identifiable information must be stripped from the uploaded document.
• All presentations must be titled. Titles should appear at the top of the page.
• The overview of the proposed presentation should not exceed 300 words.

Presenters will be allotted 45-minute time slots. One abstract must be submitted for each presentation considered. All abstracts must be written in English.

Evaluation process

The following criteria will determine abstract rankings:

• Applicability to the requested topics (see below)
• Relevance to web application development and operations
• Relevance to the cybersecurity industry at large
• Relevance to the OWASP Foundation
• Strength of presentation (as determined by the review committee)
• Timeliness of submission

Submitted abstracts will be assessed by selected members of the Colorado OWASP chapters. All reviews will be blind and author information will not be visible to reviewers.

Dates and deadlines

Abstract collection will begin January 14th and continue until all speaking slots are filled. Evaluations will occur on a rolling schedule with selected papers announced each Monday, beginning on February 11th. Although the rolling format extends the submission period significantly, potential speakers are advised to submit as early as possible in order to maximize chances for selection.

Final presentations of accepted abstracts must be submitted for review by March 17th. Templates and other presentation formatting constraints will be made available to selected speakers directly.

Phase 1: Jan 14 - Feb 11
Jan 14 - Feb 03: Submission period
Feb 04 - Feb 10: Evaluation period
Feb 11: Selected papers announcement

Phase 2: Feb 04 - Feb 18 (as needed)
Feb 04 - Feb 10: Submission period
Feb 11 - Feb 17: Evaluation period
Feb 18: Selected papers announcement

Phase 3: Feb 11 - Feb 25 (as needed)
Jan 11 - Feb 17: Submission period
Feb 18 - Feb 24: Evaluation period
Feb 25: Selected papers announcement

Phase 4: Feb 18 - Mar 04 (as needed)
Feb 18 - Feb 24: Submission period
Feb 25 - Mar 03: Evaluation period
Mar 04: Selected papers announcement

Presentation evaluation
Mar 17: Final draft presentations due
Mar 18 - Mar 25: Committee final review
Mar 28, 2013: SnowFROC proceedings

Legalities

All speakers must agree with and abide by the OWASP Speaker Agreement v2.0.

Anyone who cannot or will not abide by these terms will not be permitted to present at the conference.

In addition, presenters must agree to allow use of abstract titles, text, speaker names, and bios for conference promotion. With speaker consent, presentation materials will be distributed to conference attendees and will be recorded and archived for future reference.

Preferred topics

The following topics will be prioritized during the selection process.

High-level technical track

• Web application security testing, especially targeting large and complex enterprise applications
• Mobile device security
• Cloud security
  • Impacts on the security model
  • Implementation of security controls
• OWASP tools and projects
  • New and proposed projects
  • Development and status of existing projects

Deep-dive technical track

• Technology-specific presentations (HTML5, AJAX, etc.)
• Secure coding for web applications
• Static code analysis
• Hands-on countermeasures
• Encryption across an n-tiered web application stack
• Auditing web application mash-ups

Management track

• Web application security management (scope, boundaries, responsibilities, legal considerations, etc.)
• Emerging threats
• Planning and managing secure software development life cycles
• Metrics for managing application security
• Business risks associated with application security

Legal track

• Liability related to web application security
• Data ownership and privacy laws within the cloud
• Cybersecurity and privacy legislation and regulation
• Electronic discovery considerations, both traditional and in the cloud
• Cybersecurity considerations related to law enforcement