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
(→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?''' | |
− | '''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?''' | |
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?''' | |
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?''' | |
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?''' | |
− | |||
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