Cosmosdb Security

Azure Cosmos DB security best practices: disabling local authentication (keys), managed identity with DefaultAzureCredential, network access restrictions, RBAC least privilege, and continuous backup for point-in-time restore. USE FOR: Cosmos DB security, disable local auth, disable keys, managed identity, DefaultAzureCredential, Entra ID, network restrictions, IP firewall, private endpoints, RBAC roles, least privilege, data plane roles, continuous backup, point-in-time restore, PITR, zero-trust. DO NOT USE FOR: client-side encryption (pending), SDK authentication code (use cosmosdb-sdk).

atc-net Updated 3 repo stars

File contents

Azure Cosmos DB Security

Security best practices for Azure Cosmos DB accounts, covering authentication, network isolation, access control, and data protection.

When to Apply

Reference these guidelines when:

  • Setting up authentication for Cosmos DB
  • Configuring network access restrictions
  • Assigning RBAC roles for data plane access
  • Enabling continuous backup
  • Hardening a Cosmos DB account for production

Rules

  • security-disable-local-auth - Disable local authentication (keys)
  • security-managed-identity - Use managed identity with DefaultAzureCredential
  • security-network-restrict - Restrict network access
  • security-rbac-least-privilege - Assign minimum RBAC roles
  • security-continuous-backup - Enable continuous backup for PITR

atc-net/atc-agentic-toolkit/tree/main/plugins/cosmosdb/skills/cosmosdb-security commit 1259253513

Frequently asked questions

npx skillmds@latest add atc-net/cosmosdb-security