Ensure Key Vault has private endpoint enabled
Key Vaults should use private endpoints for secure VNet access.
Security Impact
Public endpoints expose Key Vault to internet-based attacks.
How to Remediate
Create private endpoint for Key Vault. Disable public network 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 Key Vault 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, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- azure-keyvault-4
- Service
- Azure Key Vault
- Category
- Network Security
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your Azure environment for this and 160+ other security checks.
Start Free TrialRelated Azure Key Vault Checks
View all checksEnsure Key Vault has soft delete enabled
Ensure Key Vault has purge protection enabled
Ensure Key Vault uses RBAC for access control
Ensure Key Vault network access is restricted
Ensure Key Vault diagnostic logging is enabled