Jeff Williams had a great post following the discussion we had at TwitterLand (direct quote from Jeff's email):
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 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 want**
- Open Test – test with your account all you want
- Staged Test–register and we’ll let you test on a non-production system
- No Testing – you are an evil hacker
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 disclosure
- OWASP Private Security Program – Staged Testing + private disclosure
- 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…