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
(Privacy Label: minor grammar changes: added space following comma, changed "representer" to "representative")
(FAQs: Cleaned up paragraph indenting)
Line 141: Line 141:
 
  Different labeling categories for different purposes.
 
  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?'''
 
'''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.
 
  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?'''
+
'''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.
 
  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.
  
Line 157: Line 156:
 
  This label certifies that your software does not come with non-authorized spyware, and that your personal data will be respected.
 
  This label certifies that your software does not come with non-authorized spyware, and that your personal data will be respected.
  
'''Why is the Privacy label relevant?'''
+
'''Why is the Privacy label relevant?'''
 
  Developers assume the legal compromise of not including hidden backdoors and surveillance code.  
 
  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.
 
  The user would also have the obligation of checking the software hashsums.
Line 164: Line 163:
 
  Is about exposing all the components of your software, such as API's, shared libraries, third party software.
 
  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?'''
+
'''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,  
 
  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.
 
  avoid non intentional license compatibility controversies, and so forth.
  
 
 
'''What is the Openness label(O) about?'''
 
'''What is the Openness label(O) about?'''
 
  It is dedicated to high security environments. Web Applications will expose their vulnerabilities of the  
 
  It is dedicated to high security environments. Web Applications will expose their vulnerabilities of the  
Line 174: Line 172:
 
  The scans should be fixed in a regular basis(e.g. each week).
 
  The scans should be fixed in a regular basis(e.g. each week).
  
'''Why is the Openness label(O) relevant?'''
+
'''Why is the Openness label(O) relevant?'''
 
 
  Getting this label means that a security team reveals their vulnerabilities to the public as expected.  
 
  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.  
+
  but at the same time, it shows to the public how good and fast they are in order to fix them.
 
 
  
 
= Acknowledgements =
 
= Acknowledgements =

Revision as of 22:16, 14 May 2014

OWASP security labeling system2.png

PURPOSE

Making security VISIBLE for everybody.


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).

HOW DOES IT WORK?

The labeling system is classified by 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...)

* 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.

* 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.

* 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.


IMPLEMENTATION

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 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.

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 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 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 is READY. Time for Opinions and Corrections.


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