I read some issues on github where people didn't find it very accurate. I've also looked at the requests in my logs, and the default settings would block a whole lot of stuff, including (I suspect) requests coming from the IP of the server itself (typically wp-cron calls). I will skip it for now I think.I have mixed results with the DOS protection of coreruleset. It does block some "1 IP" flood attacks but not all. It's hard to monitor when it does or doesn't "trigger" a block.
I was too, until a recent change by DA forcibly installed 4.19.0 on many of my servers, which was fun..I'm still on OWASPv3.7 for production![]()
That makes sense.but I think I would put custom modifications in REQUEST-900-EXCLUSION...conf either above or directly below the IncludeOptional /opt/modsecurity.plugins/*/plugins/*-config.conf statement (depending on the contents of the plugin config file you might want to disable or "overwrite").