Signed releases#
Every intoPanel release is signed with intoPanel's release key. The public half of that key is built into the panel and the installer. A server installs a release only when its size and checksum match what the licence server announced and its signature matches the key, so nobody else can publish an update, not even someone who breaks into the licence server.
Secure by default#
The installer sets up the CSF firewall and login protection, ModSecurity with the OWASP Core Rule Set, brute-force protection for the panel, SSH, FTP and mail, a protected /tmp, symbolic link protection, closed compilers and limited shell processes. The Security Checkup page lists anything that could still be made safer, most important first.
Separation inside the server#
The panel has two parts: a web server that shows the pages and runs as its own unprivileged user, and a daemon that makes the changes as root and accepts only well-formed requests from the web server. With Account Isolation on, each hosting account's PHP runs in a service of its own that sees only its own files.
Signing in#
Every login can use two-step sign-in with an authenticator app and recovery codes. Sessions end after a period of inactivity, admin and client areas sign in separately on their own ports, and repeated failed sign-ins lock the address out.
Your licence data#
The licence check sends the server's address and a fingerprint of its machine id; the id itself never leaves the server. Licence answers are signed by the licence server and checked by the panel.
Reporting a security issue#
If you believe you have found a security issue in intoPanel or in one of our websites, write to support@intopanel.com with the subject "Security". Include what you found and how to reproduce it. Please give us reasonable time to fix it before you share it with anyone else; we will keep you informed and credit you if you wish.