Imunify360 dashboard displays "Medium" or "Poor" protection status with messages:
"Medium: Server has some issues" or "Poor: Server is unprotected"
Environment supported by Imunify360.
The solution, in this case, will be following the dashboard recommendations and enabling the suggested feature(s) to update the server protection status.
Let's consider the example below:
- You have the following status and recommendation inside the Imunify360 dashboard
requiring "Connection-based DoS" Protection and "Binary (ELF) malware detection" features enabled.
- Once proceeding with the necessary changes which can be done via the Imunify360 UI settings or CLI, the status will need some time to reflect the changes. The dashboard is updated once a day (the corresponding note is shown on the dashboard), so the protection status won't be updated immediately.
- After the changes are reflected, the protection status will be changed:
Imunify promotes optimal security configuration. The following features additionally will be promoted using Dashboard recommendations and Advisor:
|Malware Database Scanner||+||medium||+|
|Connection-based DoS Protection||+||medium|
WordPress Account Compromise Prevention
|Automatically scan all modified files||+||medium||+|
|Automatically scan any file uploaded using web||+||medium||+|
|Automatically scan any file uploaded using ftp||+||medium||+|
|Optimize real-time scan||+||medium||+|
|ELF malware detection||+||optional|
|Kill mode for Proactive Defense||+||important||+|
Other variables like the lack of OSSEC events can also trigger the poor protection status, so it is advised to make sure that the logs are present and also some general packages like rsyslog are installed on a system.
The above features deserve to be promoted since switching them on will reduce the infection rate and enhance protection.