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 "Summit 2011/Open letter to WebAppSec Tool and Services vendors: Release your schemas and allow automation/Letter Content"
Dinis.cruz (talk | contribs) |
Dinis.cruz (talk | contribs) (→Open Letter) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 14: | Line 14: | ||
Although you provide a product or service that automates (as much as you can) the process of evaluating the security of a particular application, at the moment (Feb 2011) it is very hard to consume, consolidate, integrate and instrument your deliverables and technology. | Although you provide a product or service that automates (as much as you can) the process of evaluating the security of a particular application, at the moment (Feb 2011) it is very hard to consume, consolidate, integrate and instrument your deliverables and technology. | ||
| − | Our industry (and clients) desperately need to move into a world where we are able to consolidate, analyse and present the results created by multiple tools/services. This would create a scenario where we (for example) are able to deliver to developers (as Unit Tests or Software-as-a-Service) 'complete and integrated' findings (i.e. security findings that contain both WhiteBox and BlackBox findings). We also need to be able to create WAF rules from the findings delivered, and must have the ability to integrate them with other technologies used through the Software Development LifeCycle (e.g. BugTracking, Change Control, Application Modelling/Design Tools, Threat Modelling tools, Knowledge-Base/ELearning solutions etc...) | + | Our industry (and clients) desperately need to move into a world where we are able to consolidate, analyse and present the results created by multiple tools/services. This would create a scenario where we (for example) are able to deliver to developers (as Unit Tests or Software-as-a-Service) 'complete and integrated' findings (i.e. security findings that contain both WhiteBox and BlackBox findings). We also need to be able to create WAF rules from the findings delivered, and must have the ability to integrate them with other technologies used through the Software Development LifeCycle (e.g. BugTracking, Change Control, Application Modelling/Design Tools, Threat Modelling tools, Knowledge-Base/ELearning solutions, etc...) |
At the moment there are numerous companies and projects that are trying to achieve such integration (good luck on their endeavours), but we need an independent base we call all work from. | At the moment there are numerous companies and projects that are trying to achieve such integration (good luck on their endeavours), but we need an independent base we call all work from. | ||
| Line 32: | Line 32: | ||
* '''APIs that can be used to instrument and control your scanning engine''' (please provide as much documentation as possible on the currently supported ways to interact with your product) | * '''APIs that can be used to instrument and control your scanning engine''' (please provide as much documentation as possible on the currently supported ways to interact with your product) | ||
| − | With these materials (to be uploaded to a google code repository), the OWASP community will try to create the following standards (reusing as much as possible the great work done by others in this space (MITRE, CWE, NIST, etc...): | + | With these materials (to be uploaded to a google code repository), the OWASP community will try to create the following standards (reusing as much as possible the great work done by others in this space (MITRE, CWE, NIST, OVAL, etc...): |
* Open Findings Schema | * Open Findings Schema | ||
* Open Rules Schema | * Open Rules Schema | ||
Latest revision as of 20:10, 2 February 2011
To WebAppSec vendors
This request is mainly focused on the commercial vendors of products and services of the following WebAppSec categories: Pen-testing, Code Review, BlackBox Scanning, WhiteBox Scanning and WAFs.
Other software/services categories, including equivalent Open Source tools, are more than welcomed to participate.
Open Letter
02/Feb/2010
Open letter to WebAppSec tool/services vendors: Release your schemas and allow automation
Dear vendor,
Although you provide a product or service that automates (as much as you can) the process of evaluating the security of a particular application, at the moment (Feb 2011) it is very hard to consume, consolidate, integrate and instrument your deliverables and technology.
Our industry (and clients) desperately need to move into a world where we are able to consolidate, analyse and present the results created by multiple tools/services. This would create a scenario where we (for example) are able to deliver to developers (as Unit Tests or Software-as-a-Service) 'complete and integrated' findings (i.e. security findings that contain both WhiteBox and BlackBox findings). We also need to be able to create WAF rules from the findings delivered, and must have the ability to integrate them with other technologies used through the Software Development LifeCycle (e.g. BugTracking, Change Control, Application Modelling/Design Tools, Threat Modelling tools, Knowledge-Base/ELearning solutions, etc...)
At the moment there are numerous companies and projects that are trying to achieve such integration (good luck on their endeavours), but we need an independent base we call all work from.
With this in mind, the following data and artifacts are requested from you and ALL product vendors in this space :
- The XSD (schemas) for ALL released versions of your product/service (starting with the most recent release and going back as far as possible)
- Sample XML files (or whatever format the data can be exported) of: vulnerable-by-design and Open Source web applications - To kickstart this process please deliver the results for the following applications:
- OWASP WebGoat (Java),
- HacmeBank - OWASP version (.Net),
- MediaWiki (PHP),
- NerdDinner (ASP.NET MVC),
- PetStore (Struts/Spring version)]
- PetStore (DWR version).
- Other applications can be also provided at the discretion of the vendors (as long as it is possible to also scan those applications from other tools/services)
- Artifacts created during scanning (for example Internal representations of source code or web applications)
- Rules used during the scans (to allow the replication of findings and the creation of a core 'industry wide' set of rules)
- APIs that can be used to instrument and control your scanning engine (please provide as much documentation as possible on the currently supported ways to interact with your product)
With these materials (to be uploaded to a google code repository), the OWASP community will try to create the following standards (reusing as much as possible the great work done by others in this space (MITRE, CWE, NIST, OVAL, etc...):
- Open Findings Schema
- Open Rules Schema
- Open Application Artifacts Schema (which could also be called: Open Scan Targets Schema)
- Open Intermediate Representation Schema (abstraction layer of code and web assets)
The OWASP Summit 2011 represents a unique opportunity to make this happen, so please either provide the requested data yourselves, or allow your current clients to do so (without the thread of a lawsuit)
The undersigned below, urge you to join these effort and to active participate in this endeavour
