|
|||||||||||
|
Re: Web Application Source Vulnerability Scanners
From: Kevin Spett <kspett(at)spidynamics.com>
Date: Tue Mar 04 2003 - 14:22:39 EST Moderator: As SA stated, this is delicate as it involves the discussion of commercial software produced by the companies that I (and Ory) work for. However, I think that my points are valid and discussion-worthy. First, there are other tools besides AppScan that know how to keep state correctly. WebInspect does. Second, on to the aforementioned article. The info security magazine test report is less than scientific, as it doesn't detail any of the exact testing procedures, server configuration, give source code for the applications, etc. It does not allow anyone to duplicate or evaluate its findings. Also, the test was financed and performed by a company that makes money by performing services that tools such as AppScan and WebInspect are designed to test. Finally, the two authors of the article are not well-known in the area of web application security. Keep in mind that these are not accusations. I am not alleging that the test results were incorrect. I am not saying that the authors are unqualified. I'm just saying that the test really doesn't really provide enough information for real technical discussion. Thus, its findings cannot be "proved" either way. I distrust that which cannot be proved. I simply recommend that people who are interested in appraising the quality of web security tools, both free or commercial, make their own tests and judgements, so that they can control every variable of the analysis. This will have to be the case until there are truly "open" evaluations that are not lacking in steps for reproduction.
Kevin Spett
>
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:07:49 EDT |
||||||||||
|
|||||||||||