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 Security Labeling System Project"

From OWASP
Jump to: navigation, search
 
(24 intermediate revisions by 2 users not shown)
Line 5: Line 5:
  
 
{| 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;" |
+
| style="border-right: 1px dotted gray;padding-right:25px;" valign="top" |
  
 
== PURPOSE ==
 
== PURPOSE ==
Line 12: Line 12:
  
 
== WHAT IS IT?==
 
== WHAT IS IT?==
−
It is system of security labels for web applications and software(in general). It can be used for any distributed software (when the user install in his device), or in web applications where the user connects to a server(as in cloud services).
+
:It is system of security labels for web applications.
  
 
== HOW DOES IT WORK?==
 
== HOW DOES IT WORK?==
−
The labeling system is classified by 4 labels:
+
:There are 4 labels:
  
−
'''* Security(S).'''  Security starts with SECURE CODING, and secure maintenance. This badge is for Software developed with a secure life cycle, following recommended security coding practices(OWASP TOP TEN, OWASP security principles...) and recommended security tools(Zed Attack Proxy, SAINT, Dependency check...)
+
'''* Security (S).'''  Security starts with SECURE CODING, and secure maintenance. This label is based on the OWASP Application Security Verification Standard(ASVS). Web applications will get a rating based on the Applications Security Verification levels on the AVSV standard(cursory, standard, opportunistic, and advanced).
  
−
'''* Privacy(P).'''  Security is also about TRUST. Technical security is not relevant if Software comes with hidden non-authorized backdoors, or surveillance code by default. This Privacy badge is for Software free of non-authorized spyware, and web applications following ethical principles of data protection.
+
'''* Privacy (P).'''  Security is also about TRUST. Technical security is not relevant if Software comes with hidden backdoors, and non-transparent policies. This label will require a Privacy scanning policy that may be based on the OWASP Top Ten Privacy project. Web applications must follow ethical principles of data processing and data protection.  
  
−
'''* Ingredients(I).'''  Security is also about TRANSPARENCY. This condition is possible through the use of Open Source Software. Contemporary Software is built(and linked) by many components such as shared libraries, third party code, APIS, and so on. This label consists on Software exposing their components and third party code.
+
'''* Ingredients (I).'''  Security is also about TRANSPARENCY. This condition is only possible through the use of Open Source Software. Contemporary Software is built(and linked) by many components such as shared libraries, APIs, and so on. This label is about Web Applications exposing all their ingredients, including third party code and dependencies.
  
−
'''* Openness(O).'''  Security might also be OPEN. Open security means having a fast and reliable IT security team. This openness label consists on exposing the Software or Web Application last vulnerability reports to the public.
+
'''* Openness (O).'''  Security might also be OPEN. Open security means having a fast and reliable IT security team. This label consists on a scanning policy based on the OWASP Top Ten project, and making the scan visible.  
  
 +
| style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" |
  
−
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
+
== IMPLEMENTATION==
  
−
== IMPLEMENTATION==
+
Due to the complexity of the tasks, the Labels will be implemented 1 by 1. The first Label to be implemented is the OPENNESS LABEL. We will start with this experimental implementation in June - 2015. In the mean time we need open security promoters, to get submitted into the project's records.
  
 
The System provides 4 logos and 4 clauses(1 for each label). The clauses can be added before the copyright public licenses as a "license exception", or included in the warranty clause(or any other) in custom copyright licenses, license contracts, terms of services, or even privacy policies.
 
The System provides 4 logos and 4 clauses(1 for each label). The clauses can be added before the copyright public licenses as a "license exception", or included in the warranty clause(or any other) in custom copyright licenses, license contracts, terms of services, or even privacy policies.
  
−
STEP 1: Get Registered in the OWASP Security Labeling system Site.
+
STEP 1: Get Registered into the OWASP Security Labeling system Site.
  
 
STEP 2: Download the label-logo(s) and paste before your copyright license, license contract, terms of service, or privacy policy.
 
STEP 2: Download the label-logo(s) and paste before your copyright license, license contract, terms of service, or privacy policy.
  
−
STEP 3: Incorporate the correspondent label-clause(s) into your copyright license, license contract,terms of service,or privacy policy.
+
STEP 3: Incorporate the correspondent label-clause(s) in a visible place within your Web application, copyright license, license contract,terms of service,or privacy policy.
  
 
== COMPROMISES ==
 
== COMPROMISES ==
−
- Between DEVELOPER and the OWASP SECURITY LABELING PROJECT. By including the Labeling-logos, the Developer gets the compromise of following the OWASP labeling requirements.  
+
- Between DEVELOPER and the OWASP SECURITY LABELING PROJECT. By including the Labeling-logos, the Developer gets the compromise of following the OWASP labeling system requirements.  
  
−
- Between DEVELOPER and USERS. By incorporating the Labeling-Clauses, the Developer assumes a direct compromise with their software users. This compromise has a legal value as it is incorporated into the contract.
+
- Between DEVELOPER and USERS. By incorporating the Labeling-Clauses, Web service providers assume a direct compromise with their users.  
  
 
- Between OWASP SECURITY LABELING PROJECT and USERS. Users can report violations of the labeling system to the OWASP labeling project Volunteers.   
 
- Between OWASP SECURITY LABELING PROJECT and USERS. Users can report violations of the labeling system to the OWASP labeling project Volunteers.   
Line 47: Line 48:
 
== PRESENTATION ==
 
== PRESENTATION ==
  
 +
http://owaspsecuritylabelingsystem.blogspot.com/
 
http://www.slideshare.net/luisenriquezA/owaspsecuritylabelingsystem
 
http://www.slideshare.net/luisenriquezA/owaspsecuritylabelingsystem
  
Line 53: Line 55:
 
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.
 
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.
  
−
 
+
| style="padding-left:25px;width:200px;" valign="top" |  
−
| valign="top"  style="padding-left:25px;width:200px;" |  
 
−
 
 
  
 
== NEWS AND EVENTS ==
 
== NEWS AND EVENTS ==
−
* The proposal of this project is READY. Time for Opinions and Corrections.
+
* The proposal of this project has been relaunched. We are examining with a new team the possibilities of a joint venture for complying the new legal regulations such as GDPR in the summer of 2019.
  
 +
'''YOU ARE ALL INVITED TO JOIN THIS SECURITY PROJECT'''.
  
 
== PROJECT LEADER ==
 
== PROJECT LEADER ==
Line 78: Line 79:
 
   {| width="200" cellpadding="2"
 
   {| width="200" cellpadding="2"
 
   |-
 
   |-
−
   | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
+
   | rowspan="2" width="50%" valign="top" align="center" | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
−
   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]   
+
   | width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=]]   
 
   |-
 
   |-
