On this page
Prism is configured one server at a time, but one page shows all of them at once. Use it to see which of your servers are onboarded, how many rules and blocks each of them carries, and whether any of them is not being filtered right now.
The page is headed Network & Firewall. Nothing on it can be changed. Every row is a link into the server it belongs to, and every change is made there.
The three counts at the top
Three tiles across the top summarise your whole account. All three are counted from your own servers only.
| Tile | What it counts |
|---|---|
| Protected servers | How many of your servers have protection switched on, with the total number onboarded into Prism underneath. When those two numbers differ, at least one server is not being filtered. |
| Configured ports | The number of inbound rules reported for each of your servers, added together. The panel labels it "rules across your servers". |
| Blocked IPs | The source addresses you have blocked, added together across your servers. Trusted sources are not part of this figure. |
The server list
The card headed Protected servers holds one row per onboarded address. A row shows the server's name, the IP that is protected, how many port rules and blocked addresses it carries, and a state badge.
Some rows carry a small city chip next to the server name. That chip is inferred from the product's name, not read from a location field, so treat it as a hint and not as a statement of which datacenter the server runs in. The chip is absent on any server whose name the panel does not recognise.
Active, Paused, and Sealed
The badge on the right of each row reads one of exactly three things.
- Active. Protection is on for that IP and traffic is being filtered.
- Paused. Filtering is off for that IP and all traffic passes through unfiltered. This is the same switch described on The Firewall tab, and that tab is where you set it back to Active.
- Sealed. Hovering the badge gives the panel's own explanation: "No server is attached to this address. It is sealed, and all traffic is denied, until one is."
When the list is empty
If no servers are listed, the card says:
None of your servers are onboarded into Clouduxe Prism yet. Contact support to enable DDoS protection on a specific IP.
That is a statement about onboarding, not a fault. Protection is enabled per IP, so a server you have just bought can sit outside Prism until it is added. Open a ticket naming the IP you want protected.
The two lists below
Port rules
This card appears only when at least one of your servers has a rule, and it
groups every inbound rule under the server it applies to. The columns are
Port, Proto, Service, and Limits.
Limits carries a short chip for each setting the rule actually has: Proxy only when the rule accepts proxied sources only, No UDP when it drops UDP
aimed at the port, and the rule's packet ceiling written as a figure followed by
pps. A rule with none of those shows a dash. A rule that is not in service
carries a Disabled badge next to its service name; see
The Firewall tab for what that badge means
and why it cannot be switched back on here.
The heading of each group links to that server's Firewall tab, which is where rules are added, edited, and deleted. See Port rules.
Blocked IPs
This card appears only when at least one address is blocked somewhere on your account. Each row shows the blocked address and the server it is blocked on, and opens that server's Firewall tab. See Blocking and allowing IPs.
What this page does not show
There are no attack figures here. What was dropped, when, and from where is recorded per server on that server's Attacks tab. See Reading the Attacks tab.