Difference between revisions of "OWASP WebScarab Project Roadmap"

From OWASP
Jump to: navigation, search
 
m (WebScarab NG category addded)
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
 
The project's overall goal is to...
 
The project's overall goal is to...
  
   Mission statement here
+
   Provide a robust '''tool''' that assists the user to identify weaknesses in
 +
  HTTP(S) based applications.
 +
 
 +
  In its simplest form, it provides an intercepting proxy that allows the user
 +
  to observe and manipulate requests sent to the server, and the responses
 +
  returned from the server.
  
 
In the near term, we are focused on the following tactical goals...
 
In the near term, we are focused on the following tactical goals...
  
# one
+
# migration from the current messy code base to a hopefully cleaner implementation, based on the Spring Framework and the Spring Rich Client platform. This will provide a database-backed archive, as well as a more user-friendly user interface, with input validation, and proper feedback
# two
+
# reimplementing the current functionality of WebScarab in the "next generation" code
# three
+
  
Here are the current tasks defined to help us achieve these goals
 
 
* Gather existing presentations and email messages and pull ideas into OWASP
 
 
{{Template:Stub}}
 
  
 
[[Category:OWASP WebScarab Project]]
 
[[Category:OWASP WebScarab Project]]
 +
[[Category:OWASP WebScarab NG Project]]

Latest revision as of 12:23, 23 January 2011

The project's overall goal is to...

 Provide a robust tool that assists the user to identify weaknesses in 
 HTTP(S) based applications. 
 
 In its simplest form, it provides an intercepting proxy that allows the user 
 to observe and manipulate requests sent to the server, and the responses 
 returned from the server.

In the near term, we are focused on the following tactical goals...

  1. migration from the current messy code base to a hopefully cleaner implementation, based on the Spring Framework and the Spring Rich Client platform. This will provide a database-backed archive, as well as a more user-friendly user interface, with input validation, and proper feedback
  2. reimplementing the current functionality of WebScarab in the "next generation" code