Pipeline: 5.4.2 Ensure That Private Endpoints Are Used Where Possible

Description

Private endpoints limit network traffic to approved sources.

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.

Remediation

From Azure Portal

Open the portal menu.
Select the Azure Cosmos DB blade.
Select the Azure Cosmos DB account.
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.

Default Value

By default Cosmos DB does not have private endpoints enabled and its traffic is public to the network.

Run the pipeline

To run this pipeline from your terminal:

flowpipe pipeline run azure_cis.pipeline.cis_v300_5_4_2

Use this pipeline

To call this pipeline from your pipeline, use a step:

step "pipeline" "step_name" {
  pipeline = azure_cis.pipeline.cis_v300_5_4_2  
}

Params

Name	Type	Required	Description	Default
database	connection.steampipe	Yes	Database connection string.	`connection.steampipe.default`
notifier	notifier	Yes	The name of the notifier to use for sending notification messages.	`notifier.default`
notification_level	string	Yes	The verbosity level of notification messages to send. Valid options are 'verbose', 'info', 'error'.	`info`

Outputs

This pipeline has no outputs.