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 "Category:OWASP Orizon Project"
| Line 18: | Line 18: | ||
== Goals == | == Goals == | ||
| + | |||
Orizon’s goal is to provide a set of APIs to: | Orizon’s goal is to provide a set of APIs to: | ||
* Manage a safe coding rules library | * Manage a safe coding rules library | ||
| Line 33: | Line 34: | ||
== Download == | == Download == | ||
| + | |||
The source code is in a Subversion repository and hosted at sourceforge.net. | The source code is in a Subversion repository and hosted at sourceforge.net. | ||
| Line 63: | Line 65: | ||
A few words need to be said here: there is no intention to reinvent the wheel. The Web is full of libraries that sanitize source code in order to mitigate an attack on a web application. Bastion is just our small contribution to the community; we really hope that you'll appreciate it. | A few words need to be said here: there is no intention to reinvent the wheel. The Web is full of libraries that sanitize source code in order to mitigate an attack on a web application. Bastion is just our small contribution to the community; we really hope that you'll appreciate it. | ||
| − | == The | + | == The Library == |
For a code review tool, the most important factor is its knowledge, which are the security checks that is applied to the source code. No matter how many features a tool has or how fancy is its UI, a poor security check library means that the tool is useless. | For a code review tool, the most important factor is its knowledge, which are the security checks that is applied to the source code. No matter how many features a tool has or how fancy is its UI, a poor security check library means that the tool is useless. | ||
| Line 120: | Line 122: | ||
== Project Contributors == | == Project Contributors == | ||
| + | |||
--[[User:Thesp0nge|thesp0nge]] 09:47, 2 October 2006 (EDT) | --[[User:Thesp0nge|thesp0nge]] 09:47, 2 October 2006 (EDT) | ||
== Project Sponsor == | == Project Sponsor == | ||
| + | [https://www.owasp.org/index.php/OWASP_Summer_of_Code_2008 OWASP Summer of Code 2008] | ||
[[Category:OWASP Project]] | [[Category:OWASP Project]] | ||
[[Category:OWASP Tool]] | [[Category:OWASP Tool]] | ||
[[Category:OWASP Download]] | [[Category:OWASP Download]] | ||
Revision as of 03:56, 2 December 2008
Click here to return to OWASP Projects page.
Click here to see (& edit, if wanted) the template.
| PROJECT IDENTIFICATION | |||||||
|---|---|---|---|---|---|---|---|
| Project Name | OWASP Orizon Project | ||||||
| Short Project Description | This project born in 2006 in order to provide a framework to all Owasp projects developing code review services. The project is in a quite stable stage and it is usable for Java static code review and some dynamic tests against XSS. Owasp Orizon includes also APIs for code crawling, usable for code crawling tools. | ||||||
| Key Project Information | Project Leader Paolo Perego |
Project Contributors See here |
Mailing list Subscribe here Use here |
Project Type |
Sponsor OWASP SoC 08 | ||
| Release Status | Main Links | Related Projects |
|---|---|---|
|
The Owasp OrizonProject in Power Point |
Overview
The quest for secure code is what all developers want to achieve (at least we hope so). Software must be reliable. Software must be strong. Software must be secure.
How secure does my software have to be? The correct answer is hard to find. But security is a problem that even a development team must consider.
Should skilled developers also be security gurus? Not necessarily, but it is important to provide security tools that will augment their development skills. And so our quest for secure code begins...
The OWASP Orizon project was created with the aim of providing a common ground for safe coding and code review methodologies to be applied to software. The project is approaching its first major release and it will be able to be used in a production environment in the near future.
Orizon must give thanks to Findbugs, the OWASP LAPSE Project, RATS, and Flawfinder for ideas and inspiration.
The Orizon project, hosted by Sourceforge, is here.
Goals
Orizon’s goal is to provide a set of APIs to:
- Manage a safe coding rules library
- Apply these rules to a generic source file
- Support the most widely used programming languages (e.g. Java, JSP, C#, ASP.NET, C, C++)
- Create reports that shows source code assessment results
- Allow developers to build code review tools
- Help people understand how important it is to apply safe coding rules while making software
One of OWASP’s newly created goals is to “eat its own dog food” and Orizon contributes to this goal by implementing the security checks described in the OWASP Code Review Guide.
Documentation
Available online is an Orizon presentation given at OWASP AppSec EU 2008 in Ghent, May 2008.
Download
The source code is in a Subversion repository and hosted at sourceforge.net.
The latest release is 1.0.
Dawn
In September 2007, while hacking around release 0.50, a decision was made to introduce dynamic code review facilities – first for the Java language. Dawn was chosen as the name of this new feature in Orizon.
The project team believes that this will be the most cutting edge technology inside of Orizon; it will help developers rise from buggy and unsafe code to hardened and secure code; hence, the name dawn for all related dynamic code review.
Dawn was implemented in Orizon release 0.45pre1.
Bastion
Around March 2007, feedback from stressing the importance of reviewing code for security issues brought about the realization that a more lightweight solution needed to be provided for those that were afraid of undertaking a full code review activity, or simply for those who wanted a quickie until the security review was completed..
For this reason, a parallel project called Bastion was realized in order to provide Java developers with classes that embed security checks in their core, giving them a quick fix without having to change too much code.
Please understand that Bastion will not come close to substituting for robust secure coding, but it will provide some minimal secure coding functionality while full-fledged secure coding is being undertaken in other parts of the application.
Starting from Orizon v0.25, Bastion is a separate JAR file. The latest Bastion version is 0.42 Build 193.
A very simple web application that demonstrates how to use Bastion to fix a very generic Cross Site Scripting attack by changing a single line of code can be found here. To use it, point your browser to http://<domain name>/bastion_test and follow the instructions.
The Bastion test application is built against a very old Orizon version when Bastion was still contained inside of Orizon. Because the current focus of the project is on the Orizon APIs, the Bastion code remains unchanged since April.
A few words need to be said here: there is no intention to reinvent the wheel. The Web is full of libraries that sanitize source code in order to mitigate an attack on a web application. Bastion is just our small contribution to the community; we really hope that you'll appreciate it.
The Library
For a code review tool, the most important factor is its knowledge, which are the security checks that is applied to the source code. No matter how many features a tool has or how fancy is its UI, a poor security check library means that the tool is useless.
Orizon organizes safe coding best practices in XML rules that are contained in files called recipes. The mantra chosen for the project is that "coding is like cooking" and the goal is to choose the correct set of recipes.
Recipes are gathered together in a zip file named Library.
Following is the layout of the knowledge inside of Orizon.
The XML schema
The Orizon XML schema used to describe secure coding checks can be difficult to read. On this page, more details about how an XML rule is built can be found.
Blog
The Orizon blog is proudly hosted by SourceForge here.
Future Development
The first draft of the project roadmap was far too optimistic. Refer to the official Orizon Roadmap page for an updated and more realistic project roadmap.
Presentations
All presentations listed here were given by Paolo Perego.
Owasp Orizon Internals @ Owasp AppSec NY 2008, New York 22-25th September 2008
Owasp Orizon Internals @ Owasp AppSec EU 2008, Ghent 21-22nd May 2008
Owasp Orizon Internals @ Owasp Day Italy 2008, Rome 31st March 2008
OWASP Orizon Project @ SMAU eAcademy, Milan 4-7th October 2006
I will talk to SMAU eAcademy2006 next Saturday 7th October 2006 about code review and safe coding. Here you can find more information (for now, only in Italian). The last part of the speech will be about introducing the Orizon project and giving a development roadmap.
Project Creation
OWASP Orizon Project Created! - 09:24, 2 October 2006 (EDT)
The Open Web Application Security Project is proud to announce the OWASP Orizon Project!
Feedback and Participation
Orizon wants you!
Of course, as an open source project, anybody is welcome to join Orizon, and please do. If you are a skilled C#, Java, or ASP developer and you want to share your experience with these languages, feel free to use the mailing list to contribute to these Orizon-supported languages.
If you are a skilled Java developer why don't you consider writing a bunch of code for Orizon? Or, consider joining the project for documentation, advertising, blog maintenance, etc.
We hope you find the OWASP Orizon Project useful. Please contribute to the project by volunteering for one of the tasks, or by sending your comments, questions, and suggestions to [email protected].
To join the OWASP Orizon Project mailing list or view the archives, please visit the subscription page.
Project Contributors
--thesp0nge 09:47, 2 October 2006 (EDT)
Project Sponsor
Pages in category "OWASP Orizon Project"
This category contains only the following page.
