Critical AWS Network exposure

Security group open to the whole internet (0.0.0.0/0)

A security group is AWS's instance-level firewall. When an inbound rule allows 0.0.0.0/0 (or ::/0 for IPv6), the port behind it is reachable from every address on the internet — not just your team.

Why it matters

Anything open to 0.0.0.0/0 is found within minutes: the whole IPv4 space is scanned continuously by bots looking for exposed SSH (22), RDP (3389), databases (3306, 5432, 6379, 27017) and admin panels.

Once a service is reachable, one weak password, a reused credential, or a known CVE in the software behind the port is a direct path in. Most cloud breaches start with a service that should never have been public.

How to check for it

How to fix it

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

Is 0.0.0.0/0 ever acceptable?
Only for ports a public service genuinely needs — typically 80 and 443 behind a load balancer. Admin ports (22, 3389) and databases should never be open to 0.0.0.0/0.
Does a security group replace a host firewall?
It's a strong first layer, but defence in depth means keeping the OS firewall and patched software too. A single layer is a single point of failure.