Security

Server security auditing: firewall, SSH, fail2ban and more, with fixes you approve.

Auditing and guided remediation

When you connect a VPS to SecuryBlack, FerroSentry checks these controls and shows you what fails and how to fix it. You decide what gets applied: each fix is launched from the panel with your confirmation and, for critical commands, with Sudo Mode.

Nothing changes on your server without your confirmation. Fixes are standard, proven security changes.

Controls it checks

Firewall (UFW)
Firewall enabled and configured with minimal rules. Only the ports you use are open. The rest are closed by default.
  • Detects open ports and Docker containers that bypass UFW
  • Rate limiting on SSH ports
SSH Key-only
Password authentication disabled. SSH keys only.
  • Prevents brute force attacks
  • More secure and faster than password
Root login disabled
Cannot connect directly as root. Only as a regular user.
  • Requires sudo for privileged operations
  • Adds an audit layer
Fail2ban
Automatic intrusion attempt detection. 5 failed attempts in 10 minutes = IP blocked for 1 hour (SSH).
  • Watches SSH login attempts
  • Automatic and temporary blocks
Security auto-updates
Automatic updates for critical packages without requiring reboot.
  • Unattended-upgrades enabled
  • Configurable according to your needs
Continuous auditing
Continuous monitoring of your server's security posture.
  • Detects configuration changes
  • Alerts if something is disabled

Security dashboard

In your dashboard, the "Security" section shows the status of all controls:

  • Status of each control (enabled/disabled)
  • Latest blocked intrusion attempts
  • Servers with pending controls
  • Configuration change history
  • Pending security update alerts

Security audit (FerroSentry)

FerroSentry is the module behind continuous auditing: an optional agent you install per server from the server details page in your dashboard. It audits the host's security posture, open ports, and pending security updates.

Each finding shows up on the server page with its severity and a concrete recommendation to fix it. You decide which ones to apply from the panel.

Additional best practices

In addition to what the audit checks, we recommend:

  1. 1

    Use strong passwords for sudo

    Even if not needed with SSH keys, keep a secure password

  2. 2

    Clean logs regularly

    Use logrotate to prevent logs from growing indefinitely

  3. 3

    Monitor active users

    Use w or who to see active SSH sessions

  4. 4

    Review audit logs periodically

    SecuryBlack keeps a record of all changes in your dashboard

  5. 5

    Back up regularly

    The physical security of your data is just as important as hardening

Customization

If you need to customize the security controls applied to your server (e.g., open additional ports, change fail2ban configuration, etc.), you can do so directly on your server:

Firewall (UFW)

sudo ufw allow 8080

SSH config

sudo nano /etc/ssh/sshd_config

SecuryBlack respects your changes and does not overwrite them automatically.

Security questions?

If you have questions about how to apply or customize these controls, contact us.