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
OWASP Security Labeling System Project
OWASP Security Labeling System ProjectThe 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.
MotivationAfter 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. LicensingThe 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:
PresentationLink to presentation
Project LeaderLuis Enriquez
Related Projects
|
News and EventsIn PrintThis project can be purchased as a print on demand book from Lulu.com
Classifications
|
- Q1
- A1
- Q2
- A2
Volunteers
XXX is developed by a worldwide team of volunteers. The primary contributors to date have been:
- xxx
- xxx
Others
- xxx
- xxx
As of XXX, the priorities are:
- xxx
- xxx
- xxx
Involvement in the development and promotion of XXX is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:
- xxx
- xxx
PROJECT INFO What does this OWASP project offer you? |
RELEASE(S) INFO What releases are available for this project? | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|