OWASP Security Labeling System Project

=Main=



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

OWASP Security Labeling System Project
The purpose of this project is creating a transnational and market wise software security labeling system. Security is invisible, so the OWASP labeling system will help to make it visible. The system consists on four kinds of OWASP security labels for Web applications and Software:

* Privacy label (P). This label certifies to the public that your software does not come with non-authorized spyware. Security is about TRUST, and there is not trust if software comes hacked by default. This label is obtained by adding the 'privacy clause' to your contracts or licenses.

* Openness label (O). This label consists about exposing to the public your web application vulnerabilities. The requirement to obtain this label is to expose your last vulnerability scans, and adding the 'openness clause' to your contracts or licenses.

* Security label (S). This is the standard security certification label. This label certifies that the software is 'good enough' because it follows good security practices in its development life cycle, updates and security patches following relevant security projects(such as OWASP Top Ten, OWASP security coding principles) and using relevant tools(such as Zed Attack Proxy, SAINT, Dependency Checker, and so on). This label is obtained by adding the 'security clause' to your contracts or licenses.

* Ingredients label (I). This label certifies that the software reveals all software components that integrate the software such as shared libraries, third party code, and so on. The requirement to obtain this label is to openly publish your software ingredients information, and adding the 'ingredients clause' declaration in your contracts or licenses.

Motivation
After joining the OWASP community in my local chapter, I got the idea of a security labeling system. When I contacted Jeff Williams I found out that he already proposed a very similar idea few years ago. We think we can revive it. The OWASP international community has the purpose of making security visible, and opinions from different sides are crucial in order to create a practical and widely used labeling system.

Licensing
The OWASP Security Labeling System Project is free to use. All documentation is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.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.


 * valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

What is OWASP Security Labeling System?
The goal is labeling the security of web applications and software, with the purpose of making security more visible. The OWASP Security Labeling System provides:


 * The Labeling linking logos.
 * The contract clauses model for the 4 labels: P(Privacy).O(Openness).S(Security).I(Ingredients).
 * A certificate of authenticity.

Presentation
http://www.slideshare.net/luisenriquezA/owasp-security-labeling-system-project

Project Leader
Luis Enriquez

Related Projects

 * OWASP_Legal_Project
 * OWASP_CISO_Survey


 * valign="top" style="padding-left:25px;width:200px;" |

News and Events

 * The project has begun. In this first phase we are shaping the labeling models. Please help us filling these OPINION POLLS:
 * USERS POLL: https://docs.google.com/a/owasp.org/forms/d/1A0aijN4dI2HPZOktnRx8bWebrXlwI1C5Zh0gGcjSczE/
 * DEVELOPERS POLL: https://docs.google.com/a/owasp.org/forms/d/1GNnve1SIxf8q5XGWZXJSmeSUzmKIEH5sQPQR3a-TTE8

Classifications

 * }

=FAQs=

 Why creating a security labeling system is important? Making security more visible. Is a transnational and market wise solution. Visual, and easy to apply. Different labeling categories for different purposes.

Which security labels can I add to my Software? Privacy label(P). Openness label(O). Security label(S). Ingredients label(I). What is the Privacy label(P) about? This label certifies that your software does not come with non-authorized spyware.

Why is the Privacy label relevant? Developers assume the legal compromise of not including hidden backdoors and surveillance code. The user would also have the obligation of checking the software hashsums. What is the Openness label(O) about? It is dedicated to high security environments. Web Applications will expose their vulnerabilities of the last vulnerability scan the public. They will have the time to patch them until the next vulnerabilities scan. The scans should be fixed in a regular basis(e.g. each week).

Why is the Openness label(O) relevant? Getting this label means that a security team reveals their vulnerabilities to the public as expected. but at the same time, it shows to the public how good and fast they are in order to fix them.

What is the Security label(S) about? It certifies that certain software follows a secure life cycle, recommended scan policies, secure coding practices, quick vulnerabilities patches, and is programmed and maintained by developers with a software security orientation.

Why is the Security label(S) relevant? Many software projects are already using OWASP guides and tools. A lot of them require developers to follow the OWASP secure coding principles. This label will make these security practices visible for users.

What is the Ingredients label(I) about? Is about exposing all the components of your software, such as API's, shared libraries, third party software.

Why is the Ingredients label(I) relevant? Because it will help developers and users to identify properly third party code, evaluate the risks of using it, avoid non intentional license compatibility controversies, and so forth.

= Acknowledgements =

Volunteers
The OWASP Security Labeling System is developed by a worldwide team of volunteers. The primary contributors to date have been:


 * Luis Enriquez
 * Jeff Williams
 * Jorge Lara

= Road Map and Getting Involved = The priorities of the OWASP Security Labeling System are:

(1)Create and Distribute opinion polls to different sides involved in the IT environment(such as software developers, e-commerce agents, IT security firms, Cyber communities, Internet rights NGOs, lawyers, and of course, users). This stage has already begun, and results are helping us to shape the model. (2)Create the most suitable methodology for the security labeling system. At this point seems that the best methodology is to create a clause(or declaration) for each label type, which will have to be included in IT contracts, or copyright licenses(additional terms for public licenses). The developer has the compromise of providing the OWASP labeling system conditions.

(3)Application of the labeling system. The OWASP labeling system volunteers will contribute to check that the system is working properly. If a Web application is not comitting their compromise, the label can be removed.

Involvement in the development and promotion of the OWASP Security Labeling System is actively encouraged! You do not have to be a security or legal expert in order to contribute. Some of the ways you can help:
 * Distribute the opinion polls.
 * Improve the system.
 * Translate the 'clauses' to other languages in a legal way.
 * Improve this wiki.

=Project About=