WAS Protect update (Aug 19)

I have completed a large part of the WAS Protect reference
implementation (a Java Servlet Filter). The finished part is the
backend, which allows the rule engine to be built on top. I've also
tidied the spec and created the first version of the schema (attached
to this email, together with an rule example). I will look into
improving the schema to reference multiple rule databases and to
allow rule versioning.

I expect to have a fully-functional version ready in two to three weeks,
so (with some buffer added to that) I'm giving myself a deadline to
have everything ready for September 20.

One thing I cannot do by myself is test the software. The filter
must be tested with real-life applications running on different
servlet containers. The thing that needs to be tested is the
transparency. When installed with no rules, the filter must not
interfere with the application in any way. The Servlet specification
leaves some things undefined so this is where differences between
containers may come to light.

I would appreciate if some of you could help with the testing.

-- 
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]