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"
(Add * Contract Annex in Japanese.) |
|||
| Line 1: | Line 1: | ||
| − | + | = Home = | |
{| width="100%" | {| width="100%" | ||
| Line 10: | Line 10: | ||
* '''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. | ||
| | | | ||
| Line 47: | Line 48: | ||
* [[Top Ten|OWASP Top Ten]] | * [[Top Ten|OWASP Top Ten]] | ||
* [[ASVS|OWASP Application Security Verification Standard]] | * [[ASVS|OWASP Application Security Verification Standard]] | ||
| − | *[ | + | * [[:Category:OWASP_Enterprise_Security_API|OWASP ESAPI]] |
| − | *[ | + | * [[:Category:OWASP_Newsletter#tab=Press_releases|OWASP Press Releases]] |
|} | |} | ||
| − | + | = Downloads = | |
{| width="100%" | {| width="100%" | ||
| Line 72: | Line 73: | ||
{{OWASP Book|4037498}} | {{OWASP Book|4037498}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
| − | <br> | + | <br> |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | = Project Details = | |
{{:GPC_Project_Details/OWASP_Legal_Project | OWASP Project Identification Tab}} | {{:GPC_Project_Details/OWASP_Legal_Project | OWASP Project Identification Tab}} | ||
__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> | ||
Revision as of 16:10, 18 January 2012
|
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:
|
|
Let's talk here
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?
The Legal Project project is always on the lookout for volunteers who are interested in translating Legal Project documents into another language.
|
Related resources
|
|
|
| PROJECT INFO What does this OWASP project offer you? |
RELEASE(S) INFO What does this OWASP project release offer you? | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| ||||||||||||||||||||||
Pages in category "OWASP Legal Project"
The following 15 pages are in this category, out of 15 total.
