This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Summit 2011 Working Sessions/Session025"

From OWASP
Jump to: navigation, search
Line 5: Line 5:
 
|-
 
|-
  
−
| short_working_session_description=
+
| short_working_session_description= This will be a "NO FLUFF" track where we pull out ourlaptops (not for email/IM), and show people how to develop securecode. Chris Schmidt referred to this here: http://yet-another-dev.blogspot.com/2010/11/cross-pollination-its-not-just-for-bees.html  The Global Summit in Portugal will be a prototype for this new type of "track" and hopefully we can continue it in Minnesota for AppSec USA 2011. Pravir led something like this with SAMM (but regarding process) in Portugal the first time around and it was incredibly valuable.
 +
 
  
 
|-
 
|-
Line 26: Line 27:
 
|-
 
|-
  
−
| summit_session_objective_name1=  
+
| summit_session_objective_name1= Track Mission: Building Security In: Using OWASP tools/techniques/code to build secure applications. (The list below is not in any particular order. In fact, that may be something to talk about. I've tried to provide four (4) one-hour seeds for each session, subject again to discussion)<br>
  
 
| summit_session_objective_name2 =  
 
| summit_session_objective_name2 =  
Line 50: Line 51:
 
|-
 
|-
  
−
| working_session_additional_details =  
+
| working_session_additional_details = '''Rules of Engagement''' <br>*Facilitator role replaces "speaker". They lead the session, but the session is a working session, laptops open, whiteboards filling. This is not a lecture. <br>
 +
*Other facilitators adopt the present facilitator's goal as their own and we drive the concept/design/code forward Dissenting views are for drinks later. <br>
 +
*Sessions are open to all participants provided they have at least the ability to read the chosen language, and have the following things installed when they arrive:<br>
 +
**Our victim app<br>
 +
**All session dependencies<br>
 +
**Dev tools sufficient to build and run the app and our dependencies<br>
 +
*Facilitators must agree to attend six (6) out of eight (8) sessions. Failing that, they're booted from the next venue<br>
 +
*The objective of each session is split between educating participants and bringing the state of the practice forward.<br>
 +
*Participants may bring whatever code they like, provided they contribute it to OWASP.<br>
 +
*Facilitators should seek to absorb any new developments into the next conference session. IE: each session should have some new and unique content <br>
 +
*Facilitators don't 'own' topics, in fact, I'd like them to rotate between cons. if possible. <br> <br>
 +
'''1. Applying ESAPI Input Validation'''
 +
*Serial Decomp: Decode, canonicalize, filter<br>
 +
*Structured data (SSN, CC, etc.) <br>
 +
*Unstructured data (comments, blogs, etc.) <br>
 +
*Other input exaples (ws-, database, etc.) <br>
 +
'''2. Defining AppSensor Sensors for:'''<br>
 +
*Forced Browsing <br>
 +
*Request Velocity<br>
 +
*Unexpected encodings<br>
 +
*Impersonation (Sudden user switch) <br>
 +
'''3. Managing Sessions'''<br>
 +
*Across requests<br>
 +
*Across containers<br>
 +
*Invalidating sessions (Timeout, attack event, logout)<br>
 +
*Invalidating sessions (across containers, SSO token invalidation, user termination)<br>
 +
'''4. Protecting Information Stored Client-Side'''<br>
 +
*Threat Modeling the problem <br>
 +
*Protecting theft and re-playability of application-specific info (on client & in flight)<br>
 +
*Protecting theft and re-playability of session-specific info (in flight)<br>
 +
*Protecting session-specific information from attack on the client <br>
 +
'''5. Protecting against CSRF - Dan Cornell, Eric Sheridan '''<br>
 +
*Hygiene: Discuss/show frames-busting, cross-domain policy; Discuss referrer and other red herrings <br>
 +
*Tokens (crafting, scoping, and checking)<br>
 +
*Discussions, techniques on scale<br>
 +
*Discussions, techniquest on CAPTCHA, re-auth, etc. <br>
 +
'''6. Providing Access to Persisted Data'''<br>
 +
*Controlling visibility of tables by role<br>
 +
*Providing access to safe SQL-like query through DAO layer<br>
 +
*Discussions, techniques for providing secure'auto-wiring' / marshaling<br>
 +
*Encoding and canonicalization for storage (or alternatively: Security concerns with heirarchical caching and object pooling) <br>
 +
 
 +
'''7. and 8. TBD'''
 +
 
 +
There also will be a session to process the "Future" of a "NO FLUFF" OWASP Secure Coding Working Group -- How do we scale this idea and how can we get sponsorship for it?  We hope to schedule at least two more "No Fluff" days for 2011.
 +
<br>
 +
 
  
 
|-
 
|-

Revision as of 12:02, 19 December 2010

Global Summit 2011 Home Page
Global Summit 2011 Tracks

{{{summit_ws_logo}}} Applying ESAPI Input Validation
Please see/use the 'discussion' page for more details about this Working Session
Working Sessions Operational Rules - Please see here the general frame of rules.
WORKING SESSION IDENTIFICATION
Short Work Session Description This will be a "NO FLUFF" track where we pull out ourlaptops (not for email/IM), and show people how to develop securecode. Chris Schmidt referred to this here: http://yet-another-dev.blogspot.com/2010/11/cross-pollination-its-not-just-for-bees.html The Global Summit in Portugal will be a prototype for this new type of "track" and hopefully we can continue it in Minnesota for AppSec USA 2011. Pravir led something like this with SAMM (but regarding process) in Portugal the first time around and it was incredibly valuable.
Related Projects (if any)


Email Contacts & Roles Chair


 Operational Manager
 Mailing list
{{{mailing_list}}}
WORKING SESSION SPECIFICS
Objectives
  1. Track Mission: Building Security In: Using OWASP tools/techniques/code to build secure applications. (The list below is not in any particular order. In fact, that may be something to talk about. I've tried to provide four (4) one-hour seeds for each session, subject again to discussion)

Venue/Date&Time/Model Venue/Room
OWASP Global Summit Portugal 2011 		Date & Time


 Discussion Model
participants and attendees

WORKING SESSION OPERATIONAL RESOURCES
Projector, whiteboards, markers, Internet connectivity, power

WORKING SESSION ADDITIONAL DETAILS
Rules of Engagement
*Facilitator role replaces "speaker". They lead the session, but the session is a working session, laptops open, whiteboards filling. This is not a lecture.
  • Other facilitators adopt the present facilitator's goal as their own and we drive the concept/design/code forward Dissenting views are for drinks later.
  • Sessions are open to all participants provided they have at least the ability to read the chosen language, and have the following things installed when they arrive:
    • Our victim app
    • All session dependencies
    • Dev tools sufficient to build and run the app and our dependencies
  • Facilitators must agree to attend six (6) out of eight (8) sessions. Failing that, they're booted from the next venue
  • The objective of each session is split between educating participants and bringing the state of the practice forward.
  • Participants may bring whatever code they like, provided they contribute it to OWASP.
  • Facilitators should seek to absorb any new developments into the next conference session. IE: each session should have some new and unique content
  • Facilitators don't 'own' topics, in fact, I'd like them to rotate between cons. if possible.

1. Applying ESAPI Input Validation

  • Serial Decomp: Decode, canonicalize, filter
  • Structured data (SSN, CC, etc.)
  • Unstructured data (comments, blogs, etc.)
  • Other input exaples (ws-, database, etc.)

2. Defining AppSensor Sensors for:

  • Forced Browsing
  • Request Velocity
  • Unexpected encodings
  • Impersonation (Sudden user switch)

3. Managing Sessions

  • Across requests
  • Across containers
  • Invalidating sessions (Timeout, attack event, logout)
  • Invalidating sessions (across containers, SSO token invalidation, user termination)

4. Protecting Information Stored Client-Side

  • Threat Modeling the problem
  • Protecting theft and re-playability of application-specific info (on client & in flight)
  • Protecting theft and re-playability of session-specific info (in flight)
  • Protecting session-specific information from attack on the client

5. Protecting against CSRF - Dan Cornell, Eric Sheridan

  • Hygiene: Discuss/show frames-busting, cross-domain policy; Discuss referrer and other red herrings
  • Tokens (crafting, scoping, and checking)
  • Discussions, techniques on scale
  • Discussions, techniquest on CAPTCHA, re-auth, etc.

6. Providing Access to Persisted Data

  • Controlling visibility of tables by role
  • Providing access to safe SQL-like query through DAO layer
  • Discussions, techniques for providing secure'auto-wiring' / marshaling
  • Encoding and canonicalization for storage (or alternatively: Security concerns with heirarchical caching and object pooling)

7. and 8. TBD

There also will be a session to process the "Future" of a "NO FLUFF" OWASP Secure Coding Working Group -- How do we scale this idea and how can we get sponsorship for it? We hope to schedule at least two more "No Fluff" days for 2011.

WORKING SESSION OUTCOMES / DELIVERABLES
Proposed by Working Group Approved by OWASP Board

After the Board Meeting - fill in here.

After the Board Meeting - fill in here.

After the Board Meeting - fill in here.

After the Board Meeting - fill in here.

After the Board Meeting - fill in here.

{{{summit_session_deliverable_name6}}}

After the Board Meeting - fill in here.

{{{summit_session_deliverable_name7}}}

After the Board Meeting - fill in here.

{{{summit_session_deliverable_name8}}}

After the Board Meeting - fill in here.

Working Session Participants

(Add you name by clicking "edit" on the tab on the upper left side of this page)

WORKING SESSION PARTICIPANTS
Name Company Notes & reason for participating, issues to be discussed/addressed

{{{summit_session_attendee_company1}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed1}}}

{{{summit_session_attendee_company2}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed2}}}

{{{summit_session_attendee_company3}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed3}}}

{{{summit_session_attendee_company4}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed4}}}

{{{summit_session_attendee_company5}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed5}}}

{{{summit_session_attendee_company6}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed6}}}

{{{summit_session_attendee_company7}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed7}}}

{{{summit_session_attendee_company8}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed8}}}

{{{summit_session_attendee_company9}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed9}}}

{{{summit_session_attendee_company10}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed10}}}

{{{summit_session_attendee_company11}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed11}}}

{{{summit_session_attendee_company12}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed12}}}

{{{summit_session_attendee_company13}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed13}}}

{{{summit_session_attendee_company14}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed14}}}

{{{summit_session_attendee_company15}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed15}}}

{{{summit_session_attendee_company16}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed16}}}

{{{summit_session_attendee_company17}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed17}}}

{{{summit_session_attendee_company18}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed18}}}

{{{summit_session_attendee_company19}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed19}}}

{{{summit_session_attendee_company20}}}
 {{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed20}}}
Retrieved from "https://wiki.owasp.org/index.php?title=Summit_2011_Working_Sessions/Session025&oldid=97092"