Azure NSG Open to Internet
The rule admits traffic from any address, so everything behind it is exposed to the internet whatever the application's own controls do.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Restrict unrestricted ingress on network 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
- Network Security Groups on Azure
- The fix, by hand
- Network security groups → the resource → Inbound security rules.
- Replace Source = Any / Internet with specific Service Tags (VirtualNetwork) or your office CIDR.
- For SSH / RDP, delete the rule and adopt Azure Bastion (Bastion → connect via browser, no public IP on the VM).
- For public web, keep :443 but front via App Gateway with a WAF_v2 policy.
- Apply NSG Flow Logs (Network Watcher) to confirm only expected sources reach the workload.
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-1360
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.