−
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
+
   | width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=]]
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
+
   | colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
+
   | colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
 
   |}
 
   |}
  
Line 91: Line 92:
  
 
= Labeling clauses =
 
= Labeling clauses =
−
''/*Add these clauses into your license contracts, terms of services or privacy policy(for the privacy label). If your software is licensed under the terms of a generic purpose FOSS public license(such as the GPL license, the Apache license, the Mozilla license, and so on...),you might add these clauses before the license terms as a license exception, or as additional terms.*/''  
+
''/*Add these clauses on your web applications in a visible place. You could also add them into your license contracts, terms of services or privacy policies. If your software is licensed under the terms of a generic-purpose FOSS public license(such as the GPL license, the Apache license, the Mozilla license, and so on...),you might add these clauses before the license terms as a license exception, or as additional terms.*/''  
  
  
Line 97: Line 98:
  
  
−
OWASP SECURITY LABELING SYSTEM. This Software has been labeled under the OWASP security labeling system with the purpose of making security VISIBLE for everybody. THIS LEGAL COMPROMISE IS BETWEEN THE ADMINISTRATOR or LEGAL REPRESENTATIVE OF THIS SOFTWARE, AND THE END USER.
+
OWASP SECURITY LABELING SYSTEM. This Web Application is labeled under the OWASP security labeling system with the purpose of making security VISIBLE for everybody. THIS IS A SECURITY COMPROMISE BETWEEN THE ADMINISTRATOR of this Web Application, and the end users. This system is only based on trust and reputation. OWASP denies any liability, or damage claims of any kind.
  
 
==Security Label==
 
