In June 2010, Trustwave acquired Breach Security, which brought with it the popular Open-Source Web Application Firewall ModSecurity for Apache. At that time, Trustwave relicensed the code under the Apache license. This relicensing allowed more public participation in the project, and 2012 saw the release of an IIS port from Microsoft and a port for Nginx.
Despite that, porting the Apache module to other web platforms was time-consuming and expensive, so in 2015, Trustwave began a complete rewrite of ModSecurity from the ground up. This new modular architecture was called libmodsecurity, aka ModSecurity 3.0, and was introduced to the public in 2018.
Eventually, all things change, and Trustwave is no different. With a change in our business focus, we announced the End-of-Sale (EOS) for Trustwave support of ModSecurity, which took effect on August 1, 2021. The time has come for the End-of-Life (EOL) of support, taking place on July 1, 2024.
It's been an incredible 14 years taking care of ModSecurity and watching it and its community grow. However, there is no need for handwringing since custodianship of the code has been transferred to the Open Worldwide Application Security Project (OWASP). We have no doubt the project is in good hands.
Overview for rules released by Trustwave SpiderLabs in June for ModSecurity Commercial Rules package. The rules are available for versions 2.9.x and 3.x of ModSecurity.
ModSecurity Commercial Rules detect attacks or classes of attacks on web applications and their components as well as provide virtual patches for public vulnerabilities.
All the rules released this month are available for download and can be configured using the ModSecurity Dashboard. The rules are associated with the default profile and enabled for all licensed servers. To verify the rules were successfully downloaded by ModSecurity, log in to the ModSecurity Dashboard and verify the server "Last seen" date, which indicates the last successful download for the specified server.