01 / Security / E.04How it works
E.04

WAF and malware scanner status

See which WAF rule set and which malware scanner runs on each server: Imunify360, ModSecurity with OWASP CRS, Atomic Basic or ClamAV. A scanner that is installed but stopped shows up as a finding, and so does one that was never installed. For now the screen reports state; rule editing and manual scans are still being built.

Screen sheetE.04
Topic
E · Security
Order
04 / 05
Points
05
Panel support
3 / 4 panels
02 / FigurePanel screen
Hover the numbers
app.ctapanel.com/security/wafWAF and malware5 servers · 1 stopped scannerServerWAF engineScannerStateweb01.fraModSecurity + OWASP CRSClamAVrunningweb02.fraModSecurity + OWASP CRSClamAVstoppedweb01.amsAtomic BasicImunify360runningrs01.nycModSecurity + OWASP CRSClamAVrunningbak01.ash——noneClamAV is installed but stopped on web02.fraAn installed but stopped scanner is worse than none at all: the panel looks protected.The finding links to the services screen.Go to servicesThe engine comes from the service list and the panel: Imunify360 where the imunify service runs, Atomic Basic on Plesk,ModSecurity + OWASP CRS on cPanel and DirectAdmin. With no panel neither is present, and that is reported as missing.Rule management and starting a scan by hand are on the way. Today the screen reports state, so there is nothing here for you to change yet.01020304
  1. 01Engine from the panelImunify360 where the imunify service runs, Atomic Basic on Plesk, ModSecurity + OWASP CRS on cPanel.
  2. 02Missing means missingA panel-less server has no WAF and that is reported as missing, not implied to be there.
  3. 03Stopped scanner findingAn installed but stopped scanner shows up as its own finding and links to the services screen.
  4. 04Reporting for nowRule management and manual scans aren’t here yet; the screen reports which engine runs.
Fig. 02 — WAF and malware scanner status
03 / What it does5 points

What it does.

Installed doesn’t mean running. The table shows each engine’s state, so you don’t keep trusting a scanner that has been off for months. If one has stopped, the row takes you to the services screen and you start it from there. Rule editing and manual malware scans aren’t here yet. For now this screen tells you what runs where, and what doesn’t.

  1. The WAF engine comes from the service list and the panel: an imunify service means Imunify360, Plesk means Atomic Basic, cPanel and DirectAdmin mean ModSecurity with OWASP CRS.

  2. A panel-less server has no WAF, and the table reports it as missing rather than implying one is there.

  3. The malware scanner is detected the same way (imunify360 or clamav), and you get a finding when neither is present.

  4. An installed but stopped scanner is a finding of its own, with a link to the services screen.

  5. Reporting only for now: rule management and starting a scan by hand are not available yet.

04 / Panel-by-panel support3 / 4 panels

Which panels support it?

Capability WAF (ModSecurity) state

  • yesManaged from the panel
  • yesManaged from the panel
  • yesManaged from the panel
  • noNot possible on that panel

Servers without a control panel have no account, reseller or mailbox management, because those come from the panel itself. Firewall, DNS, services and the terminal work over SSH. See the full table

05 / Security5 screens

Security

From the firewall to SSH keys, read per server.

06 / Get started14 days free · No card needed

Connect your first server today.

Free for 14 days, no card needed. Create your account, add your first server with an API token or an SSH key, and the panel starts filling in a few minutes later.

No setup fee · Cancel anytime · EU-hosted