My server runs the following ModSecurity Rules:
Imunify360 LiteSpeed Rule Set (Minimized ModSec Ruleset)
COMODO ModSecurity LiteSpeed Rule Set
I had to disable the following rule set because it was causing a LOT off false positives within our WordPress websites, to the extent that we...
We have Mod Security enabled, and using mod sec rules developed and provided by our data center. It has worked out very well, but there are some things we like about the OWASP Core Rule Set (CRS) that cPanel is making available to us. I'm investigating enabling these rules, either in...
Hi all, this may be nothing but I wanted to post my experience this morning with our website suddenly refusing PUT requests. This morning I visited the WHM interface and got an upgrade popup saying that new ModSecurity rules would be installed (my memory is not perfect but it definitely...
I have version 92.0.4 and I see something strange.
When I go to an account in cPanel and then SECURITY> ModSecurity says:
But I'm sure the modsecurity is enabled on the server. I test it and blocks successful rules in domains, server etc. It's something wrong with this info inside...
I have added exclude rule to ModSecurity in /etc/apache2/conf.d/modsec/modsec2.user.conf to whitelisting Googlebot from being blocked, but it doesn't work. Googlebot will still blocked if accessing to robots.txt.
SecRule REMOTE_ADDR "^66\.249\.xxx\.xxx$"...
Is there a way to show ModSecurity Hit List to customers in cPanel (not in WHM)? And also, is there any plugin to allow customers edit their own ModSecurity rules (disable some of them on specific URL, just like ConfigServer ModSec Control but at the cPanel side) ?
cPanel & WHM Version 92 to RELEASE!
We are happy to announce that cPanel, L.L.C. has released cPanel & WHM Version 92 to the RELEASE tier! Some highlights of this release can be found below, but please check the Release Site for more information.
Experimental ImageMagick for CentOS 8
EasyApache 4 November 23 Release
We are happy to announce that cPanel, L.L.C. has released an update for EasyApache 4! Take a look at some highlights below, and then join us on Discord or Reddit to talk about this update and much more.
I have an issue with ModSecurity. Request body and file temporary file on /tmp isn't completely cleared, so I have to clean up very regularly /tmp to avoid it filling up all my disks. Would you know why it have this strange comportment?
On the apache log, I found only this as relevant...
I'm running tests on Centos 8.2 and Cpanel v92. When I install mod_security v3 and want to add custom rules from the edit rules section, I see the following error. None of the SecConnEngine, SecRuleEngine, SecRule codes are recognized.
Error: The system could not validate the new Apache...
i want to add Geolocation db in modsecurity config...
looking to the description:
so it appears ModSecurity accepts only GeoIp v1 format
in the maxmind i found only Geoip2 database...
any suggestions please??thanks a lot
Hello, I know cPanel is loaded with questions similar to what I'm seeing. But I started using (just today/yesterday) modsecurity rules. I'm seeing some permission denied errors for GeoIP and other and I think it is because I don't have a db path in the configuration section for modsecurity...
Are modsec rule ID's sequential? Like is their preference linear? If I want to whitelist an IP does my ID have to be as low as possible (eg. 1 thru say 200)? Or can I make it like 60000 and it will still work?
Does any of you have any experience yet with the newly released OWASP ModSecurity Core Rule Set v3.3 that was released last month?
(OWASP ModSecurity Core Rule Set – The 1st Line of Defense Against Web Application Attacks)
Worth trying out?
Does anyone know where the notation is made within the modsec configuration when a user disables modsecurity for all or any domain within their cPanel?
I've looked in the expected locations (/etc/apache2/conf.d/userdata etc.) without success.
We just need to be able to produce a...
When I run "/usr/local/cpanel/scripts/modsec_vendor update OWASP3" I get the following errors:
The system failed to update the vendor from the URL http://httpupdate.cpanel.net/modsecurity-rules/meta_OWASP3.yaml
warn [modsec_vendor] The system failed to update the vendor from the URL...
I've searched this for thousands of topics and haven't found it, oddly enough.
I would like to know from any of you how can I clear ModSecurity logs?
I already deleted modsec_audit.log, but the logs continue. In my case I have more than 20,000 pages of logs.
All of our servers are reporting identical update failures:
The cPanel & WHM update process failed for the following reason:
Maintenance ended; however, it did not exit cleanly (256). The following events were logged: “scripts/modsec_vendor”. Review the update logs to determine why the update...
Please, how could I limit the action of this rule only in wp-login.php and xmlrpc.php?
SecRule REQUEST_HEADERS:User-Agent "@contains gecko" "id:5000501,t:none,t:lowercase,deny,nolog,msg:'BAD BOT - Detected and Blocked. '"