Difference between revisions of "Category:OWASP Source Code Review OWASP Projects Project"

From OWASP
Jump to: navigation, search
m (Process)
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[:Category:OWASP Project|Click here to return to OWASP Projects page.]]<br>
 
[[:Project Information:template Source Code Review OWASP Projects|Click here to see (& edit, if wanted) the template.]]
 
 
{{:Project Information:template Source Code Review OWASP Projects}}
 
{{:Project Information:template Source Code Review OWASP Projects}}
[[Category:OWASP Project]]
+
[[Category:OWASP Project|Source Code Review OWASP Projects Project]]
 +
[[Category:OWASP Document]]
 +
[[Category:OWASP Download]]
 +
[[Category:OWASP Release Quality Document]]
  
== Process ==
+
== Summary ==
  
 +
This project involving creating a process for integrating the Fortify Open Review Process into the OWASP project development lifecycle and working with Fortify to develop and test their new Open Review site at [http://owasp.fortify.com/ http://owasp.fortify.com/].  The [https://www.owasp.org/images/c/c9/OWASPEU_SourceReview.ppt OWASP EU Summit presentation] contains a more detailed summary of the project.
 +
 +
== Goals ==
 +
 +
The goals of this project were to:
 +
 +
# Create a process for integrating the Fortify Open Review into open source development, so that source code review can be a required step in OWASP development.
 +
# Test functionality of the new Fortify Open Review site introduced in Summer 2008.
 +
# Scan 10 OWASP projects with the Fortify Open Review to verify the site's functionality and establish a baseline.
 +
# Scan 25 popular open source PHP projects to verify the site's ability to handle large scale projects and establish a baseline.
 +
 +
== Process ==
  
The OWASP Source Code Review integrates OWASP projects with the Fortify Open Review Process. The workflow can be found in [[https://www.owasp.org/index.php/Image:Workflow_July_11a.zip Workflow.zip]] Therefore, any open source project using this workflow must first be added as an OWASP project as illustrated in [[Image:Workflow_Draft1.pdf#file]].   
+
The purpose of this workflow is to integrate and automate SCA into the development cycle of open source applications for the sole purpose of decreasing software vulnerabilities.  This effort can, and should, be supplemented by a manual code review as described in the OWASP Open Review Project. The workflow diagrams can be found in [https://www.owasp.org/index.php/Image:Workflow_July_11a.zip Workflow.zip]. Within the ZIP file, overview.pdf describes the relationships between the different parts of the workflow. The file start.pdf describes the first step of the workflow which verifies that the project is an OWASP project.  If it is not then the project is added as a new OWASP project [[Image:Workflow_Draft1.pdf#file]].  Once the project is established as an OWASP project, it can be added by an OWASP administrator (contact the project mailing list below to contact an OWASP administrator) to the Fortify Open Review (reference createProject.pdf).   
  
As described in the Fortify Open Review Process, the Project Lead or Source Code Review Lead can choose between a continuous evaluation, where SCA is done weekly, or one time analysis. The single analysis requires the evaluator to submit a Fortify output file, which requires the evaluator to own a copy of Fortify.  The continuous evaluation is automated and in accordance with the [ http://www.lulu.com/content/1415989 OWASP Code Review Guide], these results can be used to remove common problems.  The common problems, along with other software errors exposed by findBugs, will be documented as known problems.
+
As described in the [http://www.owasp.org/index.php/Category:OWASP_Open_Review_Project_owasp.fortify.com_FAQ Fortify Open Review process], the Project Lead or Source Code Review Lead can choose between a continuous evaluation, where the project is checked out from its repository and the Open Review scan is updated on a weekly basis, or a one time analysis as part of their usual development process (see waterfall.pdf and iterative.pdf) after unit testing and prior to final system testing.  The single analysis requires the evaluator to produce and upload a Fortify FPR scan file, which requires either that the evaluator uses their own copy of Fortify SCA or contacts an OWASP administrator via the project mailing list to request a scanIn order to track project progress over time, single analyses of major project versions will be maintained on the project web site so that software vulnerability metrics can be tracked.  The continuous evaluation is automated, does not require the developer have a Fortify SCA license. There are additional open source static analysis tools that can be used as part of a project's development lifecycle on a regular basis, such as FindBugs (see findBugs.pdf) and OWASP Orizon.
  
The single analysis or any one of the continuous analysis can be followed by a code review Manual Review as described in the OWASP Open Review Project.
+
Of course, once vulnerabilities are detected, they need to be either fixed or marked as false positives through the Fortify Open Review site interface.  See the [http://www.lulu.com/content/1415989 OWASP Code Review Guide] for information on how to fix common vulnerabilities.
  
 
== OWASP Projects Scanned ==
 
== OWASP Projects Scanned ==

Latest revision as of 12:45, 9 March 2010


PROJECT IDENTIFICATION
Project Name OWASP Source Code Review OWASP-Projects Project
Short Project Description The objectives of this project are: 1. Develop and document a workflow for FLOSS projects to incorporate static analysis into the Software Development Life Cycle (SDLC); 2. Apply the above workflow as a required step for OWASP projects; 3. Aid in auditing select FLOSS projects to create a baseline for comparing security amongst FLOSS projects.
Project key Information Project Leader
Dan Cornell
SoC's Project Leader
James Walden
Project Contributors
Justin Derry
Maureen Doyle
Michael Whelan
Grant Welch
Mailing list
Subscribe here
Use here
License
Creative Commons Attribution Share Alike 3.0
Project Type
Documentation
Sponsor
OWASP SoC 08
Fortify
Release Status Main Links Related Projects

Release Quality
Please see here for complete information.


Contents

Summary

This project involving creating a process for integrating the Fortify Open Review Process into the OWASP project development lifecycle and working with Fortify to develop and test their new Open Review site at http://owasp.fortify.com/. The OWASP EU Summit presentation contains a more detailed summary of the project.

Goals

The goals of this project were to:

  1. Create a process for integrating the Fortify Open Review into open source development, so that source code review can be a required step in OWASP development.
  2. Test functionality of the new Fortify Open Review site introduced in Summer 2008.
  3. Scan 10 OWASP projects with the Fortify Open Review to verify the site's functionality and establish a baseline.
  4. Scan 25 popular open source PHP projects to verify the site's ability to handle large scale projects and establish a baseline.

Process

The purpose of this workflow is to integrate and automate SCA into the development cycle of open source applications for the sole purpose of decreasing software vulnerabilities. This effort can, and should, be supplemented by a manual code review as described in the OWASP Open Review Project. The workflow diagrams can be found in Workflow.zip. Within the ZIP file, overview.pdf describes the relationships between the different parts of the workflow. The file start.pdf describes the first step of the workflow which verifies that the project is an OWASP project. If it is not then the project is added as a new OWASP project File:Workflow Draft1.pdf. Once the project is established as an OWASP project, it can be added by an OWASP administrator (contact the project mailing list below to contact an OWASP administrator) to the Fortify Open Review (reference createProject.pdf).

As described in the Fortify Open Review process, the Project Lead or Source Code Review Lead can choose between a continuous evaluation, where the project is checked out from its repository and the Open Review scan is updated on a weekly basis, or a one time analysis as part of their usual development process (see waterfall.pdf and iterative.pdf) after unit testing and prior to final system testing. The single analysis requires the evaluator to produce and upload a Fortify FPR scan file, which requires either that the evaluator uses their own copy of Fortify SCA or contacts an OWASP administrator via the project mailing list to request a scan. In order to track project progress over time, single analyses of major project versions will be maintained on the project web site so that software vulnerability metrics can be tracked. The continuous evaluation is automated, does not require the developer have a Fortify SCA license. There are additional open source static analysis tools that can be used as part of a project's development lifecycle on a regular basis, such as FindBugs (see findBugs.pdf) and OWASP Orizon.

Of course, once vulnerabilities are detected, they need to be either fixed or marked as false positives through the Fortify Open Review site interface. See the OWASP Code Review Guide for information on how to fix common vulnerabilities.

OWASP Projects Scanned

AntiSamy

CSRFGuard

CSRFTester

DirBuster

JBroFuzz

Lapse

Stinger

Webekci

WebGoat

WebScarab

Non-OWASP projects scanned in MediaWiki, WordPress, and many others. See owasp.fortify.com for details.

Get involved

We need OWASP project leaders to submit their projects for review. We will work with you to upload your project and review the findings, so that we can get each OWASP project to show zero defects.

Please go to https://lists.owasp.org/mailman/listinfo/owasp-scode-review-owasp-projects to subscribe to the list to contact us. You can post to the mailing list by emailing [1].

People

Project lead: James Walden

Contributors: Maureen Doyle, Grant Welch, Michael Whelan

Reviewers: Marco Morano, Alex Fry

Fortify Software has generously made their Source Code Analyzer (SCA) technology available for use by open source projects at owasp.fortify.com.

This category currently contains no pages or media.