Cosmos DB should use managed identity
Medium
Azure
General
cosmosdb-managed-identity
Applies to
Microsoft.DocumentDB/databaseAccounts
What CGPulse checks
A resource passes this rule when identity.type must be set. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Enable managed identity to eliminate stored credentials and improve security. In Azure Portal: Cosmos DB > Identity > enable System-assigned managed identity. See: https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-setup-managed-identity
CLI
az resource update --ids "{id}" --set identity.type=SystemAssignedTerraform
resource "azurerm_cosmosdb_account" "{name}" {
name = "{name}"
resource_group_name = "{rg}"
location = var.location
offer_type = "Standard"
kind = "GlobalDocumentDB"
identity {
type = "SystemAssigned"
}
consistency_policy {
consistency_level = "Session"
}
geo_location {
location = var.location
failover_priority = 0
}
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Azure rules
- Action Group should be enabled
- Activity Log Alert should be enabled
- AKS cluster logs should be sent to Log Analytics
- AKS cluster must enable RBAC
- AKS cluster must enable RBAC
- AKS cluster should be a private cluster
- AKS cluster should disable local accounts
- AKS cluster should enable Azure RBAC for Kubernetes