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"

From OWASP
Jump to: navigation, search
(The library: enhance English grammar)
 
(43 intermediate revisions by 9 users not shown)
Line 1: Line 1:
[[:Category:OWASP Project|Click here to return to OWASP Projects page.]]<br>
+
=Main=
[[:Project Information:template Orizon Project|Click here to see (& edit, if wanted) the template.]]  
+
{|
{{:Project Information:template Orizon Project}}
+
|-
 +
! width="700" align="center" | <br>
 +
! width="500" align="center" | <br>
 +
|-
 +
| align="right" | [[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]]  
 +
| align="right" |
  
== 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'''.
+
==OWASP Orizon Project==
  
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.
+
OWASP Orizon is a source code security scanner designed to spot vulnerabilities in J2EE web applications, Android code and generally speaking in Java written source code.
  
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...
+
==Description==
  
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.
+
Owasp Orizon is a source code static analyzer tool designed to spot security issues in Java applications.
  
Orizon must give thanks to Findbugs, the OWASP LAPSE Project, RATS, and Flawfinder for ideas and inspiration.
+
Owasp Orizon mission is to provide people an opensource tool, helping them in reviewing:
  
The Orizon project, hosted by Sourceforge, is [http://orizon.sourceforge.net here].
+
* single Java classes
 +
* Java standalone tools packed in JAR files
 +
* web applications packed in EAR / WAR files
 +
* Android APK applications
  
== Goals ==
+
It was a dark and stormy night in Milan, Italy. It was 2006 and I felt the need of something helping me in reviewing other people java source code. So Owasp Orizon born and grew up as security tool trying to parse Java source code, building an Abstract Syntax Tree and spot for unsafe calls in the code.
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 [https://www.owasp.org/index.php/Category:OWASP_Code_Review_Project OWASP Code Review Guide].
+
In the very beginning Owasp Orizon was a sort of enhanced grep tool. In 2008, I started supporting PHP programming language but the initial boost disappeared. After being in love with other programming languages and technolgies, eight years later, in 2017 I kickstarted the project again from scratch.
  
== Documentation ==
+
==Licensing==
 +
OWASP Orizon is an opensource tool. It is licensed under the [http://www.apache.org/licenses/LICENSE-2.0 Apache 2 License].
  
Available online is an  [http://downloads.sourceforge.net/orizon/The_Owasp_Orizon_Project_Internals_v2.2.ppt?use_mirror=osdn Orizon presentation] given at  [http://www.owasp.org/index.php/OWASP_AppSec_Europe_2008_-_Belgium OWASP AppSec EU 2008] in Ghent, May 2008.
+
== Quick Start ==
  
== Download ==
+
See project [https://github.com/thesp0nge/owasp-orizon GitHub home page]
The source code is in a Subversion repository and hosted at sourceforge.net.
 
  
The latest release is [http://downloads.sourceforge.net/orizon/orizon-1.0.jar?use_mirror=heanet 1.0].
+
== Project Resources ==
  
=== Dawn ===
+
[https://owasporizon.wordpress.com Blog]
  
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.  
+
[https://github.com/thesp0nge/owasp-orizon  Code] | [https://github.com/thesp0nge/owasp-orizon/releases Binaries]
  
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.
+
[https://github.com/thesp0nge/owasp-orizon/issues Issue Tracker]
  
Dawn was implemented in Orizon release 0.45pre1.
+
== Project Leader ==
  
=== Bastion ===
+
Paolo Perego<br/>
 +
[mailto:[email protected] email] [https://twitter.com/thesp0nge/ twitter] [https://codiceinsicuro.it blog ]
  
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..
+
== News and Events ==
 +
* [Spring 2017] - [http://owaspsummit.org/Working-Sessions/Project-Summit/Owasp-Orizon-Reboot.html Owasp Orizon kickstart session]
 +
* [13 September 2016] - Paolo Perego take back project leadership, kickstarting Owasp Orizon again
 +
* [February, 2014] - Greg Disney-Leugers adopted the OWASP Orizon project.
 +
* [November 2009] - we started moving from current release to the next major bump (v2.0) that will happen next June 2010 during Owasp AppSEC conference in Stockholm.
  
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.
+
== Roadmap and Getting Involved==
  
Please understand that Bastion will not come close to substituting for robust security coding, but it will provide some minimal secure coding functionality while full-fledged secure coding is being undertaken in other parts of the application.
+
Owasp Orizon kickstart is scheduled during the upcoming [http://owaspsummit.org/Working-Sessions/Project-Summit/Owasp-Orizon-Reboot.html Owasp Summit 2017]
  
Starting from Orizon v0.25, Bastion is a separate JAR file.The latest Bastion version is
+
Some intended milestones to be putted in roadmap are:
[http://downloads.sourceforge.net/orizon/bastion-0.42-b193.jar?use_mirror=heanet 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
+
* Spring 2017 - Defining the team and overall goals
[http://downloads.sourceforge.net/orizon/bastion_test.war?use_mirror=heanet here]. To use it, point your browser to ''http://<domain name>/bastion_test'' and follow the instructions.
+
* Autumn 2017 - First alpha release
 +
* Winter 2017 - Second alpha release
 +
* January 2018 - First beta
  
  
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.
+
==Classifications==
  
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.
+
  {| width="200" cellpadding="2"
 +
  |-
 +
  | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
 +
  | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]] 
 +
  |-
 +
  | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
 +
  |-
 +
  | colspan="2" align="center"  | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
 +
  |-
 +
  | colspan="2" align="center"  | [[File:Project_Type_Files_TOOL.jpg|link=]]
 +
  |}
  
== 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 [http://www.owasp.org/index.php/OWASP_Orizon_Project_XML page], more details about how an XML rule is built can be found.
 
  
== Blog ==
+
=Project About=
Owasp blog is now proudly hosted by sourceforge [http://orizon.sourceforge.net/blog here].
+
{{:Project Information:template Orizon Project}} 
  
 +
__NOTOC__ <headertabs />
  
 
+
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]
== Future Development ==
 
This is the updated project RoadMap. I was too optimistic in my first roadmap draft. This is a more realistic timeline...
 
 
For an up to date roadmap you have to refer to official Orizon Roadmap [http://orizon.sourceforge.net/roadmap.html page]
 
 
 
== Speeches ==
 
 
 
'''Owasp Orizon Internals @ Owasp AppSec NY 2008, New York 22-25th September 2008'''
 
[http://www.owasp.org/index.php/OWASP_NYC_AppSec_2008_Conference Orizon@AppSec NY 2008]
 
 
 
'''Owasp Orizon Internals @ Owasp AppSec EU 2008, Ghent 21-22nd May 2008'''
 
[http://www.owasp.org/index.php/AppSecEU08_The_OWASP_ORIZON_project Orizon@AppSec EU 2008]
 
 
 
'''Owasp Orizon Internals @ Owasp Day Italy 2008, Rome 31st March 2008'''
 
[http://www.owasp.org/images/5/54/Owaspday2Perego.ppt Orizon@Owasp Day in Italy]
 
 
 
'''OWASP Orizon Project @ SMAU eAcademy, Milan 4-7th October 2006'''
 
I will talk to [http://www.webb.it SMAU eAcademy2006] next saturday 7th October 2006 about code review and safe coding. [http://webb.it/event/eventview/5772/1/0,0/code_review_e_principi_di_programmazione_sicura Here] you can find more informations in italian only by now.
 
Last part of the speech will be about introducing Orizon project, giving development roadmap
 
 
 
== 2.10.2006 ==
 
 
 
'''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 opensource project, '''anyone''' is welcome tho join Orizon, and please do it.
 
If you are a C#, Java or ASP skilled developer and you want to share your experience with such languages feel free to use mailing list to contribute in Orizon supported languages.
 
 
 
If you are a Java skilled developer why don't you think about writing some bunch of codes for Orizon?
 
 
 
If you write quite well or, it's not so difficult, better than me, please think about joining the project for documentation, advertising, blog maintenance ...
 
 
 
We hope you find the OWASP Orizon Project useful. Please contribute to the Project by volunteering for one of the Tasks, sending your comments, questions, and suggestions to [email protected]. To join the OWASP Orizon Project mailing list or view the archives, please visit the [http://lists.owasp.org/mailman/listinfo/owasp-orizon subscription page.]
 
 
 
== Project Contributors ==
 
--[[User:Thesp0nge|thesp0nge]] 09:47, 2 October 2006 (EDT)
 
 
 
== Project Sponsor ==
 
 
 
 
 
[[Category:OWASP Project]]
 
[[Category:OWASP Tool]]
 
[[Category:OWASP Download]]
 

Latest revision as of 15:15, 11 May 2017



OWASP Inactive Banner.jpg

OWASP Orizon Project

OWASP Orizon is a source code security scanner designed to spot vulnerabilities in J2EE web applications, Android code and generally speaking in Java written source code.

Description

Owasp Orizon is a source code static analyzer tool designed to spot security issues in Java applications.

Owasp Orizon mission is to provide people an opensource tool, helping them in reviewing:

  • single Java classes
  • Java standalone tools packed in JAR files
  • web applications packed in EAR / WAR files
  • Android APK applications

It was a dark and stormy night in Milan, Italy. It was 2006 and I felt the need of something helping me in reviewing other people java source code. So Owasp Orizon born and grew up as security tool trying to parse Java source code, building an Abstract Syntax Tree and spot for unsafe calls in the code.

In the very beginning Owasp Orizon was a sort of enhanced grep tool. In 2008, I started supporting PHP programming language but the initial boost disappeared. After being in love with other programming languages and technolgies, eight years later, in 2017 I kickstarted the project again from scratch.

Licensing

OWASP Orizon is an opensource tool. It is licensed under the Apache 2 License.

Quick Start

See project GitHub home page

Project Resources

Blog

Code | Binaries

Issue Tracker

Project Leader

Paolo Perego
email twitter blog

News and Events

  • [Spring 2017] - Owasp Orizon kickstart session
  • [13 September 2016] - Paolo Perego take back project leadership, kickstarting Owasp Orizon again
  • [February, 2014] - Greg Disney-Leugers adopted the OWASP Orizon project.
  • [November 2009] - we started moving from current release to the next major bump (v2.0) that will happen next June 2010 during Owasp AppSEC conference in Stockholm.

Roadmap and Getting Involved

Owasp Orizon kickstart is scheduled during the upcoming Owasp Summit 2017

Some intended milestones to be putted in roadmap are:

  • Spring 2017 - Defining the team and overall goals
  • Autumn 2017 - First alpha release
  • Winter 2017 - Second alpha release
  • January 2018 - First beta


Classifications

Owasp-incubator-trans-85.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files TOOL.jpg

|}





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

License
Creative Commons Attribution Share Alike 3.0

Project Type
Tool

Sponsor
OWASP SoC 08
Release Status Main Links Related Projects

Beta Quality
Please see here for complete information.

The Owasp OrizonProject in Power Point
Orizon Safe coding and beyond - Word File
Orizon 1.19 - The Latest Release
Orizon internal draft
Orizon site at sourceforge
Orizon blog

OWASP Code Review Guide


Pages in category "OWASP Orizon Project"

This category contains only the following page.