Security

Security Built from Mechanisms You Can Check.

Nodekeeper came out of day-to-day production operations and customer security reviews. That's why isolation, access control, web protection, operation records and recovery get so much attention. This page lists the actual controls, the plans that include them, and where each one stops.

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 site runs as its own system user and group, and the site root is owned by root.
  • PHP-FPM gets one pool per site. Apache (mod_php) gets one instance per site by default.
  • Each site's runtime logs can be read only by that site's user and root.
  • Extracting and restoring archives runs with the site's identity. It never creates symbolic or hard links and skips ../ and absolute paths. A website backup restores only into that site's own directories.
  • Site SSH / SFTP is key-only, confined to one site and time-limited (per-site virtual ssh).

In testing on 2026-11-03, the November 2026 release refused every cross-member request: sites, files, tasks, SSH grants, FTP, PHP pools and logs, backups, domains, WAF logs, reverse proxy and forwarding. The isolation check script passed 72 of 72 checks.

Limits and prerequisites
  • Isolation keeps sites apart from each other. It does not protect against someone who already has root on the host.
  • If you put several sites on one shared Apache instance, those sites share a runtime user and lose their separation from each other.
  • Behaviour on this page was verified on the November 2026 release. Older installations should update to get it.

Site access & isolation in detail →

Accounts and access

Member accounts All plans, including Free

Customers and colleagues get their own panel accounts. Nobody needs to share the administrator login.

Groups and roles From Pro

User groups, role permissions and delegated administration for teams.

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

Configure the host's SSH service, keys and two-factor authentication from the panel. Operations that cannot be undone ask for a fresh 2FA code.

Snapshot rollback From Business

Rolling back a storage snapshot requires 2FA and a disk that is not in use. A snapshot of the current state is taken automatically first.

Web and network protection

Base WAF All plans, including Free

ModSecurity rule sets for your sites, managed in the panel.

System firewall All plans, including Free

Host firewall rules and port forwarding (iptables, frp, SSH) are managed from 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.

Limits and prerequisites
  • Traffic rules act on what you configure. They do not recognise every bot or every attack.
  • GeoIP rules work from IP-based location estimates.

Audit logs

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

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

eBPF tamper protection From Pro

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

Limits and prerequisites
  • The running kernel must support BPF-LSM (kernel 4.18 or newer, with BPF-LSM enabled). Enabling it 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 who fully controls the host as root may be able to turn it off.

Services run with the least privilege they need

  • Self-hosted mail runs as its own program under an unprivileged system user, not as root.
  • Each site's FTP service and PHP workers run as that site's user.
  • Site SSH is served by a separate Nodekeeper service that keeps sessions inside the site, apart from the host's sshd.

What remains your responsibility

  • Keep Nodekeeper and the operating system updated.
  • Choose supported PHP versions. PHP 8.1 and older are end-of-life upstream and carry other known vulnerabilities.
  • Keep independent backups and test restores. A snapshot is not a separate copy of your data.

Nodekeeper provides technical controls: isolation, permissions, 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 [email protected] with the version, a description and the steps to reproduce. Please do not send passwords, private keys or customer data.

N Nodekeeper

All-in-one Linux server management agent.

Support
[email protected] WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.