Ensure Private Endpoints Are Used To Access Cosmos DB Accounts

Overview

Private endpoints limit network traffic to approved sources.

Rationale

For sensitive data, private endpoints allow granular control of which services can communicate with Cosmos DB and ensure that this network traffic is private. You set this up on a case by case basis for each service you wish to be connected.

Impact

Only whitelisted services will have access to communicate with the Cosmos DB.

Default Value

By default, Cosmos DB does not have private endpoints.

Remediation guidance

Remediate from Azure Portal

Open the Cosmos DB account using the Open in Azure button.
Select Networking.
Select Private access.
Click + Private Endpoint.
Provide a Name.
Click Next.
From the Resource type drop down, select Microsoft.AzureCosmosDB/databaseAccounts.
From the Resource drop down, select the Cosmos DB account.
Click Next.
Provide appropriate Virtual Network details.
Click Next.
Provide appropriate DNS details.
Click Next.
Optionally provide Tags.
Click Next : Review + create.
Click Create.

Multiple Remediation Paths

Azure

SERVICE-WIDE (RECOMMENDED when many resources are affected): Assign Azure Policy initiatives at management group/subscription scope and trigger remediation tasks.

az policy assignment create --name <assignment-name> --scope /subscriptions/<subscription-id> --policy-set-definition <initiative-id>
az policy remediation create --name <remediation-name> --policy-assignment <assignment-id>

ASSET-LEVEL: Apply the resource-specific remediation steps above to the listed non-compliant resources.

PREVENTIVE: Embed Azure Policy checks into landing zones and IaC workflows to block or auto-remediate drift.

References for Service-Wide Patterns

Azure Policy overview: https://learn.microsoft.com/en-us/azure/governance/policy/overview
Azure Policy remediation: https://learn.microsoft.com/en-us/azure/governance/policy/how-to/remediate-resources
Azure Policy initiative structure: https://learn.microsoft.com/en-us/azure/governance/policy/concepts/initiative-definition-structure

Operational Rollout Workflow

Use this sequence to reduce risk and avoid repeated drift.

1. Contain at Service-Wide Scope First (Recommended)

Azure: assign policy initiatives at management group/subscription scope and run remediation tasks.

az policy assignment create --name <assignment-name> --scope /subscriptions/<subscription-id> --policy-set-definition <initiative-id>
az policy remediation create --name <remediation-name> --policy-assignment <assignment-id>

2. Remediate Existing Affected Assets

Execute the control-specific Console/CLI steps documented above for each flagged resource.
Prioritize internet-exposed and production assets first.

3. Validate and Prevent Recurrence

Re-scan after each remediation batch.
Track exceptions with owner and expiry date.
Add preventive checks in IaC/CI pipelines.

Query logic

These are the stored checks tied to this control.

Azure Cosmos DB accounts without private endpoints

Connectors

Microsoft Azure

Covered asset types

CosmosDBAccount

Expected check: eq []

{
  cosmosDbAccounts(where: { privateEndpoints_SOME: null }) {
    ...AssetFragment
  }
}