Ensure Cosmos DB uses private endpoints
Cosmos DB accounts should use private endpoints for secure VNet access.
Security Impact
Public endpoints expose database to internet scanning and potential attacks.
How to Remediate
Configure private endpoints for Cosmos DB and restrict 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 Cosmos DB 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-cosmosdb-7
- Service
- Azure Cosmos DB
- 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 Cosmos DB Checks
View all checksEnsure Cosmos DB has firewall rules configured
Ensure Cosmos DB uses encryption at rest
Ensure Cosmos DB disables public network access
Ensure Cosmos DB has diagnostic logging enabled
Ensure Cosmos DB uses Azure AD authentication