Summit 2011 Working Sessions/Session025

Global Summit 2011 Home Page
Global Summit 2011 Tracks

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	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
Nishi Kumar @	FIS