Difference between revisions of "OWASP Validation Documentation Project"

From OWASP
Jump to: navigation, search
 
Line 3: Line 3:
 
=News=
 
=News=
  
  '''OWASP Validation Documentation rough draft released! - 18:22, 4 August 2006 (EDT)'
+
  '''OWASP Validation Documentation rough draft released! - 18:22, 4 August 2006 (EDT)'''
  
 
The OWASP Validation Project is pleased to announce the immediate availability of the OWASP Validation Documentation rough draft. The documentation is the result of a tireless effort to provide clear design goals when implementing input validation in web applications. The following is the document abstract:
 
The OWASP Validation Project is pleased to announce the immediate availability of the OWASP Validation Documentation rough draft. The documentation is the result of a tireless effort to provide clear design goals when implementing input validation in web applications. The following is the document abstract:
  
 +
''Correctly implementing an input validation mechanism for a custom application is extremely difficult. It is then inevitable that large web applications will fall victim to this class of vulnerability. Therefore, a developer should have a clear understanding of how to successfully design and implement a reusable input validation mechanism for their applications. The OWASP Validation Documentation attempts to fulfill this requirement by providing the necessary design principals as well as an example implementation. This document is structured such that if a developer were to incorporate all of the presented design principals, then the result will be a complete and reusable input validation engine.''
  
  
 
[[Category:OWASP Validation Project]]
 
[[Category:OWASP Validation Project]]

Revision as of 17:32, 4 August 2006

Overview

News

OWASP Validation Documentation rough draft released! - 18:22, 4 August 2006 (EDT)

The OWASP Validation Project is pleased to announce the immediate availability of the OWASP Validation Documentation rough draft. The documentation is the result of a tireless effort to provide clear design goals when implementing input validation in web applications. The following is the document abstract:

Correctly implementing an input validation mechanism for a custom application is extremely difficult. It is then inevitable that large web applications will fall victim to this class of vulnerability. Therefore, a developer should have a clear understanding of how to successfully design and implement a reusable input validation mechanism for their applications. The OWASP Validation Documentation attempts to fulfill this requirement by providing the necessary design principals as well as an example implementation. This document is structured such that if a developer were to incorporate all of the presented design principals, then the result will be a complete and reusable input validation engine.