OWASP Security Labeling System Project
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 different kinds of OWASP security labels for Web applications and Software( Please send your proposals):
* Ingredients criterion label (I). This label certifies that the software reveals all software components that integrate the software, or that were used to create it(eg. Shared libraries, APIs, and so on).
* Security 'good enough' criterion label (S). This would be the standard certification label. This label certifies that the software is 'good enough' because follows good security practices in its development life cycle, updates and security patches(Eg. OWASP Top Ten, the AVSV Security and verification standard, security control programming interfaces as OWASP ESAPIs).
* Legal 'good enough' criterion label (L). This is an additional label in case that the contract includes security software clauses following the OWASP principles.The OWASP legal principles would be based in the OWASP secure contract annex, and perhaps a soft law document containing relevant legal issues such as third party source code, Privacy, Data protection, and so forth.
* Disclosure of vulnerabilities criterion label (D). This label consists in the open disclosure of vulnerabilities of the software or Web Applications to the public.
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.
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.
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 official presentation will be ready very soon. But in the mean time you could check Jeff William's presentation from 2010: http://www.slideshare.net/DinisCruz/2010-11-owaspsoftwarelabels
News and Events
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
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 developers, e-commerce agents, IT security firms, Cyber communities, Internet rights NGOs, lawyers, and of course, users).
(2)Choose the sources of the security labeling system(which OWASP projects).
(3)Application of the labeling system. A platform in which developers can apply for the chosen label, a fast verification process, and to generate certificates (Of course, this methodology may change during the fist phases of the life cycle).
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:
- Help us to distribute the opinion polls.
- We might need a creative graphical designer for the logos.
| PROJECT INFO
What does this OWASP project offer you?
| RELEASE(S) INFO|
What releases are available for this project?