Server on a public IP with no firewall
When a cloud server has a public IP and no cloud firewall attached, every port the OS is listening on is reachable from the whole internet — unless the host's own firewall happens to block it.
Why it matters
A public IP is scanned within minutes. Any service bound to 0.0.0.0 — a database, a cache, an admin panel, SSH — is directly reachable and attacked.
Relying only on the OS firewall means one misconfiguration or a service that binds to all interfaces exposes you. A cloud firewall is a separate, default-deny layer in front of the machine.
How to check for it
- In your provider's console, check whether a cloud firewall is attached to the server (Hetzner: Firewalls; DigitalOcean: Networking → Firewalls).
- From outside, a port scan of the public IP shows what's reachable — anything beyond the ports you intend is a problem.
How to fix it
- Attach a cloud firewall that allows only the ports and source ranges you actually need (for example 443 from anywhere, 22 from your VPN only).
- Default-deny inbound: start closed and open the minimum.
- Keep the OS firewall configured too, as a second layer — but don't rely on it alone.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Isn't the OS firewall enough?
- It's a good layer, but it's on the same machine you're trying to protect and easy to misconfigure. A cloud firewall sits in front of the server and fails closed, so two layers is the standard.