==Security Label==
Line 103: Line 104:
 
[[File:Owasp-security-scaled.png]]
 
[[File:Owasp-security-scaled.png]]
  
−
SECURITY LABEL CLAUSE: Security is about secure coding. This software has been developed and is maintained following the highest secure coding practices. A list of all the security guides and tools used by the developers of this software must be included or linked through this notice.
+
SECURITY LABEL CLAUSE: Security starts with secure coding and mantainance. This Web application is following the security guidelines of the OWASP Application Security Verification Standard. Reports can be downloaded "here".
  
  
Line 109: Line 110:
 
[[File:Privacy-scaled.png]]
 
[[File:Privacy-scaled.png]]
  
−
PRIVACY LABEL CLAUSE: Security is about Trust. This Software comes free of non authorized spy-ware or surveillance code of any kind. The administrator,legal representer, or person in charge of this software will not sale, commercialize, or miss-use user's personal data without the user's permission.
+
PRIVACY LABEL CLAUSE: Security is about Trust. This Web application uses a scan policy based on the OWASP top ten Privacy project. Reports can be downloaded here.
−
 
 
  
  
Line 116: Line 116:
 
[[File:Owasp-ingredients-scaled.png]]
 
[[File:Owasp-ingredients-scaled.png]]
  
−
INGREDIENTS LABEL CLAUSE: Security is about Transparency. This software discloses a list of all its software components in a human readable file, including source code, plug-ins, shared libraries, and third party code. This compromise is only effective is the provider distributes a list of all components within the packet, and a link to access the source code.
+
INGREDIENTS LABEL CLAUSE: Security is about Transparency. This Web application  discloses a list of all its components and third party code, including source code, plug-ins, shared libraries. Reports can be downloaded here.
  
 
==Openness Label ==
 
==Openness Label ==
 
[[File:Openness-scaled.png]]
 
[[File:Openness-scaled.png]]
  
−
OPENNESS LABEL CLAUSE: Security is about Transparency. This Web application makes available its latest vulnerability reports to the public. The report or a link to the report must be clearly published in this Web application. This compromise is only effective if the vulnerability report's date is not older than 1 week.
+
OPENNESS LABEL CLAUSE: Security is about Transparency. This Web application is regularly scanned by a policy based on the OWASP top ten project. Reports can be downloaded here.
  
−
THIS COMPROMISE IS ONLY VALID AS LONG AS THIS SOFTWARE'S VERSION IS REGISTERED INTO THE OWASP SECURITY LABELING SYSTEM RECORDS.
 
−
----
 
  
 +
THIS COMPROMISE IS VALID AS LONG AS THE WEB APPLICATION IS REGISTERED INTO THE OWASP SECURITY LABELING SYSTEM RECORDS.
  
−
IF THE SOFTWARE COMES AS SOURCE CODE OR BINARIES, PLEASE ADD THIS CLAUSE:
 
−
 
−
The user must download this software from trusted sources, verify the correspondent hash-sum of the packets, and maintain the software with the recommended security updates and patches.
 
−
 
−
----
 
−
Please visit the DEMO page for a guide on how to apply this system to your computer programs distribution, or web applications.
 
  
 
=FAQs=
 
=FAQs=
  
 
''' Why creating a security labeling system is important?'''
 
''' Why creating a security labeling system is important?'''
−
Making security more visible.
+
: Making security more visible.
−
Is a transnational and market wise solution.  
+
: Is a transnational and market wise solution.  
−
Visual, and easy to apply.  
+
: It is based on trust and reputation.
−
Different labeling categories for different purposes.
+
: Visual, and easy to apply.  
 +
: Different labeling categories for different purposes.
  
−
'''Which security labels can I add to my Software?'''
+
'''Which security labels can I add to my Software?'''
−
'''S'''ecurity label(S).   
+
: '''S'''ecurity label (S).   
−
'''P'''rivacy label(P).  
+
: '''P'''rivacy label (P).  
−
'''I'''ngredients label(I).
+
: '''I'''ngredients label (I).
−
'''O'''penness label(O).
+
: '''O'''penness label (O).  
−
 
