Difference between revisions of "Category:OWASP Legal Project"

From OWASP
Jump to: navigation, search
 
(20 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
+
= Home =
{{ProjectTabs |
+
Proj_About=  
+
[[Image:Legal-bannerbug.JPG|300px|right]]
+
'''Why is a legal project relevant?'''
+
  
The OWASP Legal Project's '''Secure Software Development Contract Annex (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. Most contracts are silent on these issues, and the parties frequently have dramatically different views on what has actually been agreed to. Clearly articulating these terms is the best way to ensure that both parties can make informed decisions about how to proceed. The goal of the Contract Annex is simply to ensure, at each stage of the life cycle, that appropriate attention has been paid to security. An additional benefit is that this documentation can be collected together to form a "certification package" that essentially lays out the argument for why this software should be trusted to do what it claims it does. There are currently versions in English.<br><br>
+
{| width="100%"
 
+
|-
'''What are some examples of how the contract annex can be used?'''
+
! width="66%" |
 
+
! width="33%" |
Here are two examples:
+
|- 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:
  
 
* '''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.
 
* '''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.
 
* '''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.
<br>
+
|
 +
[[Image:Esapi-sponsors.PNG]]
  
'''What's new?'''
+
|}
 
+
* [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
+
  
 +
{| width="100%"
 +
|-
 +
! width="33%" |
 +
! width="33%" |
 +
! width="33%" |
 +
|- valign="top"
 +
|
 +
== Let's talk here  ==
  
 +
[[Image:Asvs-bulb.jpg]]'''Legal 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 [mailto:jeff.williams@owasp.org contact us].
  
 +
*[https://lists.owasp.org/mailman/listinfo/owasp-legal owasp-legal mailing list (this is the main list)]
  
 
|  
 
|  
 +
== Got translation cycles?  ==
  
Proj_Documentation=
+
[[Image:Asvs-writing.JPG]]'''Legal Project Translations'''
<br>
+
{{OWASP Book|4037498}}
+
<br>
+
<br>'''More About the Contract Annex'''
+
<br>
+
[[Image:Legal-handout.JPG|thumb|90px|left|Handout]]
+
* 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])
+
  
 +
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 ==
  
+
[[Image:Asvs-satellite.jpg]]'''OWASP Resources'''
+
  
+
* [[Top Ten|OWASP Top Ten]]
 +
* [[ASVS|OWASP Application Security Verification Standard]]
 +
* [[:Category:OWASP_Enterprise_Security_API|OWASP ESAPI]]
 +
* [[:Category:OWASP_Newsletter#tab=Press_releases|OWASP Press Releases]]
 +
|}
  
+
= Downloads =
+
+
'''Related projects'''
+
  
[[Image:Owasp-projects-page.jpg|thumb|110px|left|Projects Page]]
+
{| width="100%"
* [http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project OWASP Top Ten]
+
|-
* [http://www.owasp.org/index.php/Category:OWASP_Application_Security_Verification_Standard_Project OWASP ASVS Project]
+
! width="33%" |  
* [http://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API OWASP ESAPI]
+
! width="33%" |  
 +
|- valign="top"
 +
|  
 +
[[Image:Asvs-step1.jpg]]'''1. About Legal Project Documents'''
  
+
* 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])
 +
* One Page Datasheet in Japanese ([https://www.owasp.org/index.php/File:Legal_One_Page_Handout-ja.pdf PDF])
  
+
[[Image:Asvs-step2.jpg]]'''2. Get Legal Project Documents'''
+
  
<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])
====Contract Annex====
+
* Contract Annex in Spanish ([http://www.owasp.org/index.php/Anexo_para_Contrato_de_Software_Seguro_de_OWASP HTML])
'''OWASP Contract Annex - Release (This is the current official release version)'''
+
* Contract Annex in Japanese ([https://www.owasp.org/index.php/OWASP_Secure_Software_Contract_Annex/ja HTML])
<br>
+
* Contract Annex in French ([https://www.owasp.org/index.php/File:OWASP_Secure_Software_Contract_Annex-FR.doc Word])
[[Image:Legal-book.JPG|thumb|90px|left|Release]]
+
* Verification schedule in English ([http://www.owasp.org/index.php/Image:Sample_ASVS_Fee_Schedule_Template.xls Excel])
Download free:
+
  
'''OWASP Contract Annex - Release'''
+
{{OWASP Book|4037498}}
  
* [[Image:OWASP Secure Software Contract Annex.doc]]
+
|}
<br><br><br><br><br>
+
 
+
 
+
 
+
 
+
   
+
 
+
 
+
+
  
|
+
<br>
  
Proj_Mail= '''Project News'''
+
= Project Details =
 
+
{{:GPC_Project_Details/OWASP_Legal_Project | OWASP Project Identification Tab}}
* 03/20/2009 - OWASP Contract Annex updated to support the use of [http://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API OWASP Enterprise Security API (ESAPI)].
+
* 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].
+
 
+
<br>'''Mailing List'''<br>[https://lists.owasp.org/mailman/listinfo/owasp-legal Subscribe here]<br>[mailto:owasp-legal(at)lists.owasp.org Use here]
+
  |
+
 
+
Proj_Related= [[Top Ten|OWASP Top Ten]] |
+
 
+
Proj_Contributors= '''Project Leader'''<br>[[:User:Jeff Williams|Jeff Williams]]<br><br>'''Project Contributors'''<br>[http://www.owasp.org/index.php/User:Mike.boberski Mike Boberski]
+
 
+
 
+
'''The OWASP Legal project is sponsored by:'''
+
 
+
[[Image:Aspect logo.jpg]]
+
 
+
 
+
'''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 [[:User:Jeff Williams|Jeff Williams]] Thanks for supporting OWASP!
+
}}
+
''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>

Latest revision as of 21:55, 16 June 2013

[edit]

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

Asvs-step1.jpg1. About Legal Project Documents

  • One Page Datasheet (Word, PDF)
  • One Page Datasheet in Japanese (PDF)

Asvs-step2.jpg2. Get Legal Project Documents

  • Contract Annex in English (Word, HTML)
  • Contract Annex in Spanish (HTML)
  • Contract Annex in Japanese (HTML)
  • Contract Annex in French (Word)
  • 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.


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.