Security & Access Control

Clear Access Boundaries for Websites, Clients and Teams

Nodekeeper comes out of day-to-day production operations and customer security reviews, so isolation, access checks, web protection, operation records and recovery get particular attention. This page lists the controls that exist, which plan includes each one and where each one stops: sites run separately, accounts get permissions by user group, panel actions are recorded, and there is a way to recover when something goes wrong.

On this page: Website isolation · Accounts and access · Web and network protection · Operation records · Tamper protection · Service privileges

Basic Security Is Not an Upgrade All plans, including Free

Site isolation, the base WAF, core access checks and operation records are in every plan, Free included. Paid plans build on that baseline with deeper traffic controls, log viewers, collaboration and tamper protection.

Strong website isolation All plans, including Free

Each website runs inside its own boundary, so a problem in one site does not spread to the others through a shared account or directory. Teams and clients get access by user group and maintain the resources they are responsible for.

  • Every site uses its own system user and group, and the site root is owned by root.
  • PHP-FPM gets one pool per site, and Apache (mod_php) gets one instance per site by default.
  • A site's runtime logs can be read only by that site's user and root.
  • Extracting and restoring archives runs with the site's own identity, never produces symbolic or hard links and skips ../ and absolute paths. Website backups restore only into that site's own directory.
  • Site SSH / SFTP is key-only, confined to one site and time-limited (Per-site virtual SSH).
  • A request for another member's resource is refused with the same message as for one that does not exist, so members cannot discover what others own.
Limits and prerequisites
  • Isolation keeps sites apart from each other. It does not protect against someone who already has root on the host.
  • Sites attached to one shared Apache instance share a runtime user and are no longer separated from each other.

Per-site SSH and SFTP access → · Web hosting panel →

Accounts and Access: Every Permission Is Granted by User Group

Each permission can be configured per user group, and only users who hold it can perform the action. Every request also checks who owns the resource.

Member accounts All plans, including Free

Clients and colleagues each use their own panel account instead of sharing the administrator's.

User groups and roles From Pro

Custom user groups, role permissions and delegated administration, so each team works within the resources it is responsible for.

Host SSH, 2FA, keys All plans, including Free

Set up the host's SSH service, keys and two-factor authentication in the panel. Irreversible operations ask for a fresh 2FA code.

Snapshot rollback From Business

Rolling back a storage snapshot needs 2FA and the disk must not be in use. A snapshot of the current state is taken automatically before the rollback.

Web and Network Protection

Base WAF All plans, including Free

Enable ModSecurity rule sets for a site and manage them in the panel.

System firewall All plans, including Free

Host firewall rules and port forwarding (iptables, frp, SSH) are managed in the same panel.

Abnormal traffic handling From Personal

Rate limits, IP and GeoIP rules, a human check in front of a site, and JA3 client-fingerprint rules. See traffic analytics

Limits and prerequisites
  • Traffic rules work as you configure them. They cannot recognise every bot or every attack.
  • GeoIP rules rely on IP-based location estimates.

Audit logs: Who Did What, and When

In every plan, Free included, panel actions are recorded with the account, the permission used, the request path and the source IP. Forged X-Forwarded-For and X-Real-IP headers are ignored, and the real address is recorded.

The website-log and WAF-log viewers start at Personal. Paid plans add viewing and analysis tools, and Free records operations just the same.

eBPF tamper protection From Pro

An eBPF LSM program in the kernel protects the files and directories you choose, according to the policy you set.

Limits and prerequisites
  • The running kernel must support BPF-LSM (4.18 or newer, with BPF-LSM enabled). Turning it on in the boot configuration is a separate, high-risk administrator permission.
  • It protects the objects you select. It does not stop every attack, and an attacker with full root on the host may still turn it off.

Services Get Only the Privileges They Need

  • Self-hosted mail is a separate program that runs as an unprivileged system user, not root. About free self-hosted email
  • Each site's FTP service and PHP workers run as that site's user.
  • Site SSH is served by a separate Nodekeeper service that confines sessions to the site, apart from the host's sshd.

What still falls to you

  • Keep Nodekeeper and the operating system up to date.
  • Choose supported PHP versions. PHP 8.1 and older are end-of-life upstream and carry other known vulnerabilities.
  • Keep independent backups and rehearse a restore. A snapshot is not a separate copy of your data. See website, database and cloud PC backups.

Nodekeeper provides technical controls: isolation, permissions, a WAF, operation records and recovery tools. Installing it does not by itself make a deployment pass a security audit or a compliance review.

Report a Security Issue

Every user can report a security issue, on any plan, including Free. Write to support@host.mw with the version, a description and the steps to reproduce. Please do not send passwords, private keys or customer data.

N Nodekeeper

Manage websites, office PCs and servers from one panel on your own hardware.

Support
support@host.mw WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.