−
 
−
'''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?'''
+
'''What is the Security label (S) about?'''
−
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.
+
: Web Applications must be developed and maintained with a security orientation.  
  
−
'''What is the Privacy label(P) about?'''
+
'''Why is the Security label (S) relevant?'''
−
This label certifies that your software does not come with non-authorized spyware, and that your personal data will be respected.
+
: Users have the right to know if web applications are secure enough. This is the main purpose of OWASP. Currently we propose using the AVSV standard as it provides a basis for testing web application technical security controls.  
  
−
'''Why is the Privacy label relevant?'''
+
'''What is the Privacy label (P) about?'''
−
Developers assume the legal compromise of not including hidden backdoors and surveillance code.
+
: Surveillance code, misuse of personal data, and non-transparent policies are as dangerous as code vulnerabilities.
−
The user would also have the obligation of checking the software hashsums.
 
  
−
'''What is the Ingredients label(I) about?'''
+
'''Why is the Privacy label relevant?'''
−
  Is about exposing all the components of your software, such as API's, shared libraries, third party software.
+
: Users have the right to know how their information is processed and stored. We propose developing a privacy scan policy based on the OWASP Top Ten Privacy Project.
  
−
'''Why is the Ingredients label(I) relevant?'''
+
'''What is the Ingredients label (I) about?'''
−
Because it will help developers and users to identify properly third party code, evaluate the risks of using it,  
+
: Is about exposing all the components of your software, such as API's, and shared libraries.
−
avoid non intentional license compatibility controversies, and so forth.
 
  
−
+
'''Why is the Ingredients label (I) relevant?'''
−
'''What is the Openness label(O) about?'''
+
: Because it will help developers and users to identify properly third party code, evaluate the risks of using it,
−
It is dedicated to high security environments. Web Applications will expose their vulnerabilities of the
+
: avoid non intentional license compatibility controversies, and so forth.
−
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?'''
+
'''What is the Openness label (O) about?'''
−
+
: It is dedicated to rate security. Web Applications will expose their vulnerabilities of the
−
Getting this label means that a security team reveals their vulnerabilities to the public as expected.  
+
: last vulnerability scan the public. They will have the time to patch them until the next vulnerabilities scan.
−
but at the same time, it shows to the public how good and fast they are in order to fix them.  
+
: The scans should be fixed in a regular basis(e.g. each week).
  
 +
'''Why is the Openness label (O) relevant?'''
 +
: Vulnerabilities such as XSS scripting and SQL injection must be efficiently fixed.
 +
: Scan policies must be based on the OWASP Top ten Project.
  
 
= Acknowledgements =
 
= Acknowledgements =
Line 187: Line 176:
 
* Luis Enriquez (Copyright & IT Lawyer)
 
* Luis Enriquez (Copyright & IT Lawyer)
 
* Jeff Williams (Computer Security Expert)
 
* Jeff Williams (Computer Security Expert)
−
* Jorge Lara    (Graphical Designer)
 
  
  
Line 193: Line 181:
 
The priorities of the OWASP Security Labeling System are:
 
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
+
'''(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).  
−
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 badge type, which will have to be included in IT contracts, licenses(additional terms for public licenses), terms of service, or privacy policies. The Developer has the compromise of providing the OWASP labeling system conditions.
+
'''(2) Create the most suitable methodology for the security labeling system'''. At this point seems that the best methodology is to create a logo and a declaration. The logo must be visible within the web application, and linked to the declaration and reports stored on the OWASP security labeling system records. The declaration may also be included within the web application, or as part of IT contracts, copyright licenses(additional terms for public licenses), terms of service, or privacy policies.
  
−
'''(3)Application of the labeling system.''' The OWASP labeling system volunteers will contribute to check that the system is working properly. The label can always be removed.
 
  
−
Involvement in the development and promotion of the OWASP Security Labeling System is actively encouraged!
+
'''(3) Create a secure server in order to generate genuine certificates for the labeled web applications. '''WE ARE HERE
−
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.
 
  
−
=DEMO1(source code)=
 
