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

From OWASP
Jump to: navigation, search
 
(20 intermediate revisions by 9 users not shown)
Line 5: Line 5:
 
| summit_session_attendee_name1 =  
 
| summit_session_attendee_name1 =  
 
| summit_session_attendee_email1 =  
 
| summit_session_attendee_email1 =  
 +
| summit_session_attendee_username1 =
 
| summit_session_attendee_company1=
 
| summit_session_attendee_company1=
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed1=
+
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed1=  
  
| summit_session_attendee_name2 =  
+
| summit_session_attendee_name2 = Vishal Garg
| summit_session_attendee_email2 =  
+
| summit_session_attendee_email2 = vishalgrg@gmail.com
| summit_session_attendee_company2=
+
| summit_session_attendee_username2 =  
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed2=
+
| summit_session_attendee_company2= AppSecure Labs Ltd
 +
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed2= Consumers should have the visibility into the efforts made by businesses to secure their web portals, before they (consumers) provide their personal and credit card information.
  
| summit_session_attendee_name3 =  
+
| summit_session_attendee_name3 = Doug Wilson
| summit_session_attendee_email3 =  
+
| summit_session_attendee_email3 = dougDOTwilsonATowaspDOTorg
| summit_session_attendee_company3=
+
| summit_session_attendee_username3 = Dallendoug
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed3=
+
| summit_session_attendee_company3= [http://www.mandiant.com Mandiant]
 +
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed3= I have had contact with a variety of government organizations who are interested in measuring more than just flaws or vulnerabilities to get a better view of the value of software rather than just cataloging defects.
  
| summit_session_attendee_name4 =  
+
| summit_session_attendee_name4 = Alexandre Miguel Aniceto
| summit_session_attendee_email4 =  
+
| summit_session_attendee_email4 = alexandre.aniceto@sekirite.org
| summit_session_attendee_company4=
+
| summit_session_attendee_username4 = Alexandre Miguel Aniceto
 +
| summit_session_attendee_company4= Willway
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed4=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed4=
  
 
| summit_session_attendee_name5 =  
 
| summit_session_attendee_name5 =  
 
| summit_session_attendee_email5 =  
 
| summit_session_attendee_email5 =  
 +
| summit_session_attendee_username5 =
 
| summit_session_attendee_company5=
 
| summit_session_attendee_company5=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed5=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed5=
Line 30: Line 35:
 
| summit_session_attendee_name6 =  
 
| summit_session_attendee_name6 =  
 
| summit_session_attendee_email6 =  
 
| summit_session_attendee_email6 =  
 +
| summit_session_attendee_username6 =
 
| summit_session_attendee_company6=
 
| summit_session_attendee_company6=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed6=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed6=
Line 35: Line 41:
 
| summit_session_attendee_name7 =  
 
| summit_session_attendee_name7 =  
 
| summit_session_attendee_email7 =  
 
| summit_session_attendee_email7 =  
 +
| summit_session_attendee_username7 =
 
| summit_session_attendee_company7=
 
| summit_session_attendee_company7=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed7=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed7=
Line 40: Line 47:
 
| summit_session_attendee_name8 =  
 
| summit_session_attendee_name8 =  
 
| summit_session_attendee_email8 =  
 
| summit_session_attendee_email8 =  
 +
| summit_session_attendee_username8 =
 
| summit_session_attendee_company8=
 
| summit_session_attendee_company8=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed8=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed8=
Line 45: Line 53:
 
| summit_session_attendee_name9 =  
 
| summit_session_attendee_name9 =  
 
| summit_session_attendee_email9 =  
 
| summit_session_attendee_email9 =  
 +
| summit_session_attendee_username9 =
 
| summit_session_attendee_company9=
 
| summit_session_attendee_company9=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed9=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed9=
Line 50: Line 59:
 
| summit_session_attendee_name10 =  
 
| summit_session_attendee_name10 =  
 
| summit_session_attendee_email10 =  
 
| summit_session_attendee_email10 =  
 +
| summit_session_attendee_username10 =
 
| summit_session_attendee_company10=
 
| summit_session_attendee_company10=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed10=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed10=
Line 55: Line 65:
 
| summit_session_attendee_name11 =  
 
| summit_session_attendee_name11 =  
 
| summit_session_attendee_email11 =  
 
| summit_session_attendee_email11 =  
 +
| summit_session_attendee_username11 =
 
| summit_session_attendee_company11=
 
| summit_session_attendee_company11=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed11=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed11=
Line 60: Line 71:
 
| summit_session_attendee_name12 =  
 
| summit_session_attendee_name12 =  
 
| summit_session_attendee_email12 =  
 
| summit_session_attendee_email12 =  
 +
| summit_session_attendee_username12 =
 
| summit_session_attendee_company12=
 
| summit_session_attendee_company12=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed12=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed12=
Line 65: Line 77:
 
| summit_session_attendee_name13 =  
 
| summit_session_attendee_name13 =  
 
| summit_session_attendee_email13 =  
 
| summit_session_attendee_email13 =  
 +
| summit_session_attendee_username13 =
 
| summit_session_attendee_company13=
 
| summit_session_attendee_company13=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed13=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed13=
Line 70: Line 83:
 
| summit_session_attendee_name14 =  
 
| summit_session_attendee_name14 =  
 
| summit_session_attendee_email14 =  
 
| summit_session_attendee_email14 =  
 +
| summit_session_attendee_username14 =
 
| summit_session_attendee_company14=
 
| summit_session_attendee_company14=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed14=  
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed14=  
Line 75: Line 89:
 
| summit_session_attendee_name15 =  
 
| summit_session_attendee_name15 =  
 
| summit_session_attendee_email15 =  
 
| summit_session_attendee_email15 =  
 +
| summit_session_attendee_username15 =
 
| summit_session_attendee_company15=
 
| summit_session_attendee_company15=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed15=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed15=
Line 80: Line 95:
 
| summit_session_attendee_name16 =  
 
| summit_session_attendee_name16 =  
 
| summit_session_attendee_email16 =  
 
| summit_session_attendee_email16 =  
 +
| summit_session_attendee_username16 =
 
| summit_session_attendee_company16=
 
| summit_session_attendee_company16=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed16=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed16=
Line 85: Line 101:
 
| summit_session_attendee_name17 =  
 
| summit_session_attendee_name17 =  
 
| summit_session_attendee_email17 =  
 
| summit_session_attendee_email17 =  
 +
| summit_session_attendee_username17 =
 
| summit_session_attendee_company17=
 
| summit_session_attendee_company17=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed17=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed17=
Line 90: Line 107:
 
| summit_session_attendee_name18 =  
 
| summit_session_attendee_name18 =  
 
| summit_session_attendee_email18 =  
 
| summit_session_attendee_email18 =  
 +
| summit_session_attendee_username18 =
 
| summit_session_attendee_company18=
 
| summit_session_attendee_company18=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed18=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed18=
Line 95: Line 113:
 
| summit_session_attendee_name19 =  
 
| summit_session_attendee_name19 =  
 
| summit_session_attendee_email19 =  
 
| summit_session_attendee_email19 =  
 +
| summit_session_attendee_username19 =
 
| summit_session_attendee_company19=
 
| summit_session_attendee_company19=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed19=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed19=
Line 100: Line 119:
 
| summit_session_attendee_name20 =  
 
| summit_session_attendee_name20 =  
 
| summit_session_attendee_email20 =  
 
| summit_session_attendee_email20 =  
 +
| summit_session_attendee_username20 =
 
| summit_session_attendee_company20=
 
| summit_session_attendee_company20=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed20=
 
| summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed20=
  
 
|-
 
|-
 
+
| summit_track_logo = [[Image:T._metrics.jpg]]
| summit_session_name = Metrics for positive security properties
+
| summit_ws_logo = [[Image:WS._metrics.jpg]]
 +
| summit_session_name = Metrics and Labeling
 
| summit_session_url = http://www.owasp.org/index.php/Summit_2011_Working_Sessions/Session057
 
| summit_session_url = http://www.owasp.org/index.php/Summit_2011_Working_Sessions/Session057
 +
| mailing_list =
  
| short_working_session_description=We all know that you can’t control what you can’t measure and that you need to measure the right things or you won’t be steering towards the right outcome.  For this session we will define the right outcome as “low risk to an organization from vulnerabilities in applications.” What are the right things to measure? How can we measure them? How can we use these application security metrics to drive towards low application risk.  It would also be great if this could be translated into monetary risk to determine if an organizations investment in applications is not too much or too littleSome of the concepts discussed will be to take a portfolio view of application risk, assigning business risk to applications, counting defects, and measuring SDLC process performance.  This is a big unsolved problem so come prepared with ideas and be willing to take part in a discussion.
+
| short_working_session_description= Consumers and organizations enlist the services of web-based services with no ability to make an informed decision on its securityThis can include enterprise class websites such as payment processing, HR portals, benefits administration, and other corporate services, as well as consumer centric websites such as tax preparation, personal finance, social media, or medical records. While the companies providing these services are unlikely to share detailed information about known vulnerabilities in their systems, it would be beneficial to have a standardized mechanism for describing the security controls and processes in placeIn other words, what are they doing right that should give consumers some level of confidence that the provider exercises application security best practices?
  
 
|-
 
|-
Line 129: Line 151:
 
|-
 
|-
  
| summit_session_objective_name1=  
+
| summit_session_objective_name1 = Discuss positive security properties that should be tracked
  
| summit_session_objective_name2 =  
+
| summit_session_objective_name2 = Discuss options for consumer-friendly labeling
  
| summit_session_objective_name3 =  
+
| summit_session_objective_name3 = Discuss ways to encourage participation in risk labeling
  
 
| summit_session_objective_name4 =  
 
| summit_session_objective_name4 =  
Line 157: Line 179:
 
|-
 
|-
  
|summit_session_deliverable_name1 =  
+
|summit_session_deliverable_name1 = White paper sketching out a standard for a software security label and a plan to finalize the standard.
|summit_session_deliverable_url_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 =  
  
 
|-
 
|-
  
| summit_session_leader_name1 = Chris Wysopal
+
| summit_session_leader_name1 = Chris Eng
| summit_session_leader_email1 = cwysopal@Veracode.com
+
| summit_session_leader_email1 = ceng@Veracode.com
 +
| summit_session_leader_username1 = Chris Eng
  
| summit_session_leader_name2 = Chris Eng
+
| summit_session_leader_name2 =  
| summit_session_leader_email2 = ceng@Veracode.com
+
| summit_session_leader_email2 =  
 +
| summit_session_leader_username2 =
  
 
| summit_session_leader_name3 =  
 
| summit_session_leader_name3 =  
 
| summit_session_leader_email3 =  
 
| summit_session_leader_email3 =  
 +
| summit_session_leader_username3 =
  
 
|-
 
|-
Line 187: Line 213:
 
| operational_leader_name1 =
 
| operational_leader_name1 =
 
| operational_leader_email1 =
 
| operational_leader_email1 =
 +
| operational_leader_username1 =
  
 
|-
 
|-

Latest revision as of 18:47, 7 February 2011

Global Summit 2011 Home Page
Global Summit 2011 Tracks

WS. metrics.jpg Metrics and Labeling
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 Consumers and organizations enlist the services of web-based services with no ability to make an informed decision on its security. This can include enterprise class websites such as payment processing, HR portals, benefits administration, and other corporate services, as well as consumer centric websites such as tax preparation, personal finance, social media, or medical records. While the companies providing these services are unlikely to share detailed information about known vulnerabilities in their systems, it would be beneficial to have a standardized mechanism for describing the security controls and processes in place. In other words, what are they doing right that should give consumers some level of confidence that the provider exercises application security best practices?
Related Projects (if any)


Email Contacts & Roles Chair
Chris Eng @

Operational Manager
Mailing list
Subscription Page
WORKING SESSION SPECIFICS
Objectives
  1. Discuss positive security properties that should be tracked
  2. Discuss options for consumer-friendly labeling
  3. Discuss ways to encourage participation in risk labeling

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

White paper sketching out a standard for a software security label and a plan to finalize the standard.

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



Vishal Garg @
AppSecure Labs Ltd
Consumers should have the visibility into the efforts made by businesses to secure their web portals, before they (consumers) provide their personal and credit card information.
Doug Wilson @
Mandiant
I have had contact with a variety of government organizations who are interested in measuring more than just flaws or vulnerabilities to get a better view of the value of software rather than just cataloging defects.
Alexandre Miguel Aniceto @
Willway