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"

From OWASP
Jump to: navigation, search
m (incubating docs)
m (incubating docs)
 
(5 intermediate revisions by the same user not shown)
Line 3: Line 3:
  
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
−
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
+
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
  
−
==Project About==
 
−
<span style="color:#ff0000">
 
−
{{:Template:Project About
 
−
  |project_name=Software Component Verification Standard
 
−
  |leader_name1=Steve Springett
 
− 
−
  |project_license=Creative Commons Attribution ShareAlike 3.0 License
 
−
}}
 
  
−
 
+
==OWASP Software Component Verification Standard==
−
 
+
This project is currently incubating... Stay tuned.
−
==OWASP Documentation Project Template==
 
−
<span style="color:#ff0000">
 
−
This 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.
 
−
</span>
 
−
 
 
−
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.
 
−
 
 
−
==Description==
 
−
<span style="color:#ff0000">
 
−
This 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.
 
−
</span>
 
−
 
 
−
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
 
  
 
==Licensing==
 
==Licensing==
−
<span style="color:#ff0000">
+
The guide is licensed under the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
−
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses 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.
 
−
</span>
 
−
 
 
−
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html 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 &copy; by {the Project Leader(s) or OWASP} {Year(s)}. 
 
−
 
 
−
==Roadmap==
 
−
<span style="color:#ff0000">
 
−
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==
 
−
<span style="color:#ff0000">
 
−
Involvement in the development and promotion of <strong>Documentation Project Template</strong> 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:
 
  
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
  
−
== Project Resources ==
+
==Project Resources==
  
−
[https://github.com/OWASP/Software-Component-Verification-Standard GitHub Repository]
+
* [https://github.com/OWASP/Software-Component-Verification-Standard GitHub Repository]
 +
* [https://owasp.slack.com/channels/project-scvs Slack Channel]
  
−
== Project Leader ==
+
==Project Leader==
  
−
[mailto://[email protected] Steve Springett]
+
[[User:Steve_Springett|Steve Springett]]
  
 
== Related Projects ==
 
== Related Projects ==
−
<span style="color:#ff0000">
+
* [[Component Analysis|Supply Chain Component Analysis]]
−
This is where you can link to other OWASP Projects that are similar to yours.
+
* [[OWASP Dependency Check|Dependency-Check]]
−
</span>
+
* [[OWASP Dependency Track Project|Dependency-Track]]  
−
* [[OWASP_Code_Project_Template]]
 
−
* [[OWASP_Tool_Project_Template]]
 
  
 
==Classifications==
 
==Classifications==
Line 84: Line 43:
 
|}
 
|}
 
   
 
   
 +
=Roadmap=
 +
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=
 +
Involvement in the development and promotion of <strong>OWASP SCVS</strong> 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:
 +
* Supply chain risk identification
 +
* Documentation
 +
* Strategy
 +
* Messaging
 +
 +
 +
=Project About=
 +
<span style="color:#ff0000">
 +
{{:Template:Project About
 +
  |project_name=Software Component Verification Standard
 +
  |project_description=
 +
  |leader_name1=Steve Springett
 +
  |leader_username1=Steve_Springett
 +
 +
  |project_license=Creative Commons Attribution ShareAlike 3.0 License
 +
  | links_url1 = https://github.com/OWASP/Software-Component-Verification-Standard
 +
  | links_name1 = GitHub Repository
 +
}}
 +
 
__NOTOC__ <headertabs />  
 
__NOTOC__ <headertabs />  
  
 
[[Category:OWASP Project]] [[Category:OWASP_Document]]
 
[[Category:OWASP Project]] [[Category:OWASP_Document]]

Latest revision as of 23:00, 28 August 2019

OWASP Project Header.jpg


OWASP Software Component Verification Standard

This project is currently incubating... Stay tuned.

Licensing

The guide is licensed under the Creative Commons Attribution-ShareAlike 4.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.

Project Resources

Project Leader

Steve Springett

Related Projects

Classifications

Project Type Files DOC.jpg
Incubator Project Owasp-builders-small.png
Owasp-defenders-small.png
Creative Commons Attribution ShareAlike 3.0 License

As of August, 2019, the highest priority is to get a usable rough draft which can be iterated on by December 31, 2019.

Involvement in the development and promotion of OWASP SCVS 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:

  • Supply chain risk identification
  • Documentation
  • Strategy
  • Messaging


PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: Software Component Verification Standard
Purpose: N/A
License: Creative Commons Attribution ShareAlike 3.0 License
who is working on this project?
Project Leader(s):
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Main links:
Key Contacts
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Software_Component_Verification_Standard&oldid=254302"