Skip to content

Security center

The host and site security center — firewall rules, country rules and brute-force bans per server, the web application firewall mode of every site, security headers, and where to see what was blocked.

The Security page of the administrator menu shows the protection of your servers and sites in one place, and the Security tab of each account holds the protection of its sites. This page explains both. Sign-in security (two-factor authentication, passkeys, sessions) is on its own page: Security. WordPress scanning is in WordPress security scanning.

Where Who
Security in the main menu (the whole fleet) organization administrators
An account’s Security tab (its sites, its WAF log) administrators, resellers and customers for their accounts

Changes are applied by the agent on the server within a moment. The panel shows Applying…, In sync or Not applied yet next to a policy. If it shows Agent update required, that server’s agent is too old for the feature: update the server first (see How updates work).

The top of the Security page lists your servers. For each one you see:

  • whether the server accepts no inbound management (the panel confirms it), and whether the firewall’s input policy drops unlisted traffic;
  • the number of firewall rules and of active bans;
  • whether the web application firewall is installed on the server’s web entry point.

The page also shows the version of the country database used by country rules. Choose Manage on a server to open its panel, described next.

Shows what the server reports: the listening ports, the service behind each one and whether it is Exposed to the internet or Not exposed. Use it to check that nothing listens that you did not expect.

Rules apply to inbound traffic of the hosted services only: Web (80/443) and SFTP (2222). Management traffic is outbound and is never touched by these rules. Without rules, every hosted service is open.

  1. Choose Add rule.
  2. Pick the Action (Allow or Deny), enter an address or a prefix in CIDR form, for example 198.51.100.0/24, pick the Service, and add a note for yourself.
  3. Choose Save.

A country rule either blocks the selected countries or allows only the selected countries. It covers HTTPS (443) and SFTP (2222). Country rules need the country database; until it is imported the panel says so and the rule cannot be set.

When it is on, an address is banned after repeated failed logins to the server’s login services, such as SFTP and the mail ports. You set:

  • Failures before a ban, the window in which they are counted and the length of the ban, in seconds;
  • Never ban: addresses or prefixes that are never banned, one per line, for example your office.

A repeat ban lasts longer. Active bans lists each banned address with its service, the failures and when the ban ends; choose Unban to lift one by hand. An IPv6 ban covers the whole /64 network, so unbanning any address inside it lifts it.

Every site can run behind a web application firewall (WAF) that inspects requests and stops the ones that look like attacks. Per site you choose one of three modes:

Mode What happens
Off No inspection: requests reach the site unchecked.
Detect (log only) Suspicious requests are written to the WAF log and never blocked.
Block Suspicious requests get a 403 answer and are written to the WAF log.

New sites start in Block, unless your administrator chose another default. Sites that already exist keep their mode.

On the Security page, WAF default for new sites sets the mode a new site starts with. It does not change existing sites.

WAF overview counts your sites per mode and lists every site with its chosen mode, the mode actually running on the server (it reads Not reported until the server has confirmed it), and how many requests were blocked and logged in the last 24 hours. Below it, Recent blocked requests shows the latest blocks across all sites. For a single site’s history, open its WAF log: see Reading the WAF log.

Open the account, choose the Security tab and pick the site:

  • WAF mode and Paranoia level. The level goes from 1 (fewest false alarms) to 4 (strictest). A higher level catches more and blocks more legitimate requests; start at 1 and raise it only if you can test the site.
  • WAF for all sites sets the mode of every site of the account at once. Other settings of each site stay.
  • Rule exclusions turn one rule off for the whole site or for one path. They exist to fix a false alarm; see Reading the WAF log.
  • Security headers, below.

Each site shows the mode that is Running on the server next to the one you chose. If the panel says the server’s web entry point is being updated, the firewall and the country rule apply after the update.

Security headers are sent with every response of the site:

  • HSTS max-age in seconds; 0 sends no Strict-Transport-Security header. It is sent over HTTPS only. Include subdomains and Preload are separate switches; preload needs include subdomains and a max-age of at least one year (31536000).
  • Content-Security-Policy, printable ASCII without { or } and at most 4096 characters. Tick Report only to have browsers report violations without enforcing the policy; use it to test before you enforce.
  • Basic headers (nosniff, Referrer-Policy, X-Frame-Options).