[Owasp-leaders] OWASP testing and disclosure levels

Brian Bertacini brian at appsecconsulting.com
Mon Dec 21 11:50:16 EST 2009

Jeff, this is a great idea.  It would be nice to see the PCI-SSC adopt one
of these standards as a requirement for applications in scope for PA-DSS and
PCI-DSS.  All too often I run into cases where QSAs and other firms are not
doing a thorough job of testing web applications and in my opinion this
would be a very good solution.  Requiring a documented OWASP testing
standard would be a big improvement and add more credibility to the PCI
program.  It would also help generate much needed momentum in the industry.
I'm on board.  



Brian Bertacini, CISA, PCI-QSA
AppSec Consulting, Inc.
ph:   408-723-1960
cell: 408-771-8638
email: brian at appsecconsulting.com



From: owasp-leaders-bounces at lists.owasp.org
[mailto:owasp-leaders-bounces at lists.owasp.org] On Behalf Of Jeff Williams
Sent: Monday, December 21, 2009 7:55 AM
To: owasp-leaders at lists.owasp.org
Subject: [Owasp-leaders] OWASP testing and disclosure levels

I saw some twittering about this sort of thing over the weekend.


The basic idea is that we could create some OWASP standards around the way
that companies allow their websites to be tested/scanned/reviewed and how
they want to handle disclosure of issues that are discovered.  Companies
could choose the standard they want to follow and it would encourage people
to make that choice explicit and public (visible).


We could do this pretty easily in the OWASP Legal Project - the way that
Creative Commons defined some IP licenses and released them.  I'm just not
sure what the current practices are.  Has anyone catalogued a list of
companies with either testing or disclosure policies?  See Microsoft
<http://www.microsoft.com/security/msrc/report/disclosure.aspx> policies.


Just as an off the top of the head brainstorm, what do you think of these??
Of course we'd have to specify these carefully and fully.


.        Full Disclosure - disclose anything you find

.        Responsible Disclosure - work with us please

.        Private Disclosure - send it to us and pray

.        No Disclosure - we will hunt you down and kill you


.        Fully Open - code review + test all you want

.        Open Code Review - we'll let you review the source and test all you

.        Open Test - test  with your account all you want

.        Staged Test-register and we'll let you test on a non-production

.        No Testing - you are an evil hacker


** Note: I have already drafted an "OWASP Open Code Review" license that
grants people the rights they need to do a source code review without giving
up ownership or other legal rights.


We could combine these into a few interesting combinations.


.        OWASP Open Security Program - Fully open review + full disclosure

.        OWASP Shared Security Program - Open testing + responsible

.        OWASP Private Security Program - Staged Testing + private

.        OWASP "Trust Us" Insecurity Program - No testing + no disclosure




Note that this is NOT a certification program.  This is a way for companies
to *declare* their approach to security.  Your thoughts welcome.





-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/owasp-leaders/attachments/20091221/fb098b04/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 147333 bytes
Desc: not available
Url : https://lists.owasp.org/pipermail/owasp-leaders/attachments/20091221/fb098b04/attachment-0001.png 

More information about the OWASP-Leaders mailing list