[Owasp-board] Fortify's Java Open Review Project and Sponsoring an OWASP Spring of Code Project

Fredrick DeQuan Lee flee at fortifysoftware.com
Wed Apr 4 18:00:20 UTC 2007

I am working to create an OWASP specific section for projects on the  
public site right now. Hopefully, we can have that turned around  
within the month (hopefully after JavaOne).

With regards to workflow, we're currently placing the scans into a  
cruisecontrol type system. I can look into a way to allow OWASP to  
initiate/trigger the automated scans. I can add the project owners to  
the mail notification when a new scan is completed.

Another big contribution would be getting help from the OWASP project  
developers to review the issues we detect. I don't believe you've  
walked through the interface, but there's a simple option to select  
"fix/don't fix". At the moment, we're doing all of the human  
analysis. Although our results are pretty good, code auditing  
*always* benefits from actual developer knowledge/involvement.

With regards to how much, I'll get back to you before the end of this  
week. I can easily do $2k right now towards the metrics project as  
part of the open source review budget. I'll see what additional funds  
I can procure.

One final thing, we currently only have JBroFuzz and Webgoat (which  
is functioning as a demo/educational project) in the scan rotation.  
Are there any other OWASP projects that you would like to see added  

On Apr 4, 2007, at 10:20 AM, Dinis Cruz wrote:

> Well we need/should scan every OWASP released tool (and figure out  
> a workflow for that) since there is a real posibility that some of  
> them might have serious vulnerabilities or backdoors (at the moment  
> we just don't know), except for the applications that are supposed  
> to be insecure :)
> I like the idea that we create a workflow at a service like the one  
> you provide (maybe via an OWASP specific project/section) where we  
> check our apps before every major release (in the future I even  
> want to alocate a budget for that so that we have a dedicated team  
> that is responsible for checking and validating those releases).
> Regarding the sponsorship of the metrics, the answer is yes. The  
> deadline for SpoC 007 was extended one week and even when the  
> submission period is over, depending on the number and quality of  
> applicants, we might still have some budget to allocate after it.  
> So the question is how much do you want to sponsor?
> Dinis Cruz
> Chief OWASP Evangelist
> http://www.owasp.org
> On 4/4/07, Fredrick DeQuan Lee <flee at fortifysoftware.com> wrote:
> Dinis, any word on getting more OWASP projects under review by the  
> open source scanning project? Also, is there still time for Fortify  
> to sponsor more work on the metrics project?
> On Mar 30, 2007, at 12:56 PM, Fredrick DeQuan Lee wrote:
>> We had no particular external individual in mind to work on the  
>> metrics project. The metrics project seems like a good topic for  
>> an OWASP intern or grad student.
>> With regards to scanning OWASP projects, all of the Java OWASP  
>> projects are not only welcome, but encouraged to get added to our  
>> project. I know that both JBroFuzz and Webgoat are already in our  
>> routine scan list. One of our goals is to actually encourage and  
>> help open source developers to fix the issues that we find.  
>> Partnering with OWASP would at least make it easier to get OWASP  
>> projects fixed.
>> On Mar 30, 2007, at 12:47 PM, Dinis Cruz wrote:
>>> That idea does sound interesting, do you have anybody in mind to  
>>> do that project (which we could sponsor)
>>> I haven't seen a SpoC 007 on that subject ( https://www.owasp.org/ 
>>> index.php/OWASP_Spring_Of_Code_2007_Applications) but it would  
>>> definitely be an strong application
>>> Stephen or Bob, any comments on this? (Stephen is on the Java  
>>> Project and Bob Austin is on the Metrics)
>>> I also wanted to explore the option to scan OWASP projects using  
>>> your tool/free service, what are our options?
>>> Dinis Cruz
>>> Chief OWASP Evangelist
>>> http://www.owasp.org
>>> On 3/29/07, Fredrick DeQuan Lee < flee at fortifysoftware.com> wrote:
>>> Dinis,
>>>  I just read the latest OWASP news letter and saw  the call for  
>>> OWASP Spring of Code participation. As you know, Fortify Software  
>>> produces software security and quality analysis tools. Fortify  
>>> recently launched a public project, the Java Open Review Project  
>>> ( http://opensource.fortifysoftware.com), to examine Java open  
>>> source projects for security and quality defects. The project  
>>> retrieves open source projects, performs static analysis using  
>>> FindBugs and Fortify Source Code Analysis, and presents the  
>>> results for online analysis for auditors and project owners.  
>>> Fortify is currently seeking participation from those wishing to:  
>>> submit projects, review security defects, help fix open source  
>>> security defects, or supply general feedback.
>>> I noticed that two of your Spring of Code project ideas listed  
>>> would benefit from the information available at the JOR project  
>>> site. Specifically, the Java Project and the AppSec Metrics  
>>> project both could make use from the data collected in the JOR  
>>> project site. Of particular interest to me would be having an  
>>> OWASP Spring of Code participant process JOR data to use in the  
>>> AppSec Metrics -- project. Fortify should be able to contribute  
>>> additional funding for such an effort. Do you think there would  
>>> be interest in such a project?
>>> More details about the JOR Project can be found at: http:// 
>>> opensource.fortifysoftware.com
>>> I hope to hear from you soon!
>>> Fredrick DeQuan Lee
>>> Fortify Software
>>> Security Research Group
>>> (w) 650-213-5677
>> Fredrick DeQuan Lee
>> Fortify Software
>> Security Research Group
>> (w) 650-213-5677
> Fredrick DeQuan Lee
> Fortify Software
> Security Research Group
> (w) 650-213-5677

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/owasp-board/attachments/20070404/8014381b/attachment-0002.html>

More information about the Owasp-board mailing list