You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<tr><td><spanclass="notranslate">enable: True</span></td><td># allows to enable or disable option that moves IPs to <spanclass="notranslate">Gray List</span> if the ModSecurity rule is triggered</td></tr>
118
120
<tr><td><spanclass="notranslate">max_incidents: 2</span></td><td># set a number of repeats of the ModSecurity incident from the same IP for adding it to <spanclass="notranslate">Gray List</span></td></tr>
<td># allows to enable (<spanclass="notranslate">True</span>) or disable (<spanclass="notranslate">False</span> – the default value) automatic malicious file restore from backup if a clean copy exists,
135
138
otherwise <spanclass="notranslate"><em>default_action</em></span> is applied</td></tr>
@@ -184,24 +187,29 @@ Scanner's behaviour is based on other scan optimizations, therefore it is better
<td># enables resetting passwords for compromised cPanel accounts. Upon activating this functionality, our platform will detect instances where a cPanel account password has been breached and will subsequently prevent access using the previous password. End-users will then be prompted to create a new password via the <ahref="https://docs.cpanel.net/knowledge-base/security/how-to-reset-a-cpanel-account-password/"target="_blank">cPanel password reset process</a>.</td></tr>
<td># if you don't want iptables\ip6tables rules to be applied to specific NICs, list them here (e.g <spanclass="notranslate">[eth1, eth2]</span>)</td></tr>
<td># defines the default state of ports which is not explicitly set by user (<spanclass="notranslate"><em>denied</em></span> by default or <spanclass="notranslate"><em>allowed</em></span> by default). Currently only <spanclass="notranslate"><em>allowed</em></span> is supported</td></tr>
<td># enable (<spanclass="notranslate">True</span> (default)) or disable (<spanclass="notranslate">False) Blamer</span>. See also: <ahref="https://blog.imunify360.com/forcibly-enable-blamer"target="_blank">How to forcibly enable Blamer for all users on the server</a>.</td></tr>
<td># available modes:<ul><li><spanclass="notranslate">KILL</span></li><li><spanclass="notranslate">DISABLED</span></li><li><spanclass="notranslate">LOG</span> (default)</li></ul></td></tr>
<td># enable (<spanclass="notranslate">True</span>) or disable (<spanclass="notranslate">False (default)) PHP Immunity </span> (allows to automatically detect & patch vulnerabilities in software at the Proactive Defense level preventing re-infections through the same vulnerability). By enabling this feature, Blamer will be enabled as well and Proactive Defence switched into the KILL mode.</td></tr>
<tr><td><spanclass="notranslate">day_of_month: <next day after installation></span></td>
268
284
<td># when the background scan shall start, day of the month. Can be from 1 to 31, the default value is the <next day after installation>.</td></tr>
@@ -274,7 +290,8 @@ to request Anti-bot Challenge again</td></tr>
274
290
<td># interval of scan. Supported values: strings <spanclass="notranslate">`NONE`</span> (no scan), <spanclass="notranslate">`DAY`</span>, <spanclass="notranslate">`WEEK`</span>, <spanclass="notranslate">`MONTH`</span>, the default value is <spanclass="notranslate">`MONTH`</span></td></tr>
<td># enable (<spanclass="notranslate">True</span>) the Malware Database Scanner - a database antivirus with automated malware detection and clean-up of web applications. Requires MariaDB/MySQL DB management system version 5.5. Recommended version is 5.6+. Note, that only WordPress, Joomla, and Magento databases are supported now.</td></tr>
362
+
</tbody>
344
363
</table>
345
364
346
365
<spanclass="notranslate">Active Response</span> is an ossec-driven (IDS) feature of Imunify360 which has been re-engineered to make it capable of blocking access to a specific server port being attacked.
@@ -30,19 +31,17 @@ In the config file it is possible to set up ImunifyAV(+) configuration. The foll
30
31
<td># allows to use (True) the regex matching Hyperscan library in Malware Scanner to greatly improve the scanning speed. True is the default value. Hyperscan requires its own signatures set that will be downloaded from the files.imunify360.com and compiled locally.<br><b>Platform requirements</b>:<br>* Hyperscan supports Debian, Ubuntu and CentOS/CloudLinux 7 and later.<br>* SSE3 processor instructions support. It is quite common nowadays, but may be lacking in virtual environments or in some rather old servers.</td></tr>
<td># enable (<spanclass="notranslate">True</span>) scan of the system and user crontab files for malicious jobs. The default value is <spanclass="notranslate">True</span>.</td></tr>
<tr><td><spanclass="notranslate">day_of_month: <next day after installation></span></td>
47
46
<td># when the background scan shall start, day of the month. Can be from 1 to 31, the default value is the <next day after installation>.</td></tr>
@@ -70,14 +69,14 @@ In the config file it is possible to set up ImunifyAV(+) configuration. The foll
70
69
<td># enable (<spanclass="notranslate">True</span>) or disable (<spanclass="notranslate">False</span>) (the default value) “scan” action in the UI of the end-user.</td></tr>
71
70
<tr>
72
71
<tdwidth="250px;"><spanclass="notranslate">upgrade_button: True</span></td><td># enable (<spanclass="notranslate">True</span> - the default value) or disable (<spanclass="notranslate">False</span>) the Imunify upgrade button.</td></tr>
0 commit comments