Test whether mod_security is actually working

curl -ks -o /dev/null -w '%{http_code}' "https://something.example.com/foo?username=1'%20or%20'1'%20=%20'"

If you get a 403, then ModSecurity is working as expected.

Mod_Security is enabled automatically after you select it and build Apache via EasyApache. Assuming no third-party applications are installed to manage it, you can manage its rules at:

“WHM >> Plugins >> Mod_Security”

You will typically see a “406” error code in the Apache error log when Mod_Security blocks a request.

Related posts

Latest posts

Leave a Comment

Leave a Reply

Your email address will not be published. Required fields are marked *