−
'''''/*This example shows how to include the OWASP Security Labeling System clauses into a software download. The computer program jazz-scales.zip  includes the SECURITY, PRIVACY and INGREDIENTS labels:*/'''''
 
  
−
'''''/* FIRST: Show the labels on the download page*/'''''
+
'''(4) Evaluate the labeling system with a voluntary Application on the Internet.''' This application will be promoted as the first Labeled application. We would start with the '''OPENNESS LABEL''' If the results are good enough, we will add the other labels.
  
−
Jazz-scales  is labeled under the OWASP SECURITY LABELING SYSTEM as:
 
  
−
[[File:Owasp-security-scaled.png]] [[File:Privacy-scaled.png]] [[File:Owasp-ingredients-scaled.png]]
+
'''(4) Open the labeling system for any Application''' The OWASP labeling system volunteers will contribute to check that the system is working properly. The labels can always be removed.  
  
  
−
Download jazz-scales.zip from here: [[File:Jazz-scales.zip]]
+
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:
  
−
'''''/*SECOND: Show the hash sum or a link of the hash sum in case of Privacy Label */'''''
+
* Get into the testing program.
 +
* Improve the system.
 +
* Translate the documents to other languages.
 +
* Improve this wiki.
  
−
You must verify the hash-sum of the .zip package before installing:
 
  
−
MD5sum= faffffac8cb288233951cee6587dee33
+
---------------------------------------------------------------
−
 
 
−
SHA1sum= 00c533903ab6c3afc717021e724b479f8637c41a
 
−
 
 
−
'''''/*THIRD: The demo program is licensed under a GPL v3 license, with an OWASP Security Labeling System exception(Please read the license):*/'''''
 
−
 
 
−
YOU MUST read the READ-ME file, and the LICENSE agreement before using this software.
 
  
−
-------------------------------------------------
 
−
'''/* FOURTH: The logos will be linked to the Security Labeling System Site. The certificate could look like this:*/'''''Italic text''
 
−
''
 
−
'''CERTIFICATE'''(something like this, after clicking the logo)
 
  
−
LEGAL REPRESENTATIVE: Jazz scales corporation.
+
=DEMO (Web Apps)=
 +
'''''/*This example shows how to apply the OWASP Security Labeling system clauses into your Web Site's TERMS AND CONDITIONS. They should be placed inside an OWASP Security Labeling System section. The labeling logos could be placed in your anywhere as long as they remain visible. (as in the front page of this Website, as widget). This Web Site uses 3 labels: Security, Privacy, and Openness */'''''
  
−
TYPE: Computer program. (Source code )
+
'''''/*FIRST: The logos could be placed in the front page of the website: */'''''
  
−
NAME: Jazz-Scales.zip
+
[[File:Labelingsystem-widget.png]]
  
−
FURTHER INFORMATION:
+
'''''/*SECOND: Add the OWASP Security Labeling System clause to your Terms and Conditions: */'''''
  
−
SECURITY LABEL: This software has been developed using the following security guides: OWASP Security Principles Project, OWASP Software security Assurance Process.
+
''Please read carefully the following terms and conditions before registering and using this WebSite:''
  
−
PRIVACY LABEL: You must verify the hash-sum of the .zip package before installing:
+
1. OWASP SECURITY LABELING SYSTEM. This Web Application is labeled under the OWASP security labeling system with the purpose of making security VISIBLE for everybody. THIS IS A SECURITY COMPROMISE BETWEEN THE ADMINISTRATOR of this Web Application, and the end users. This system is only based on trust and reputation. OWASP denies any liability, or damage claims of any kind.
  
−
MD5sum= faffffac8cb288233951cee6587dee33
+
SECURITY LABEL CLAUSE: Security starts with secure coding and maintainance. This Web application is following the security guidelines of the OWASP Application Security Verification Standard. Reports can be downloaded "here".
  
