Security Group with Unrestricted Inbound Access
The port is open to every address on the internet, so it is found by automated scanning within minutes of being exposed.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Restrict public ingress on security group.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Security Groups on AWS
- The fix, by hand
- EC2 → Security Groups → select the resource → Inbound rules.
- Identify each rule with source 0.0.0.0/0 or ::/0.
- Replace with specific CIDRs: office, VPN, partner ranges, or peered VPC CIDR.
- For public services (TLS termination, public APIs): keep only port 443 open; rely on auth at the app layer.
- For admin access (SSH / RDP): switch to AWS Systems Manager Session Manager and remove the open port entirely.
- For resources that don't need direct internet ingress: move them into a private subnet behind an ALB.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-084- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.