last sync: 2023-Jun-01 17:45:04 UTC

Azure Policy definition

Cosmos DB database accounts should have local authentication methods disabled

Name Cosmos DB database accounts should have local authentication methods disabled
Azure Portal
Id 5450f5bd-9c72-4390-a9c4-a7aba4edfdd2
Version 1.1.0
details on versioning
Category Cosmos DB
Microsoft docs
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
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
IF (1)
Compliance The following 1 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:** Azure Active Directory (Azure AD) is Azure's identity and authentication management service. You should standardize on Azure AD 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 Azure AD 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 Azure AD. This could be an Azure AD Enterprise Directory, Business to Business configuration, or Business to consumer configuration. **Implementation and additional context:** Tenancy in Azure AD: How to create and configure an Azure AD instance: Define Azure AD tenants: Use external identity providers for an application: n/a link 4
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
Initiative DisplayName Initiative Id Initiative Category State Type
Microsoft cloud security benchmark 1f3afdf9-d0c9-4c3d-847f-89da613e70a8 Security Center GA BuiltIn