This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Category:OWASP Legal Project"

From OWASP
Jump to: navigation, search
 
(35 intermediate revisions by 8 users not shown)
Line 1: Line 1:
<br>
+
= Home =
{{OWASP Book|4037498}}
+
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]] </div>
<br>
+
{| width="100%"
{{:Project Information:template OWASP Legal Project}}
+
|-
[[Category:OWASP Project]]
+
! width="66%" |
[[Category:OWASP Document]]
+
! width="33%" |
[[Category:OWASP Download]]
+
|- valign="top"
[[Category:OWASP Release Quality Document]]
+
|
 +
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.
  
==Overview==
+
* '''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]]
  
[[Image:Legal-book.JPG|thumb|300px|right|OWASP Contract Annex Book]]
+
|}
The OWASP Legal project provides materials related to the legal aspects of secure software, including contracting, liability, and compliance. This project should not be considered legal advice, and we strongly recommend that you find competent counsel to assist with your contract negotiations. Project materials have been place in the public domain to facilitate use in private contracts.
 
  
 +
{| width="100%"
 +
|-
 +
! width="33%" |
 +
! width="33%" |
 +
! width="33%" |
 +
|- valign="top"
 +
|
 +
== Let's talk here  ==
  
The OWASP Legal project's Secure Software Development Contract Annex (Contract Annex) is guidance that you should take with you when you talk to a qualified attorney to negotiate and capture important contractual terms and conditions related to the security of the software to be developed or delivered. It is a starting point for your agreement. You may not like all the activities, or may want to propose more. You may want to assign responsibilities differently. It is not intended to exactly capture the needs of all software Clients and Developers. The Contract Annex is intended to provide a framework for discussing the key topics that are important to ensuring that software ends up secure. After you have a security discussion and reach agreement, you should tailor this agreement to match.
+
[[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:[email protected] contact us].
  
Read about our plans in the [[OWASP Legal Project Roadmap]]. More details about the Contract Annex are below.
+
*[https://lists.owasp.org/mailman/listinfo/owasp-legal owasp-legal mailing list (this is the main list)]
  
 +
|
 +
== Got translation cycles?  ==
  
==OWASP Secure Software Contract Annex==
+
[[Image:Asvs-writing.JPG]]'''Legal Project Translations'''
  
There are many benefits to working through the OWASP Secure Software Development Contract Annex. The principal one is that it will make expectations clear between the parties involved. In some cases it will help to prevent lawsuits when difficult security problems surface in the software. Also, these are the same activities that are required by many legal and regulatory compliance reasons.
+
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!
  
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.
+
|
 +
== Related resources ==
  
 +
[[Image:Asvs-satellite.jpg]]'''OWASP Resources'''
  
* [[OWASP Secure Software Contract Annex]]
+
* [[Top Ten|OWASP Top Ten]]
* [[Secure software contracting hypothetical case study]]
+
* [[ASVS|OWASP Application Security Verification Standard]]
 +
* [[:Category:OWASP_Enterprise_Security_API|OWASP ESAPI]]
 +
* [[:Category:OWASP_Newsletter#tab=Press_releases|OWASP Press Releases]]
 +
|}
  
 +
= Downloads =
  
You can download the Microsoft Word version [[Image:OWASP Secure Software Contract Annex.doc]] and modify it to suit your needs. Please consider contributing back any enhancements you make.
+
{| width="100%"
 +
|-
 +
! width="33%" |
 +
! width="33%" |
 +
|- valign="top"
 +
|
 +
[[Image:Asvs-step1.jpg]]'''1. About Legal Project Documents'''
  
==Feedback and Participation==
+
* 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])
  
We hope you find the OWASP Secure Software Contract Annex useful. Please contribute back to the project by sending your comments, questions, and suggestions to [email protected]. To join the OWASP Legal mailing list or view the archives, please visit the [http://lists.owasp.org/mailman/listinfo/owasp-legal subscription page.]
+
[[Image:Asvs-step2.jpg]]'''2. Get Legal Project Documents'''
  
==Project Contributors==
+
* 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 in Spanish ([http://www.owasp.org/index.php/Anexo_para_Contrato_de_Software_Seguro_de_OWASP HTML])
 +
* Contract Annex in Japanese ([https://www.owasp.org/index.php/OWASP_Secure_Software_Contract_Annex/ja HTML])
 +
* Contract Annex in French ([https://www.owasp.org/index.php/File:OWASP_Secure_Software_Contract_Annex-FR.doc Word])
 +
* Verification schedule in English ([http://www.owasp.org/index.php/Image:Sample_ASVS_Fee_Schedule_Template.xls Excel])
  
The Legal project lead is Jeff Williams of Aspect Security. He can be reached at jeff.williams 'at' owasp.org.
+
{{OWASP Book|4037498}}
  
==Project Sponsors==
+
|}
  
The OWASP Legal project is sponsored by
+
<br>
[http://www.aspectsecurity.com https://www.owasp.org/images/d/d1/Aspect_logo.gif]
 
  
==Articles - More About The Legal Project and Using The Contract Annex==
+
= Project Details  =
 +
{{:GPC_Project_Details/OWASP_Legal_Project | OWASP Project Identification Tab}}
  
[[Category:OWASP Document]]
+
__NOTOC__ <headertabs /> ''This project licensed under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution ShareAlike 3.0].'' <br>
[[Category:Planning]]
+
[[Category:SAMM-SR-3]]
[[Category:Requirements]]
 
[[Category:OWASP Project]]
 
[[Category:OWASP Download]]
 
[[Category:OWASP Release Quality Document]]
 

Latest revision as of 05:36, 22 April 2015

OWASP Inactive Banner.jpg

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.