Difference between revisions of "Category:OWASP Legal Project"

Jump to: navigation, search
Line 35: Line 35:
* 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 ([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])  
* Sample verification fee schedule template ([http://www.owasp.org/index.php/Image:Sample_ASVS_Fee_Schedule_Template.xls XLS])
* Sample verification fee schedule template ([http://www.owasp.org/index.php/Image:Sample_ASVS_Fee_Schedule_Template.xls Excel])
'''Related projects'''
'''Related projects'''

Revision as of 14:14, 8 June 2009


OWASP Documentation Project

Secure Software Development Contract Annex (Contract Annex)

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 contact us.

How the Contract Annex Works

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.

Latest News


More About the Contract Annex

  • One Page Datasheet (Word, PDF)
  • Sample verification fee schedule template (Excel)

Related projects


Contract Annex

Download the Contract Annex now, for free, here.

Other Versions

  • Contract Annex (HTML)

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 News


Project Leader

Project Contributors

Project Sponsorship

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 Jeff Williams Thanks for supporting OWASP!

This project licensed under the Licensed under Creative Commons Attribution ShareAlike 3.0.

Articles Below - More About the Contract Annex and Using It