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

Difference between revisions of "Category:OWASP Legal Project"

Jump to: navigation, search
Line 69: Line 69:
'''OWASP Contract Annex - Release'''
'''OWASP Contract Annex - Release'''
* [[Image:OWASP Secure Software Contract Annex.doc]]
<br>You can view the content in the wiki at [[OWASP_Secure_Software_Contract_Annex]]
'''Wiki Version'''
* [[OWASP_Secure_Software_Contract_Annex]]
* [[Image:OWASP Secure Software Contract Annex.doc]]

Revision as of 19:22, 19 April 2009



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.

What are some examples of how the contract annex can be used?

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.

What's new?


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.

You can view the content in the wiki at OWASP_Secure_Software_Contract_Annex

More About the Contract Annex


Related projects

Projects Page

Contract Annex

OWASP Contract Annex - Release (This is the current official release version)


Download free:

OWASP Contract Annex - Release

Wiki Version


Project News

Mailing List
Subscribe here
Use here


Project Leader
Jeff Williams

Project Contributors
Mike Boberski

The OWASP Legal project is sponsored by:

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