ModSecurity: Roadmap

This page lists our plans for the future versions of ModSecurity.

After 2.5.0

• Better reverse proxy deployment documentation. Embedded deployment is just one option. Coupled with Apache configured in reverse proxy mode, ModSecurity turns into a network-based web application firewall.
• Pre-configured VMware images based around Apache and ModSecurity will make it easier for new users to start playing with the technology.
• Best practices and cookbook-style documentation. We understand better documentation is needed to make full use of ModSecurity.

Version 3.0 and Beyond

• Portability. Focus on portability, making ModSecurity able to work with web servers other than Apache.
• Release an IIS/ISA version of ModSecurity.
• Learning. ModSecurity works well when you know exactly what you want to do. We want to expand what it's capable of so it can help in situations where manual configuration is not an option.
• Configuration reload without restart.
• Code modularity. We want to make it possible for others to contribute new functionality to ModSecurity without having to learn everything about its internals.
• Define data formats, which will allow related products to build on top of what ModSecurity already provides.
• Scripting. Improve performance of the scripting implementation (Lua) and further integrate scripting into the engine.
• Rule writing in C, for when you need that extra bit of flexibility and performance.