Skip to content
Back to services

Security

Shut the door on everyday attacks

A server with a public IP receives login attempts from the very first minute. You do not need to be an expert to protect it: you need the basics done right and kept that way.

Swipe the diagram to see all of it

Your serverfail2ban✕UFW✕✕185.220.x.xtries SSH passwords✕45.141.x.xscans for open ports◎Visitorhttps◆SERVILINUXed25519 key◎Sentinelmutual TLS⇄:22 SSHkey only, no password⇄:443 HTTPSyour sites and apps⇄:9100 metricsonly for Sentinel🔒:3306closed from outside
  • Blocked
  • Allowed through its port
  • Metrics with a certificate

Whoever tries passwords over SSH is blocked by fail2ban; whoever scans for open ports hits the firewall. Visitors only reach HTTPS, SERVILINUX comes in with its key and Sentinel reads metrics with a certificate. The database cannot be seen from outside.

Key-only access

SERVILINUX logs in with its own key and can turn off password login once setup is done. Your passwords are not stored anywhere.

fail2ban and firewall

fail2ban blocks whoever tries passwords and the firewall leaves open only what is needed. When enabling it, SERVILINUX makes sure not to lock you out of SSH.

Encrypted metrics

Sentinel exporters only answer whoever presents a SERVILINUX certificate; without it, they do not even accept the connection.

Eisac watches with you

Ask who is trying to log in, which IPs are blocked or whether anything looks odd in the logs. It can block or unblock an IP, always with your confirmation.

In SERVILINUX

How it is done

  1. 1
    Connect the server

    SERVILINUX creates its user with a key and can close password access.

  2. 2
    Turn on fail2ban

    From the Security tab of the server page.

  3. 3
    Set up the firewall

    Open only what you use; SSH stays protected.

  4. 4
    Review with Eisac

    Login attempts, suspicious IPs and blocks, explained.