Vero Panel isolates administrative frameworks, hosting structures, and individual system users. Even under exploit conditions, compromises remain strictly localized.
Most web hosting panels require administrators to disable SELinux (or set it to Permissive) to bypass configuration complexities. Vero Panel does the opposite: **SELinux is strictly enforced.**
Each hosted user operates under their own Linux system account, strictly confined by custom security policies. Document roots use permanent SELinux contexts (httpd_sys_content_t) that prevent unprivileged shell execution. Even if a hosted CMS is fully compromised via an arbitrary file upload exploit, the attacker cannot access other user directories, read global configs, or execute binares in directories like /files/ or /cache/.
Instead of heavy user-space firewall wrappers that consume CPU cycles, security monitoring is offloaded to VP-Shield, a background daemon compiled in Go.
Shield monitors Nginx, SSH, and email logs in real time. Upon detecting brute-force attempts, port scanning, or malicious URL query strings, Shield inserts temporary blocking rules directly into the kernel's nftables tables using IP sets. This blocks threats instantly at the network layer, before they touch the application layer.
shield.json to persist firewall parameters across system reboots.
Email accounts inside Vero Panel are configured using strict Dovecot/Postfix integrations with SQL-based lookups. The mail storage structure is fully isolated, preventing read access from web scripts.
To protect credentials from database leakage, Vero Panel enforces the **BLF-CRYPT password scheme (bcrypt cost 12)** for all email accounts. Storing credentials in a strong, salted cryptographic hash prevents offline dictionary attacks, while Dovecot handles native authentication.