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

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 
====Call for Presentations====
 
====Call for Presentations====
  
Conference organizers are [http://owasp.aerstone.com/cfp actively seeking presentations] relating to the following topics. Please forward this site to all interested practitioners and colleagues.
+
Please distribute 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==
 
==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 [http://owasp.aerstone.com/cfp here].
+
Potential speakers shall submit brief abstracts of proposed presentations [http://owasp.aerstone.com/cfp here].
  
'''Abstract format'''
+
The submission process will format abstracts automatically during the creation process. All uploaded materials, however, must adhere to the following requirements:
<br />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.
 
*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.
 
*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.
 
*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.
 
*The overview of the proposed presentation should not exceed 300 words.
 +
 +
One abstract must be submitted for each presentation considered and all abstracts must be written in English.
  
  
 
==Evaluation process==
 
==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:
+
The following criteria will determine abstract rankings:
*Applicability to the requested topics
+
*Applicability to the requested topics (see below)
*Applicability to the conference theme
+
*Relevance to web application development and operations
*OWASP relevance
+
*Relevance to the cybersecurity Industry at large
*Industry relevance (web application development and operations, general cybersecurity, etc.)
+
*Relevance to the OWASP foundation
*Timeliness of submission
+
 
*Strength of presentation (as determined by the review committee)
 
*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 reviewers will not have visibility to author information.
  
  
 
==Dates and deadlines==
 
==Dates and deadlines==
Abstract collection will occur between January 5th through February 10th, 2013.
+
Abstract collection will occur between January 12th through February 10th, 2013. Initial presentation selections will be announced on or before February 17th. As needed, a rolling collection period will begin on February 17th and continue until all speaking slots are filled.
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.
+
Final presentations of accepted abstracts must be submitted for review by March 14th, 2013. Templates and other presentation formatting constraints will be made available to selected speakers directly.
 +
 
 +
All presentations will be delivered during conference proceedings on March 28th, 2013.
  
  
 
==Legalities==
 
==Legalities==
 
All speakers must agree with and abide by the [[Speaker_Agreement|OWASP Speaker Agreement v2.0]].
 
All speakers must agree with and abide by the [[Speaker_Agreement|OWASP Speaker Agreement v2.0]].
====Anyone who cannot or will not abide by these terms will not be permitted to present at the conference.====
+
 
 +
'''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.
 
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, presentation materials will be distributed to conference attendees and will be archived for future reference.
 
With speaker consent, presentations will be recorded and archived.
 
With speaker consent, presentations will be recorded and archived.
 +
 +
 +
==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
 +
*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 legislation

Revision as of 13:44, 13 January 2013

Contents

Call for Presentations

Please distribute this site to all interested practitioners and colleagues.

Submission process

Potential speakers shall submit brief abstracts of proposed presentations here.

The submission process will format abstracts automatically during the creation process. All uploaded materials, 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.

One abstract must be submitted for each presentation considered and 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 reviewers will not have visibility to author information.


Dates and deadlines

Abstract collection will occur between January 12th through February 10th, 2013. Initial presentation selections will be announced on or before February 17th. As needed, a rolling collection period will begin on February 17th and continue until all speaking slots are filled.

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

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.


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
  • 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 legislation