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

From OWASP
Jump to: navigation, search
m
Line 170: Line 170:
  
 
|summit_session_deliverable_name1 = A practical guideline (cookbook?) for safely storing information in a client program, particularly browsers.  Suggest tying recommendations to a threat model.
 
|summit_session_deliverable_name1 = A practical guideline (cookbook?) for safely storing information in a client program, particularly browsers.  Suggest tying recommendations to a threat model.
|summit_session_deliverable_url_1 = http://www.owasp.org/index.php/Summit_2011_Working_Sessions/Session028/Deliverable_1
 
  
 
|summit_session_deliverable_name2 =  
 
|summit_session_deliverable_name2 =  
|summit_session_deliverable_url_2 =
 
  
 
|summit_session_deliverable_name3 =  
 
|summit_session_deliverable_name3 =  
|summit_session_deliverable_url_3 =
 
  
 
|summit_session_deliverable_name4 =  
 
|summit_session_deliverable_name4 =  
|summit_session_deliverable_url_4 =
 
  
 
|summit_session_deliverable_name5 =  
 
|summit_session_deliverable_name5 =  
|summit_session_deliverable_url_5 =  
+
 
 +
|summit_session_deliverable_name6 =
 +
 
 +
|summit_session_deliverable_name7 =
 +
 
 +
|summit_session_deliverable_name8 =  
  
 
|-
 
|-

Revision as of 16:15, 25 January 2011

Global Summit 2011 Home Page
Global Summit 2011 Tracks

WS. secure coding.jpg Protecting Information Stored Client-Side
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 section will focus on providing mechanisms for protecting important or sensitive data applications and services need to store client-side. Contexts this section aims to cover include:
  • Personal or user-specific information
  • Application-specific information (tokens, secrets)
  • Key configuration data, other EIS/service information

This section will treat these topics over three contexts:

  • "Classic" 3-tier application
  • Phones (ios, Android)
  • RIA
Related Projects (if any)


Email Contacts & Roles Chair
John Steven @

Operational Manager
Mailing list
Subscription Page
WORKING SESSION SPECIFICS
Objectives

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
WORKING SESSION OUTCOMES / DELIVERABLES
Proposed by Working Group Approved by OWASP Board

A practical guideline (cookbook?) for safely storing information in a client program, particularly browsers. Suggest tying recommendations to a threat model.

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.

After the Board Meeting - fill in here.

After the Board Meeting - fill in here.

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
Elke Roth-Mandutz @
GSO-University of Applied Sciences

Colin Watson


Chris Schmidt @
Aspect Security

Justin Clarke @
Gotham Digital Science