Skip to main content

ModSecurity Rules Per Domain

Comments

12 comments

  • cPRex Jurassic Moderator

    Hey there!  That solution from the article is the only official one I have.  All you're really doing is creating the files/folders necessary for the Apache include system for one particular user, then editing the file, then restarting the service.

    I can't comment on the Configserver ModSec Control tool as that isn't something we make, and I'm not personally familiar with that one.

    0
  • quietFinn

    We use Configserver ModSec Control to disable rules per user/domain.
    You can also disable ModSecurity for all domains by a user.

    0
  • kgs

    @quietFinn And it runs alongside the existing WHM modsec pages just fine?

    0
  • quietFinn

    Yes, no problems whatsoever.

    EDIT:
    Global whitelisting does not seem to work in ConfigServer ModSecurity Control.

     

    0
  • cPRex Jurassic Moderator

    Thanks, quietFinn!!

    0
  • kgs

    Thank you! quietFinn cPRex

     

    0
  • kgs

    Well, that was easy! Quick install, quick implementation. Does exactly what I was hoping. Thanks again!

    0
  • Pietro Leone

    and now ? 

    0
  • cPRex Jurassic Moderator

    Pietro Leone - can you clarify your question a bit?

    0
  • Pietro Leone

    yes sorry

    after EOL cmc what can replace now ?

    0
  • quietFinn

    You can still use and install CMC.

     

    0
  • cPRex Jurassic Moderator

    cPanel has always included the OWASP ruleset which can be installed through WHM >> ModSecurity Vendors.  That would be the only *official* recommendation I would have as other vendors would be third-party and not something we create.

    0

Please sign in to leave a comment.