last sync: 2023-Dec-05 19:46:27 UTC

Azure Policy definition

Cosmos DB database accounts should have local authentication methods disabled

Source Azure Portal
Display name Cosmos DB database accounts should have local authentication methods disabled
Id 5450f5bd-9c72-4390-a9c4-a7aba4edfdd2
Version 1.1.0
Details on versioning
Category Cosmos DB
Microsoft Learn
Description Disabling local authentication methods improves security by ensuring that Cosmos DB database accounts exclusively require Azure Active Directory identities for authentication. Learn more at:
Mode Indexed
Type BuiltIn
Preview False
Deprecated False
Effect Default
Audit, Deny, Disabled
RBAC role(s) none
Rule aliases IF (2)
Alias Namespace ResourceType DefaultPath Modifiable
Microsoft.DocumentDB/databaseAccounts/capabilities[*].name Microsoft.DocumentDB databaseAccounts properties.capabilities[*].name false
Microsoft.DocumentDB/databaseAccounts/disableLocalAuth Microsoft.DocumentDB databaseAccounts properties.disableLocalAuth true
Rule resource types IF (1)
The following 2 compliance controls are associated with this Policy definition 'Cosmos DB database accounts should have local authentication methods disabled' (5450f5bd-9c72-4390-a9c4-a7aba4edfdd2)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
Azure_Security_Benchmark_v3.0 IM-1 Azure_Security_Benchmark_v3.0_IM-1 Microsoft cloud security benchmark IM-1 Identity Management Use centralized identity and authentication system Shared **Security Principle:** Use a centralized identity and authentication system to govern your organization's identities and authentications for cloud and non-cloud resources. **Azure Guidance:** Microsoft Entra ID is Azure's identity and authentication management service. You should standardize on Microsoft Entra ID to govern your organization's identity and authentication in: - Microsoft cloud resources, such as the Azure Storage, Azure Virtual Machines (Linux and Windows), Azure Key Vault, PaaS, and SaaS applications. - Your organization's resources, such as applications on Azure, third-party applications running on your corporate network resources, and third-party SaaS applications. - Your enterprise identities in Active Directory by synchronization to Microsoft Entra ID to ensure a consistent and centrally managed identity strategy. Note: As soon as it is technically feasible, you should migrate on-premises Active Directory based applications to Microsoft Entra ID. This could be a Microsoft Entra Enterprise Directory, Business to Business configuration, or Business to consumer configuration. **Implementation and additional context:** Tenancy in Microsoft Entra ID: How to create and configure a Microsoft Entra instance: Define Microsoft Entra ID tenants: Use external identity providers for an application: n/a link 7
CIS_Azure_2.0.0 4.5.3 CIS_Azure_2.0.0_4.5.3 CIS Microsoft Azure Foundations Benchmark recommendation 4.5.3 4.5 Use Azure Active Directory (AAD) Client Authentication and Azure RBAC where possible. Shared n/a Cosmos DB can use tokens or AAD for client authentication which in turn will use Azure RBAC for authorization. Using AAD is significantly more secure because AAD handles the credentials and allows for MFA and centralized management, and the Azure RBAC better integrated with the rest of Azure. AAD client authentication is considerably more secure than token-based authentication because the tokens must be persistent at the client. AAD does not require this. link 1
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type
CIS Microsoft Azure Foundations Benchmark v2.0.0 06f19060-9e68-4070-92ca-f15cc126059e Regulatory Compliance GA BuiltIn
Microsoft cloud security benchmark 1f3afdf9-d0c9-4c3d-847f-89da613e70a8 Security Center GA BuiltIn
Date/Time (UTC ymd) (i) Change type Change detail
2023-05-26 17:43:09 change Minor (1.0.0 > 1.1.0)
2021-07-07 15:26:31 add 5450f5bd-9c72-4390-a9c4-a7aba4edfdd2
JSON compare
compare mode: version left: version right: