ModSecurity’s ruleset is changed automatically from Atomic Advanced to Custom when Imunify360 is installed

Symptoms

• Atomic Advanced ruleset in Plesk is automatically changed to Custom;

• The following content could be found in /etc/httpd/conf/modsecurity.d/rules/custom/RELEASE:

  {
  ... 
  "vendor": "Imunify360",
  ... 
  }

• Imunify360 can be presented on the server.

  Note: Imunify360 can be installed not via Plesk

Cause

A conflict between Imunify360 and Atomic Advanced rulesets.

If Imunify360's custom ruleset is off, it loses a significant part of the functionality, and can’t fully protect the server. So the ModSecurity is auto-switched to Imunify360‘s Custom ruleset upon scheduled automatic updates of Imunify360. This is the expected behavior.

Resolution

As ModSecurity in Plesk can’t handle two independent rulesets, it is possible to use only one of them.

So only one product should be installed (Atomic Advanced or Imunify360).