Is Imunify360 compatible with ConfigServer ModSecurity Control (CMC)?

[cldlnx.frm]

Before installing Imunify360 we used CMC to manage mod_security rule whitelists on a server-wide and per-domain basis.

Can we still use CMC to do that with Imunify360? If we make an exception/whitelist for a modsec rule in CMC, will it work with Imunify360?

Thanks!

If CMC does not work with Imunify360, then how can we make a domain-specific exception to a certain modsec rule(s)?

Thanks.

[skhristich]

Hello,
Thank you for reaching out! According to the SMS description, there should be no conflicts.
Please let me know if you have a conflict and you need our help. Thank you in advance!

[henri]

In Imunify360, how can we make a domain-specific exception to a certain modsec rule(s)?

[skhristich]

Thanks for continuing. This information in our documentation will be helpful https://docs.imunify360.com/dashboard/#disabled-rules
Could you clarify what problems you have with the rules and our specialists will be able to check the problem, just create a ticket here https://cloudlinux.zendesk.com/hc/en-us/requests/new. It will be better than disabling the rules.

[henri]

Thanks. When adding hostname to the list of domains for modsec disabled rules... can we use "*" symbol?

For example, if customer has:

http://www.domain.com

domain.com
subdomain.domain.com

Can we put *.domain.com into the list of domains for disabled rules? Or if we put "domain.com" into the box.. will that automatically disable the modsec rule for all the subdomains, too?

[skhristich]

Hello,
Imunify360 works with both CMC and CSF, there is also an integration mode with CSF, described here:

https://docs.imunify360.com/ids_integration/#csf-integration

Also when you install Imunify360, the existing rulesets for Modsecurity are disabled and the Imunify360 ruleset is installed by default.
If you have any other questions, feel free to ask here. Thank you for contacting us.