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
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
= Home =
 
= Home =
 
+
<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>
 
{| width="100%"
 
{| width="100%"
 
|-
 
|-
Line 83: Line 83:
  
 
__NOTOC__ <headertabs /> ''This project licensed under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution ShareAlike 3.0].'' <br>
 
__NOTOC__ <headertabs /> ''This project licensed under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution ShareAlike 3.0].'' <br>
 +
[[Category:SAMM-SR-3]]

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

This project licensed under the Creative Commons Attribution ShareAlike 3.0.