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 "OWASP Software Component Verification Standard"
Hblankenship (talk | contribs) (Created page with "<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</div> {| style="padding: 0;margin:0;margin-top:10px;text-alig...") |
m (incubating docs) |
||
| Line 1: | Line 1: | ||
| + | =Main= | ||
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | ||
| Line 4: | Line 5: | ||
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | ||
| − | |||
| − | |||
| − | |||
==Project About== | ==Project About== | ||
<span style="color:#ff0000"> | <span style="color:#ff0000"> | ||
| Line 13: | Line 11: | ||
|leader_name1=Steve Springett | |leader_name1=Steve Springett | ||
| + | |project_license=Creative Commons Attribution ShareAlike 3.0 License | ||
}} | }} | ||
| + | |||
| Line 43: | Line 43: | ||
==Roadmap== | ==Roadmap== | ||
<span style="color:#ff0000"> | <span style="color:#ff0000"> | ||
| − | As of | + | As of August, 2019, the highest priority is to get a usable rough draft which can be iterated on by December 31, 2019. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Getting Involved== | ==Getting Involved== | ||
| Line 67: | Line 55: | ||
== Project Resources == | == Project Resources == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | [https://github.com/ | + | [https://github.com/OWASP/Software-Component-Verification-Standard GitHub Repository] |
| − | |||
| − | |||
| − | |||
| − | |||
== Project Leader == | == Project Leader == | ||
| − | |||
| − | |||
| − | |||
[mailto://[email protected] Steve Springett] | [mailto://[email protected] Steve Springett] | ||
Revision as of 19:35, 28 August 2019
Main
Project About
OWASP Documentation Project TemplateThis section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for. The OWASP Documentation Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects. By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for. And it's easy to get started by simply creating a new project from the appropriate project template. DescriptionThis is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful. The Documentation Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Documentation project. After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red. Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category. The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort. Creating a new set of project pages from scratch can be a challenging task. By providing a sample layout, with instructional text and examples, the OWASP Documentation Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security. Contextual custom dictionary builder with character substitution and word variations for pen-testers LicensingA project must be licensed under a community friendly or open source license. For more information on OWASP recommended licenses, please see OWASP Licenses. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects. This example assumes that you want to use the AGPL 3.0 license. This program is free software: you can redistribute it and/or modify it under the terms of the link GNU Affero General Public License 3.0 as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright © by {the Project Leader(s) or OWASP} {Year(s)}. RoadmapAs of August, 2019, the highest priority is to get a usable rough draft which can be iterated on by December 31, 2019.
Getting InvolvedInvolvement in the development and promotion of Documentation Project Template is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows: |
Project ResourcesProject LeaderRelated ProjectsThis is where you can link to other OWASP Projects that are similar to yours. Classifications
| ||||||||||||||||||||||||||||||||||||||||||||||
