Posted October 21Oct 21 comment_1131 Would like to update ModSecurity from 2.9.7 to 3.0.12, along with using the Latest OWASP Ruleset 4.0.7 Is there a guide how to accomplish this?
October 22Oct 22 comment_1132 21 hours ago, Starburst said: Would like to update ModSecurity from 2.9.7 to 3.0.12, along with using the Latest OWASP Ruleset 4.0.7 Is there a guide how to accomplish this? Unfortunately, apache does not work with 3.0.x version. Do you use just nginx? In the same way, I have installed in cwpsrv server. I can share the (long) command sequence with you, if would be useful.
October 25Oct 25 comment_1137 On 10/23/2024 at 2:43 AM, Sandeep B. said: any error you're getting with the latest version build with Apache? To use ModSecurity V3 (libmodsecurity), is needed to use the ModSecurity-apache connector. This project is under development and not production-ready. The functionality is not complete, so we cannot use use with Apache HTTP Server. There are a note in that page: "NOTE: This project is not production ready This project should be considered under development and not production ready. The functionality is not complete and so should not be used. With Apache HTTP Server, the recommended version of ModSecurity is v2.9.x. "
November 4Nov 4 Author comment_1143 No, The OWASP 4.x ruleset works with Mod Security 2.9.7 and Apache 2.4.62 The only problem, is notifications are not being sent by LFD from the Mod Security log (something isn't being triggered). Otherwise when I look at the log, attacks are being blocked as they should be.
November 7Nov 7 comment_1147 Quote No, The OWASP 4.x ruleset works with Mod Security 2.9.7 and Apache 2.4.62 The only problem, is notifications are not being sent by LFD from the Mod Security log (something isn't being triggered). Otherwise when I look at the log, attacks are being blocked as they should be. The lastest version of ModSecurity V3 is 3.0.12. It's important doesn't confuse ModSecurity 3.0.x with OWASP ruleset core 3.0.x. Like I said, apache doesn't work fully with ModSecurity 3.0.x. This is documented in Modsecurity site (assumed by OWASP team in july, this year) But I have myself running normally apache with OWASP Ruleset core 4.7.x, since 3.x up to 4.x. Maybe LFD problem can be solved with a few adjusts in ErrorLogFormat directive, to do it work. Edited November 7Nov 7 by Netino
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now