Imunify360 shows each cPanel user a security page for their own account. As root you decide how much they can do there, and who gets notified when malware or attacks are detected. Getting this right reduces support tickets and speeds up cleanups.
MdmHost handles this on its hosting plans. This guide is for administrators of their own cPanel server with root access.
Before you start
- Imunify360 installed (see installing Imunify360).
- Contact emails set for the server and accounts.
User permissions
- Go to WHM → Plugins → Imunify360 → Settings → General (permissions may be in a Permissions section or tab).
- Review the options, which typically include:
- Allow users to run on-demand scans.
- Allow users to clean up and restore files.
- Allow users to manage the ignore list.
- Show Proactive Defense events to users.
- Save.
| Option | Recommendation |
|---|---|
| On-demand scans | Allow; lets users verify cleanups themselves |
| Cleanup / restore | Allow; backups make it reversible |
| Ignore list | Allow for experienced customers, or keep admin-only to avoid users hiding real malware |
| Proactive Defense view | Allow; helps developers understand blocks |
What users see is described in the Imunify360 overview and the ignore list guide.
Notifications
- Go to Imunify360 → Settings → Notifications.
- For each event type, such as Real-time malware found, Scan completed, Script blocked, choose who is notified: admin email, and/or the account's contact email.
- Set the admin email address and a sensible throttle period so a mass infection does not send hundreds of emails.
- Save and trigger a test detection, for example with the EICAR test file, to confirm delivery.
Tip: Notify users about malware in their own account. They fix the cause (outdated plugins, weak passwords) faster when they hear about it directly.
Reseller visibility
Depending on version, resellers may see Imunify360 for their customers in WHM. Decide whether to allow it; it helps resellers support their own customers without escalating every detection.
Keep the noise down
- Use automatic cleanup so most detections need no action (see cleanup).
- Send admin notifications to a shared mailbox or ticket system, not a personal inbox.
- Review the incident list weekly rather than reacting to every email (see CLI commands).
Troubleshooting
Users get no emails
Check the account's contact email, the notification settings and the Exim log for delivery problems.
Too many emails
Increase the throttle period or limit notifications to real-time detections only.
Frequently asked questions
Can users turn Imunify360 off?
No. Users only get the actions you allow; protection stays on.
What is the EICAR file?
A harmless standard test string that antivirus products detect as malware. It is safe for testing detection and notifications.
Should resellers manage Imunify360 for customers?
If your version supports it, giving resellers visibility lets them help customers quickly; keep server-wide firewall settings root-only.
Where do users find the results?
In cPanel → Security → Imunify360, limited to their own account.