Ensure VMs do not have public IP addresses
Production VMs should not have public IP addresses unless required for public-facing services.
Security Impact
Public IPs expose VMs directly to internet-based attacks.
How to Remediate
Remove public IPs from VMs. Use Azure Bastion, VPN, or load balancers for access.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your Azure environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Azure Virtual Machines resources across your Azure subscriptions every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- azure-compute-2
- Service
- Azure Virtual Machines
- Category
- Network Security
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your Azure environment for this and 160+ other security checks.
Start Free Trial