−
SHA1sum= 00c533903ab6c3afc717021e724b479f8637c41a
+
PRIVACY LABEL CLAUSE: Security is about Trust. This Web application uses a scan policy based on the OWASP top ten Privacy project. Reports can be downloaded here.
  
−
This Software will not sale or transfer you personal data without authorization.  
+
OPENNESS LABEL CLAUSE: Security is about Transparency. This Web application is regularly scanned by a policy based on the OWASP top ten project. Reports can be downloaded here.
  
−
INGREDIENTS LABEL:  This computer program is distributed as source code and contains the following source files:
+
THIS COMPROMISE IS VALID AS LONG AS THIS WEB APPLICATION IS REGISTERED INTO THE OWASP SECURITY LABELING SYSTEM RECORDS.
−
 
 
−
scales.h
 
−
modal_music2.cpp
 
−
 
 
−
REPORT  VIOLATIONS TO: OWASP_Security_Labeling_System_Project
 
−
 
 
−
---------------------------------------------------------------
 
−
 
 
−
 
 
−
=DEMO2(Web Apps)=
 
−
'''''/*This example shows how to apply the OWASP Security Labeling system clauses into your Web Site's TERMS AND CONDITIONS. They should be placed inside an OWASP Security Labeling System section. The labeling logos could be placed in your anywhere as long as they remain visible. (as in the front page of this Website, as widget). This Web Site uses 3 labels: security, Privacy, and Openness */
 
−
'''''
 
−
'''''/*FIRST: The logos could be placed in the front page of the website: */''
 
−
'''
 
−
[[File:Example-web-labeling.png]]
 
−
 
 
−
'''/*SECOND: Add the OWASP Security Labeling System clause to your Terms and Conditions: */'''''Italic text''
 
−
 
 
−
''Please read carefully the following terms and conditions before registering and using this WebSite:
 
−
 
 
−
1. OWASP SECURITY LABELING SYSTEM. This Software has been labeled under the OWASP security labeling system with the purpose of making security VISIBLE for everybody. THIS LEGAL COMPROMISE IS BETWEEN THE LEGAL REPRESENTATIVE OF THIS SOFTWARE, AND THE END USER.
 
−
 
 
−
SECURITY LABEL CLAUSE:  Security is about secure coding. This software has been developed and is maintained following the highest OWASP secure coding practices. A list of all the security guides and tools used by the developers of this software must be included or linked through this notice.
 
−
 
 
−
PRIVACY LABEL CLAUSE: Security is about Trust. This Software comes free of non authorized spy-ware or surveillance code of any kind. The legal representative, or person in charge of this software will not sale, commercialize, or missuse user's personal data without the user's permission.
 
−
 
 
−
OPENNESS LABEL CLAUSE: Security is about Transparency. This Web Application makes available its latest vulnerability reports to the public. The report or a link to the report must be clearly published in this Web Application. This compromise is only effective if the vulnerability report's date is not older than 1 week.
 
−
 
 
−
THIS COMPROMISE IS ONLY VALID AS LONG AS THIS SOFTWARE IS REGISTERED INTO THE OWASP SECURITY LABELING SYSTEM RECORDS.
 
  
 
2.LIABILITY:'''/*(from here, clauses are not important)*/'''
 
2.LIABILITY:'''/*(from here, clauses are not important)*/'''
Line 294: Line 238:
 
4. TERMINATION:
 
4. TERMINATION:
 
- You can always close your account in this website. We also reserve the right of closing user's accounts if they infringe the terms and conditions of this website.
 
- You can always close your account in this website. We also reserve the right of closing user's accounts if they infringe the terms and conditions of this website.
−
''
 
−
--------------------------------------------------------
 
−
'''*/FOURTH: The labeling logos of the front WebSite page should link to the OWASP Security Labeling System Site, and generate a certificate, such as:*/'''''Italic text''
 
−
 
−
'''CERTIFICATE'''(something like this)
 
−
 
−
LEGAL REPRESENTATIVE:  FOSS Lawyers Institute.
 
−
 
−
TYPE: Web Application.
 
−
 
−
URL:  http://172.16.208.128/mutillidae
 
