@@PRODUCT@@

Choosing a security profile per server

Every server has one security model: nine modules, each with an owner, a profile that bundles the settings, and one list of settings that runs from the platform through the server, the reseller and the customer account down to a single webs

Written for: Administrator

Every server has one security model: nine modules, each with an owner, a profile that bundles the settings, and one list of settings that runs from the platform through the server, the reseller and the customer account down to a single website. This guide shows how an administrator puts a server on a profile, changes or locks a single setting, and checks where a value comes from. The panel screen arrives in a later step; for now everything goes through the panel's API and through corectl on the server itself.

Step 1: see what the server does now

Ask for the server. You see the profile, how many settings deviate from it, the modules with their owner and health, and whether the last push from the panel reached the server.

curl -s https://panel1.corecp.dev/api/v1/security/nodes/stck1.corecp.dev \
  | jq '{profile, profile_changes, sync: .sync.state,
         modules: [.modules[] | "\(.module)=\(.owner)"]}'

A server the panel sees for the first time gets the Standard profile. Whatever the administrator had already configured on that server — the mode of the website firewall, for example — stays as it is: that value is taken over and the profile only fills in what nobody had decided yet. Such a server then shows as "standard + 1 change".

On the server itself corectl security status gives the same picture, with a line saying when the panel last pushed anything.

The settings live in /etc/corecp/node.yaml on the server. If you or a tool of your own rewrites that file — a YAML library, for example — the moment of the last push may come back in a different spelling, such as 2026-11-12 20:39:53+00:00 instead of 2026-11-12T20:39:53Z. The server reads both, and writes its own form again at the next change.

Step 2: put the server on a profile

There are four profiles: Off, Basic, Standard and Strict. A profile is a bundle of values at server level: the scanner, the website firewall, the request limit, the wp-admin challenge, XML-RPC, wp-cron, the process monitor, suspending on malware and fleet reputation.

curl -s -X PUT https://panel1.corecp.dev/api/v1/security/nodes/stck1.corecp.dev/profile \
  -H 'Content-Type: application/json' -d '{"profile":"strict"}' \
  | jq '{profile, profile_changes, sync: .sync.state}'

The answer says synced when the server received the new values. If it says not_in_sync, the reason is next to it (the server is unreachable, for instance). The server keeps running on its previous values; the panel retries every five minutes, and you can force a retry with a POST on …/nodes/stck1.corecp.dev/push.

Several servers at once go through POST /api/v1/security/profile with a list of servers. Every server is applied on its own and reported on its own: a server that fails does not hold the others back.

Step 3: deviate from the profile, or lock a setting

A single setting is changed per key. The server then counts as "profile + n changes", so it stays visible that it deviates. With lock the value becomes binding for everything below the server: a reseller or customer who wants to change the same key gets the refusal setting_locked, naming the level that holds the lock.

curl -s -X PUT https://panel1.corecp.dev/api/v1/security/nodes/stck1.corecp.dev/settings/wp.admin.challenge \
  -H 'Content-Type: application/json' -d '{"value":"always","lock":true}' \
  | jq '.settings[] | select(.key=="wp.admin.challenge") | {value, locked, source_level}'

A DELETE on the same route removes the value (and the lock) again; the server then inherits from the platform once more.

Step 4: switch modules on or off

Every module has an owner: CoreCP, cPGuard or off. In this step you can switch a module off and give it back to CoreCP; cPGuard as an owner arrives in a later step and is still refused for now. The firewall and hardening can never be given to cPGuard, and the firewall can never be off either: the packet filter is always CoreCP's.

curl -s -X PUT https://panel1.corecp.dev/api/v1/security/nodes/stck1.corecp.dev/modules/scanner \
  -H 'Content-Type: application/json' -d '{"owner":"off"}' \
  | jq '[.modules[] | select(.module=="scanner")]'

Step 5: check where a value comes from

On the server, corectl security explain says for every key what applies and which level and which id it came from — for one account or one website as well. That is the same answer the panel gives, with the same origin.

corectl security explain wp.cron --domain shop.example.com
corectl security explain wp.xmlrpc --account customer01

When it says locked there, the value is locked at that level. A customer sees a padlock instead of a change button for such a setting in the panel.

What resellers and customers may do

A reseller sets defaults and locks for their own realm for the settings of accounts and websites (wp-cron, XML-RPC, the wp-admin challenge, the crawlers and the country rules), through /api/v1/security/realm. Server matters — the profile, the modules, the firewall — stay with the server administrator. A customer configures their own websites within what is not locked; the website firewall mode of a website remains a server administrator's decision.

Hardening and the real visitor address

The profile also decides which PHP functions are switched off on the server: Standard takes away what a website never needs (process control, changing user), Strict also takes away exec, system and their kin, which some plugins use for image previews or backups. Whatever the profile, PHP files are never run from wp-content/uploads, and websites send mail only through the server's own mail system. Check what the server runs now:

corectl security status

The hardening: line shows the PHP set and the uploads rule; the real ip: line shows which proxies the server believes. Behind Cloudflare that works by itself: logs, the website firewall and bans see your visitors, not Cloudflare. Behind a proxy or load balancer of your own, add its addresses:

corectl security set web.real_ip.trusted 198.51.100.10
corectl security set web.real_ip.header X-Forwarded-For

Add only proxies that set that header themselves; a visitor's own header from anywhere else is ignored.