Front Range OWASP Conference 2013/CFP

From OWASP
Revision as of 20:29, 12 January 2013 by Mark Major (Talk | contribs)

Jump to: navigation, search

Contents

Call for Presentations

Conference organizers are actively seeking presentations relating to the following topics. Please forward this site to all interested practitioners and colleagues.


Tracks and topics

The following topics will be prioritized during the selection process.

High-level technical track

  • Cloud security
    • How cloud hosting changes the security model
    • Implementation of security controls
  • Web application security testing, especially targeting large and complex enterprise applications
  • OWASP tools and projects
    • New and proposed projects
    • Development and status of existing projects

Deep-dive technical track

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

Management track

  • Web application security management: focused on a managerial view of web application security with a special focus on scope, boundaries, responsibilities, and legal considerations
  • Emerging threats
  • Planning and managing secure software development lifecycles
  • Metrics for application security
  • Business risks associated with application security

Legal track

  • Liability considerations related to web application security
  • Data ownership and privacy within the cloud
  • Cybersecurity legislation


Submission process

One abstract must be submitted for each presentation considered. Abstracts must be written in English, should not exceed 300 words, and should be uploaded here.

Abstract format
The submission website will automatically format abstracts during the submission process. Uploaded content, however, 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.


Evaluation process

Submitted abstracts will be assessed by selected members of the Colorado OWASP chapters. All reviews will be blind and reviewers will not have visibility to author information. The following criteria will determine abstract rankings:

  • Applicability to the requested topics
  • Applicability to the conference theme
  • OWASP relevance
  • Industry relevance (web application development and operations, general cybersecurity, etc.)
  • Timeliness of submission
  • Strength of presentation (as determined by the review committee)


Dates and deadlines

Abstract collection will occur between January 5th through February 10th, 2013. Initial presentation selections will be announced by February 17th, and a continuing collection may occur as needed until all tracks are filled.

Final presentations of accepted abstracts must be submitted for review by March 14th, 2013. All presentations will be delivered during conference proceedings on March 28th, 2013.


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, and speaker names and bios for conference promotion. With speaker consent, presentation materials will be distributed to conference attendees and will be archived for future reference. With speaker consent, presentations will be recorded and archived.