Ensure Bastion is used for VM access
Azure Bastion should be deployed to provide secure RDP/SSH access to VMs.
Security Impact
Without Bastion, VMs require public IPs and NSG rules for remote access.
How to Remediate
Deploy Azure Bastion in hub VNet and remove public IPs from VMs.
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 Network 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-networking-19
- Service
- Azure Virtual Network
- Category
- Access Control
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your Azure environment for this and 160+ other security checks.
Start Free TrialRelated Azure Virtual Network Checks
View all checksEnsure NSG flow logs are enabled
Ensure NSG does not allow SSH from internet
Ensure NSG does not allow RDP from internet
Ensure NSG does not allow unrestricted access to high-risk ports
Ensure Network Watcher is enabled