Difference between revisions of "Category:OWASP Legal Project"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
 
+
==== Home ====
{{ProjectTabs |
+
Proj_About=  
+
<table width="100%" valign="top"><tr><th width="50%"> </th><th> </th></tr><tr valign="top"><td>
+
''OWASP Documentation Project''
+
  
'''Secure Software Development Contract Annex (Contract Annex)'''
+
{| width="100%"
 +
|-
 +
! width="66%" |
 +
! width="33%" |
 +
|- valign="top"
 +
|
 +
The goal of the '''OWASP Legal Project''' is to ensure, at each stage of the life cycle, that appropriate attention has been paid to security. The cornerstone of the Legal Project is its Secure Software Development Contract Annex. The Contract Annex helps software developers and their clients negotiate and capture important contractual terms and conditions related to the security of the software to be developed or delivered. Here are two examples:
  
The Secure Software Development Contract Annex developed by the OWASP Legal Project helps software developers and their clients negotiate and capture important contractual terms and conditions related to the security of the software to be developed or delivered. The goal of the Contract Annex is to ensure, at each stage of the life cycle, that appropriate attention has been paid to security. For more information, please [mailto:jeff.williams@owasp.org contact us].
+
* '''Implementation.''' Developer agrees to provide and follow a set of secure coding guidelines and to use a set of common security control programming interfaces (such as the [http://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API OWASP ESAPI]). Guidelines will indicate how code should be formatted, structured, and commented. Common security control programming interfaces will define how security controls must be called and how security controls shall function. All security-relevant code shall be thoroughly commented. Specific guidance on avoiding common security vulnerabilities shall be included. Also, all code shall be reviewed by at least one other Developer against the security requirements and coding guideline before it is considered ready for unit test.
 +
* '''Security Analysis and Testing.''' Developer will perform application security analysis and testing (also called "verification") according to the verification requirements of an agreed-upon standard (such as the [http://www.owasp.org/index.php/ASVS OWASP ASVS]). The Developer shall document verification findings according to the reporting requirements of the standard. The Developer shall provide the verification findings to Client.
 +
|
 +
[[Image:Esapi-sponsors.PNG]]
  
'''How the Contract Annex Works'''
+
|}
  
Here are two examples:
+
{| width="100%"
 +
|-
 +
! width="33%" |
 +
! width="33%" |
 +
! width="33%" |
 +
|- valign="top"
 +
|
 +
== Let's talk here  ==
  
* '''Implementation.''' Developer agrees to provide and follow a set of secure coding guidelines and to use a set of common security control programming interfaces (such as the [http://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API OWASP ESAPI]). Guidelines will indicate how code should be formatted, structured, and commented. Common security control programming interfaces will define how security controls must be called and how security controls shall function. All security-relevant code shall be thoroughly commented. Specific guidance on avoiding common security vulnerabilities shall be included. Also, all code shall be reviewed by at least one other Developer against the security requirements and coding guideline before it is considered ready for unit test.
+
[[Image:Asvs-bulb.jpg]]'''Legal Communities'''  
* '''Security Analysis and Testing.''' Developer will perform application security analysis and testing (also called "verification") according to the verification requirements of an agreed-upon standard (such as the [http://www.owasp.org/index.php/ASVS OWASP ASVS]). The Developer shall document verification findings according to the reporting requirements of the standard. The Developer shall provide the verification findings to Client.
+
  
</td><td>
+
Further development of Legal Project documents occurs through mailing list discussions and occasional workshops, and suggestions for improvement are welcome. For more information, please [mailto:jeff.williams@owasp.org contact us].  
;
+
<br>'''Latest News'''
+
* [http://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API OWASP Enterprise Security API (ESAPI)] has been integrated into the OWASP Secure Software Development Contract Annex
+
* [http://www.owasp.org/index.php/ASVS OWASP Application Security Verification Standard (ASVS)] has been integrated into the OWASP Secure Software Development Contract Annex
+
* Request for users/adopters/supporters. [mailto:jeff.williams@owasp.org Please let us know your stories!]
+
* [http://www.owasp.org/index.php/Category:OWASP_Legal_Project#tab=News Legal Project News Archives]
+
* [mailto:owasp-legal@lists.owasp.org Legal Project Mailing List]
+
</td></tr>
+
</table>
+
  
 +
*[https://lists.owasp.org/mailman/listinfo/owasp-legal owasp-legal mailing list (this is the main list)]
  
 +
|
 +
== Got translation cycles?  ==
 +
 +
[[Image:Asvs-writing.JPG]]'''Legal Project Translations'''
 +
 +
The Legal Project project is always on the lookout for volunteers who are interested in translating Legal Project documents into another language.
 +
 +
*Translation Onboarding Instructions -- Coming soon!
  
 
|  
 
|  
 +
== Related resources ==
  
Proj_Documentation=
+
[[Image:Asvs-satellite.jpg]]'''OWASP Resources'''  
'''More About the Contract Annex'''
+
  
* One Page Datasheet ([http://www.owasp.org/images/a/aa/Legal_One_Page_Handout.doc Word], [http://www.owasp.org/index.php/Image:Legal_One_Page_Handout.pdf PDF])
+
* [[Top Ten|OWASP Top Ten]]
* Sample verification fee schedule template ([http://www.owasp.org/index.php/Image:Sample_ASVS_Fee_Schedule_Template.xls Excel])
+
* [[ASVS|OWASP Application Security Verification Standard]]
+
*[http://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API OWASP ESAPI]  
'''Related projects'''
+
*[http://www.owasp.org/index.php/Category:OWASP_Newsletter#tab=Press_releases OWASP Press Releases]
 +
|}
  
* [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top Ten]
+
==== Downloads ====
* [http://www.owasp.org/index.php/Category:OWASP_Application_Security_Verification_Standard_Project OWASP ASVS Project]
+
* [http://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API OWASP ESAPI]
+
  
====Download====
+
{| width="100%"
'''Contract Annex'''
+
|-
 +
! width="33%" |
 +
! width="33%" |
 +
|- valign="top"
 +
|
 +
[[Image:Asvs-step1.jpg]]'''1. About Legal Project Documents'''  
  
Download the Contract Annex now, for free, [http://www.owasp.org/index.php/Image:OWASP_Secure_Software_Contract_Annex.doc here].
+
* One Page Datasheet ([http://www.owasp.org/images/a/aa/Legal_One_Page_Handout.doc Word], [http://www.owasp.org/index.php/Image:Legal_One_Page_Handout.pdf PDF])
  
'''Other Versions'''
+
[[Image:Asvs-step2.jpg]]'''2. Get Legal Project Documents'''  
* Contract Annex ([http://www.owasp.org/index.php/OWASP_Secure_Software_Contract_Annex HTML])
+
  
<br>
+
* Contract Annex in English ([http://www.owasp.org/index.php/Image:OWASP_Secure_Software_Contract_Annex.doc Word], [http://www.owasp.org/index.php/OWASP_Secure_Software_Contract_Annex HTML])
{{OWASP Book|4037498}}
+
* Contract Annex in Spanish ([http://www.owasp.org/index.php/Anexo_para_Contrato_de_Software_Seguro_de_OWASP HTML])
<br>
+
* Verification schedule in English ([http://www.owasp.org/index.php/Image:Sample_ASVS_Fee_Schedule_Template.xls Excel])
+
|
+
  
Proj_Mail= '''Project News'''
+
{{OWASP Book|4037498}}
  
* 03/20/2009 - OWASP Contract Annex updated to support the use of [http://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API OWASP ESAPI].
+
[[Image:Asvs-step3.jpg]]'''3. Learn About Legal Project Documents'''
* 01/22/2009 - OWASP Contract Annex updated to support the use of [http://www.owasp.org/index.php/ASVS OWASP ASVS].
+
* 01/01/2009 - OWASP Contract Annex language integrated into the [http://www.sans.org/appseccontract/ SANS Application Security Procurement Language].
+
* 11/30/2006 - OWASP Contract Annex [http://www.owasp.org/index.php/Image:OWASP_Secure_Software_Contract_Annex.doc Release version published].
+
  
|
+
* Coming soon!
  
Proj_Related= [[Top Ten|OWASP Top Ten]] |
+
|}
Proj_Contributors=
+
<table width="100%" valign="top"><tr><th width="25%"> </th><th width="25%"> </th><th> </th></tr><tr valign="top"><td>
+
'''Project Leader'''
+
* [[:User:Jeff Williams|Jeff Williams]]
+
'''Project Contributors'''
+
* [http://www.owasp.org/index.php/User:Mike.boberski Mike Boberski]
+
  
</td><td>
+
<br>  
  
'''Project Sponsorship'''
+
==== Glossary ====
  
[[Image:Aspect logo.jpg]]  
+
[[Image:Asvs-letters.jpg]]'''Legal Project Terminology'''  
</td><td>
+
'''Users and Adopters'''
+
  
Coming soon! Please let us know how your organization is using the OWASP Contract Annex. Include your name, organization's name, and brief description of how you use the annex. The project lead can be reached at [mailto:jeff.williams@owasp.org Jeff Williams] Thanks for supporting OWASP!  
+
* Coming soon!
  
</td></tr>
+
==== Project Details  ====
</table>
+
{{:GPC_Project_Details/OWASP_Legal_Project | OWASP Project Identification Tab}}
}}
+
''This project licensed under the Licensed under [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution ShareAlike 3.0].''
+
<br>
+
  
= Articles Below - More About the Contract Annex and Using It =
+
__NOTOC__ <headertabs /> ''This project licensed under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution ShareAlike 3.0].'' <br>

Revision as of 10:36, 11 March 2010

Home

The goal of the OWASP Legal Project is to ensure, at each stage of the life cycle, that appropriate attention has been paid to security. The cornerstone of the Legal Project is its Secure Software Development Contract Annex. The Contract Annex helps software developers and their clients negotiate and capture important contractual terms and conditions related to the security of the software to be developed or delivered. Here are two examples:

  • Implementation. Developer agrees to provide and follow a set of secure coding guidelines and to use a set of common security control programming interfaces (such as the OWASP ESAPI). Guidelines will indicate how code should be formatted, structured, and commented. Common security control programming interfaces will define how security controls must be called and how security controls shall function. All security-relevant code shall be thoroughly commented. Specific guidance on avoiding common security vulnerabilities shall be included. Also, all code shall be reviewed by at least one other Developer against the security requirements and coding guideline before it is considered ready for unit test.
  • Security Analysis and Testing. Developer will perform application security analysis and testing (also called "verification") according to the verification requirements of an agreed-upon standard (such as the OWASP ASVS). The Developer shall document verification findings according to the reporting requirements of the standard. The Developer shall provide the verification findings to Client.

Esapi-sponsors.PNG

Let's talk here

Asvs-bulb.jpgLegal Communities

Further development of Legal Project documents occurs through mailing list discussions and occasional workshops, and suggestions for improvement are welcome. For more information, please contact us.

Got translation cycles?

Asvs-writing.JPGLegal Project Translations

The Legal Project project is always on the lookout for volunteers who are interested in translating Legal Project documents into another language.

  • Translation Onboarding Instructions -- Coming soon!

Related resources

Asvs-satellite.jpgOWASP Resources

Downloads

Asvs-step1.jpg1. About Legal Project Documents

Asvs-step2.jpg2. Get Legal Project Documents

  • Contract Annex in English (Word, HTML)
  • Contract Annex in Spanish (HTML)
  • Verification schedule in English (Excel)
OWASP Books logo.png This project has produced a book that can be downloaded or purchased.
Feel free to browse the full catalog of available OWASP books.
Asvs-step3.jpg3. Learn About Legal Project Documents
  • Coming soon!


Glossary

Asvs-letters.jpgLegal Project Terminology

  • Coming soon!

Project Details

PROJECT INFO
What does this OWASP project offer you?
RELEASE(S) INFO
What does this OWASP project release offer you?
what is this project?
OWASP Legal Project

Purpose: The goal of the OWASP Legal Project is to ensure, at each stage of the life cycle, that appropriate attention has been paid to security. The cornerstone of the Legal Project is its Secure Software Development Contract Annex. The Contract Annex helps software developers and their clients negotiate and capture important contractual terms and conditions related to the security of the software to be developed or delivered.

License: N/A

who is working on this project?
Project Leader: Jeff Williams @

Project Maintainer:

Project Contributor(s): N/A

how can you learn more?
Project Pamphlet: N/A

3x slide Project Presentation: N/A

Mailing list: Subscribe or read the archives

Project Roadmap: To view, click here

Main links:

Project Health: Greenlight.pngGreenlight.pngGreenlight.png Level 3 Project (Provisional)
To be reviewed under Assessment Criteria v2.0

Key Contacts
  • Contact Jeff Williams @ to contribute, review or sponsor this project
  • Contact the GPC to report a problem or concern about this project or to update information.
current release
First Release - Unknown Date - (download)

Release Leader: N/A

Release details: Main links, release roadmap and assessment

Rating: Greenlight.pngGreenlight.pngGreenlight.png Stable Release
To be reviewed under Assessment Criteria v2.0


This project licensed under the Creative Commons Attribution ShareAlike 3.0.