OpenParable
Skip to content
← Back to skills

Cis Azure Database 3.2

DevOps & Security
cis-azure-database-3.2

Cis Azure Database 3.2 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure that Cosmos DB uses Private Endpoints where possible

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/CIS_Microsoft_Azure_Database_Services_Benchmark_v2.0.0/cis-azure-database-3.2/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-azure-database-3-2, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

3.2 Ensure that Cosmos DB uses Private Endpoints where possible (Automated)

Profile Applicability

  • Level 2

Description

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. This can be set this up on a case by case basis for each service to be connected.

Impact

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

Audit Procedure

Audit From Azure Portal

  1. Open the portal menu.
  2. Select the Azure Cosmos DB blade.
  3. Select the Azure Cosmos DB account.
  4. Select Networking.
  5. Ensure Public network access is set to Selected networks.
  6. Ensure the listed networks are set appropriately.
  7. Select Private access.
  8. Ensure a private endpoint exists and Connection state is Approved.

Audit From Azure Policy

  • Policy ID: 58440f8a-10c5-4151-bdce-dfbaad4a20b7 - Name: 'CosmosDB accounts should use private link'

Expected Result

A private endpoint should exist with Connection state set to Approved, and Public network access should be set to Selected networks.

Remediation

Remediate From Azure Portal

  1. Open the portal menu.
  2. Select the Azure Cosmos DB blade.
  3. Select the Azure Cosmos DB account.
  4. Select Networking.
  5. Select Private access.
  6. Click + Private Endpoint.
  7. Provide a Name.
  8. Click Next.
  9. From the Resource type drop down, select Microsoft.AzureCosmosDB/databaseAccounts.
  10. From the Resource drop down, select the Cosmos DB account.
  11. Click Next.
  12. Provide appropriate Virtual Network details.
  13. Click Next.
  14. Provide appropriate DNS details.
  15. Click Next.
  16. Optionally provide Tags.
  17. Click Next : Review + create.
  18. Click Create.

Default Value

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

References

  1. https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-configure-private-endpoints
  2. https://docs.microsoft.com/en-us/azure/private-link/tutorial-private-endpoint-cosmosdb-portal
  3. https://docs.microsoft.com/en-us/cli/azure/cosmosdb/private-endpoint-connection?view=azure-cli-latest
  4. https://docs.microsoft.com/en-us/cli/azure/network/private-endpoint?view=azure-cli-latest#az-network-private-endpoint-create
  5. https://learn.microsoft.com/en-us/security/benchmark/azure/mcsb-network-security#ns-2-secure-cloud-native-services-with-network-controls

CIS Controls

Controls VersionControlIG 1IG 2IG 3
v812.2 Establish and Maintain a Secure Network ArchitectureXX
v714.1 Segment the Network Based on SensitivityXX