−
 
−
FURTHER INFORMATION:
 
−
 
−
SECURITY LABEL: This Web Application has been developed and is maintained using: The OWASP TOP TEN Project, OWASP secure coding practices, and OWASP Security Principles Project.
 
−
 
−
PRIVACY LABEL:  This Web Application will not sale or transfer you personal data without your authorization. This Web Application follows the OWASP Top Ten Privacy Project.
 
−
 
−
OPENNESS LABEL: Here you can find the lastest vulnerability report of this web application: [[File:Example-report.png]]
 
−
 
−
REPORT  VIOLATIONS TO: OWASP_Security_Labeling_System_Project
 
  
  
Line 323: Line 246:
 
__NOTOC__ <headertabs />  
 
__NOTOC__ <headertabs />  
  
−
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]
+
[[Category:OWASP Project]]   
 +
[[Category:OWASP_Builders]]  
 +
[[Category:OWASP_Defenders]]   
 +
[[Category:OWASP_Document]]

Latest revision as of 10:28, 3 June 2019

OWASP security labeling system2.png

PURPOSE

Making security VISIBLE for everybody.


WHAT IS IT?

It is system of security labels for web applications.

HOW DOES IT WORK?

There are 4 labels:

* Security (S). Security starts with SECURE CODING, and secure maintenance. This label is based on the OWASP Application Security Verification Standard(ASVS). Web applications will get a rating based on the Applications Security Verification levels on the AVSV standard(cursory, standard, opportunistic, and advanced).

* Privacy (P). Security is also about TRUST. Technical security is not relevant if Software comes with hidden backdoors, and non-transparent policies. This label will require a Privacy scanning policy that may be based on the OWASP Top Ten Privacy project. Web applications must follow ethical principles of data processing and data protection.

* Ingredients (I). Security is also about TRANSPARENCY. This condition is only possible through the use of Open Source Software. Contemporary Software is built(and linked) by many components such as shared libraries, APIs, and so on. This label is about Web Applications exposing all their ingredients, including third party code and dependencies.

* Openness (O). Security might also be OPEN. Open security means having a fast and reliable IT security team. This label consists on a scanning policy based on the OWASP Top Ten project, and making the scan visible.

IMPLEMENTATION

Due to the complexity of the tasks, the Labels will be implemented 1 by 1. The first Label to be implemented is the OPENNESS LABEL. We will start with this experimental implementation in June - 2015. In the mean time we need open security promoters, to get submitted into the project's records.

The System provides 4 logos and 4 clauses(1 for each label). The clauses can be added before the copyright public licenses as a "license exception", or included in the warranty clause(or any other) in custom copyright licenses, license contracts, terms of services, or even privacy policies.

STEP 1: Get Registered into the OWASP Security Labeling system Site.

STEP 2: Download the label-logo(s) and paste before your copyright license, license contract, terms of service, or privacy policy.

STEP 3: Incorporate the correspondent label-clause(s) in a visible place within your Web application, copyright license, license contract,terms of service,or privacy policy.

COMPROMISES

- Between DEVELOPER and the OWASP SECURITY LABELING PROJECT. By including the Labeling-logos, the Developer gets the compromise of following the OWASP labeling system requirements.

- Between DEVELOPER and USERS. By incorporating the Labeling-Clauses, Web service providers assume a direct compromise with their users.

- Between OWASP SECURITY LABELING PROJECT and USERS. Users can report violations of the labeling system to the OWASP labeling project Volunteers.

PRESENTATION

http://owaspsecuritylabelingsystem.blogspot.com/ http://www.slideshare.net/luisenriquezA/owaspsecuritylabelingsystem

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.

NEWS AND EVENTS

  • The proposal of this project has been relaunched. We are examining with a new team the possibilities of a joint venture for complying the new legal regulations such as GDPR in the summer of 2019.

YOU ARE ALL INVITED TO JOIN THIS SECURITY PROJECT.

PROJECT LEADER

Luis Enriquez


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.

RELATED PROJECTS

CLASSIFICATIONS

Owasp-incubator-trans-85.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files CODE.jpg

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