DigitalOcean droplet with no cloud firewall
A droplet with a public IP and no DigitalOcean Cloud Firewall has every listening port reachable from the internet, unless the droplet's own firewall blocks it.
Why it matters
Public droplet IPs are scanned constantly. Databases, caches and admin interfaces bound to all interfaces are the first things found and attacked.
A Cloud Firewall is a separate, default-deny layer applied to the droplet (or a tag), so it protects the machine even if the OS firewall is wrong.
How to check for it
- DigitalOcean → Networking → Firewalls shows which droplets (and tags) a firewall covers. A droplet in no firewall is exposed.
- A port scan of the droplet's public IP shows what's actually reachable.
How to fix it
- Create a Cloud Firewall and apply it to the droplet or a tag, allowing only the inbound ports and sources you need (DigitalOcean → Networking → Firewalls).
- Scope SSH to your own addresses rather than leaving 22 open to everyone.
- Use tags so new droplets inherit the firewall automatically.
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
- Can one firewall cover many droplets?
- Yes — apply it to a tag, and every droplet with that tag is covered, including ones you create later. That's the reliable way to avoid an unprotected droplet.