Category:OWASP Validation Project
Most web application platforms do not include features to validate user input. This leaves many organizations to craft their own validation mechanisms, often incomplete, flawed, and inefficient.
The OWASP Validation Project was created to provide guidance and tools related to validation. Our philosophy is that validation is required for every part of the HTTP request, including headers, query string, cookies, form fields, and hidden fields.
Currently, there are several projects underway to create validation technologies for various platforms. The long term goal is to provide a detailed guide for implementing proper input validation as well as provide validation engines for popular web application environments.
The OWASP Validation Project was created by Jeff Williams and is currently maintained by Eric Sheridan.
Project Stinger 2.0 is Underway! - 11:44, 10 July 2006 (EDT)
One of the goals of the OWASP Validation Project is updating and improving the Java validation engine, Stinger. This update will include the many submitted ideas/patches over the past several years on top of a completely rewritten engine. If you have any ideas/patches that you would like to have reviewed for submission, please contact Eric Sheridan.
OWASP Validation Finds a New Project Lead - 11:44, 10 July 2006 (EDT)
Thanks to Jeff Williams, Eric Sheridan is now the lead of the OWASP Validation Project. The project will be moving forward in the next few weeks. Refer to the road map for short term goals and deadlines. Stay tuned!
The three major goals of the OWASP Validation Project are the following:
- build an input validation guide
- provide and implement input validation mechanisms for various platforms
- rewrite Stinger to incorporate the design principals in the guide
The OWASP Validation Roadmap contains the latest information as to project goals and targeted release dates.
Guide to Building Input Validation
One of the major goals of the OWASP Validation Project is to provide clear and detailed documentation on building input validation mechanisms for your web application needs. In the near future, this section will contain such documentation. Check back soon!
The second major goal of the OWASP Validation Project is to provide input validation mechanisms which adhere to one or more of the design principals outlined in the 'Input Validation Guide'. If you have a project which fits this requirement, please submit it via email to the project lead.
The Stinger library is a full J2EE Validation Engine which strongly adheres to the principal's outline in the 'Input Validation Guide'. More information can be found on the Stinger Project page at http://www.owasp.org/index.php/OWASP_Stinger_Project
One of the goals of the OWASP Validation Project is to implement Stinger 2.0 on the .NET platform. If you are interested in leading this project, please contact Eric Sheridan. Please refer to the project road map for an estimated time of arrival.
The PHP Filters Project provides an API framework for validating input for various purposes. The project is still being ported from the previous OWASP Site. Check back soon!
OWASP Recently released the PHP Top 5, an article illustrating several attack vectors against PHP applications. The majority of the PHP Top 5 can be alleviated with a solid and well defined validation mechanism.
This category has the following 2 subcategories, out of 2 total.
Pages in category "OWASP Validation Project"
The following 13 pages are in this category, out of 13 total.
Media in category "OWASP Validation Project"
This category contains only the following file.