Already Run Imunify360 or BitNinja? Where Network Protection Fits
Server security suites protect the sites and software on a server. Network-level protection covers what they cannot see. How the two layers work together.
By Frabs · 15 November 2026 · 3 min read
The short answer: tools such as Imunify360, BitNinja, CloudLinux, CrowdSec, Monarx and Patchman protect what runs on a server: its websites, files, logins and accounts. Network-level protection watches the traffic going in and out of the server as a whole, so it catches floods, scans and outgoing abuse that never touch a website. The two cover different ground, and the right setup runs both without either changing the other's rules.
What Server Security Suites Do Well
These tools sit on the server and look at what happens there:
- Malware and web shells in the files of hosted sites.
- Web application attacks, such as attempts to exploit a CMS.
- Brute force against logins, based on the server's own logs.
- Per-account resource limits, as CloudLinux does, so one site cannot take the whole server.
- Vulnerable software, found and patched before it is exploited.
If you run shared hosting, at least one of these is almost certainly already on your servers, and it should stay there.
What They Cannot See
They work from inside the server, through its logs, files and processes. Some things happen below that:
- Floods aimed at the server. A SYN or UDP flood fills the network and the kernel before any log line is written.
- Outgoing abuse. A compromised account scanning the internet, or a VPS flooding someone else, is a problem for the people receiving it and for your IP ranges. Server suites rarely watch what leaves.
- VPS's on a hypervisor. Customers' VPS's are their own machines. You cannot install a suite inside them, and should not.
- Which customer is behind the traffic. On a node with many VPS's, traffic needs to be tied to the right one before anyone can act on it.
How the Two Layers Fit Together
Think of it as two layers:
- On the server: your security suite, looking after sites, files, logins and accounts.
- On the network: network protection, looking after the traffic in and out, and stopping floods before they reach the server.
The rule that matters is that neither layer changes the other's settings. Two tools that both rewrite the same firewall rules will fight, and the result is outages that are hard to trace.
How Frabs Works Alongside Them
Frabs runs at network level and never touches the rules or limits your other tools set. It keeps its rules in its own tables, never changes your iptables, ipsets or the server's own firewall, and never changes CloudLinux limits. On Frabs Host, it can read CloudLinux's per-account figures where they are there, to name the account behind abuse.
What it adds:
- Incoming floods and scans stopped on the network, before they reach the server.
- Outgoing abuse named to the account, server or VPS behind it, before it gets your range listed.
- Every VPS on a node, protected from the node, with nothing installed inside.
The compatibility pages list each product Frabs works alongside, and what each one covers.
Frequently Asked Questions
Do I still need Imunify360 or BitNinja if I use Frabs?
Yes, if you use them today. They protect the sites, files and logins on a server. Frabs adds protection at network level, for floods, scans and outgoing abuse, and works alongside them.
Will Frabs change my firewall rules?
No. Frabs keeps its rules in its own tables and never changes iptables, ipsets, the server's own firewall or CloudLinux limits.
Can a server security suite stop a DDoS attack?
Not on its own. A flood fills the network and the kernel before the suite sees it. It has to be stopped on the network, before it reaches the server.
Does Frabs work with CloudLinux?
Yes. On Frabs Host, Frabs can read CloudLinux's per-account figures where they are available, and it never changes your limits.