Azure Policy Regulatory Compliance controls for Azure Cosmos DB

APPLIES TO: NoSQL MongoDB Cassandra Gremlin Table

Regulatory Compliance in Azure Policy provides Microsoft created and managed initiative definitions, known as built-ins, for the compliance domains and security controls related to different compliance standards. This page lists the compliance domains and security controls for Azure Cosmos DB. You can assign the built-ins for a security control individually to help make your Azure resources compliant with the specific standard.

The title of each built-in policy definition links to the policy definition in the Azure portal. Use the link in the Policy Version column to view the source on the Azure Policy GitHub repo.

Important

Each control is associated with one or more Azure Policy definitions. These policies might help you assess compliance with the control. However, there often isn't a one-to-one or complete match between a control and one or more policies. As such, Compliant in Azure Policy refers only to the policies themselves. This doesn't ensure that you're fully compliant with all requirements of a control. In addition, the compliance standard includes controls that aren't addressed by any Azure Policy definitions at this time. Therefore, compliance in Azure Policy is only a partial view of your overall compliance status. The associations between controls and Azure Policy Regulatory Compliance definitions for these compliance standards can change over time.

CIS Microsoft Azure Foundations Benchmark 2.0.0

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for CIS v2.0.0. For more information about this compliance standard, see CIS Microsoft Azure Foundations Benchmark.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
4.5	4.5.1	Ensure That 'Firewalls & Networks' Is Limited to Use Selected Networks Instead of All Networks	Azure Cosmos DB accounts should have firewall rules	2.0.0
4.5	4.5.2	Ensure That Private Endpoints Are Used Where Possible	CosmosDB accounts should use private link	1.0.0
4.5	4.5.3	Use Azure Active Directory (AAD) Client Authentication and Azure RBAC where possible.	Cosmos DB database accounts should have local authentication methods disabled	1.1.0

CMMC Level 3

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CMMC Level 3. For more information about this compliance standard, see Cybersecurity Maturity Model Certification (CMMC).

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Incident Response	IR.2.093	Detect and report events.	Deploy Advanced Threat Protection for Cosmos DB Accounts	1.0.0

FedRAMP High

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP High. For more information about this compliance standard, see FedRAMP High.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Access Control	AC-4	Information Flow Enforcement	Azure Cosmos DB accounts should have firewall rules	2.0.0
Access Control	AC-4	Information Flow Enforcement	CosmosDB accounts should use private link	1.0.0
Access Control	AC-17	Remote Access	CosmosDB accounts should use private link	1.0.0
Access Control	AC-17 (1)	Automated Monitoring / Control	CosmosDB accounts should use private link	1.0.0
System And Communications Protection	SC-7	Boundary Protection	Azure Cosmos DB accounts should have firewall rules	2.0.0
System And Communications Protection	SC-7	Boundary Protection	CosmosDB accounts should use private link	1.0.0
System And Communications Protection	SC-7 (3)	Access Points	Azure Cosmos DB accounts should have firewall rules	2.0.0
System And Communications Protection	SC-7 (3)	Access Points	CosmosDB accounts should use private link	1.0.0
System And Communications Protection	SC-12	Cryptographic Key Establishment And Management	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0

FedRAMP Moderate

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP Moderate. For more information about this compliance standard, see FedRAMP Moderate.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Access Control	AC-4	Information Flow Enforcement	Azure Cosmos DB accounts should have firewall rules	2.0.0
Access Control	AC-4	Information Flow Enforcement	CosmosDB accounts should use private link	1.0.0
Access Control	AC-17	Remote Access	CosmosDB accounts should use private link	1.0.0
Access Control	AC-17 (1)	Automated Monitoring / Control	CosmosDB accounts should use private link	1.0.0
System And Communications Protection	SC-7	Boundary Protection	Azure Cosmos DB accounts should have firewall rules	2.0.0
System And Communications Protection	SC-7	Boundary Protection	CosmosDB accounts should use private link	1.0.0
System And Communications Protection	SC-7 (3)	Access Points	Azure Cosmos DB accounts should have firewall rules	2.0.0
System And Communications Protection	SC-7 (3)	Access Points	CosmosDB accounts should use private link	1.0.0
System And Communications Protection	SC-12	Cryptographic Key Establishment And Management	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0

HIPAA HITRUST 9.2

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - HIPAA HITRUST 9.2. For more information about this compliance standard, see HIPAA HITRUST 9.2.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
08 Network Protection	0805.01m1Organizational.12-01.m	0805.01m1Organizational.12-01.m 01.04 Network Access Control	Cosmos DB should use a virtual network service endpoint	1.0.0
08 Network Protection	0806.01m2Organizational.12356-01.m	0806.01m2Organizational.12356-01.m 01.04 Network Access Control	Cosmos DB should use a virtual network service endpoint	1.0.0
08 Network Protection	0864.09m2Organizational.12-09.m	0864.09m2Organizational.12-09.m 09.06 Network Security Management	Cosmos DB should use a virtual network service endpoint	1.0.0
08 Network Protection	0894.01m2Organizational.7-01.m	0894.01m2Organizational.7-01.m 01.04 Network Access Control	Cosmos DB should use a virtual network service endpoint	1.0.0

Microsoft Cloud for Sovereignty Baseline Confidential Policies

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for MCfS Sovereignty Baseline Confidential Policies. For more information about this compliance standard, see Microsoft Cloud for Sovereignty Policy portfolio.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
SO.1 - Data Residency	SO.1	Azure products must be deployed to and configured to use approved regions.	Azure Cosmos DB allowed locations	1.1.0

Microsoft Cloud for Sovereignty Baseline Global Policies

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for MCfS Sovereignty Baseline Global Policies. For more information about this compliance standard, see Microsoft Cloud for Sovereignty Policy portfolio.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
SO.1 - Data Residency	SO.1	Azure products must be deployed to and configured to use approved regions.	Azure Cosmos DB allowed locations	1.1.0

Microsoft cloud security benchmark

The Microsoft cloud security benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Microsoft cloud security benchmark, see the Azure Security Benchmark mapping files.

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Microsoft cloud security benchmark.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Network Security	NS-2	Secure cloud services with network controls	Azure Cosmos DB accounts should have firewall rules	2.0.0
Network Security	NS-2	Secure cloud services with network controls	Azure Cosmos DB should disable public network access	1.0.0
Network Security	NS-2	Secure cloud services with network controls	CosmosDB accounts should use private link	1.0.0
Identity Management	IM-1	Use centralized identity and authentication system	Cosmos DB database accounts should have local authentication methods disabled	1.1.0
Data Protection	DP-5	Use customer-managed key option in data at rest encryption when required	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0

NIST SP 800-171 R2

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-171 R2. For more information about this compliance standard, see NIST SP 800-171 R2.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Access Control	3.1.1	Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).	CosmosDB accounts should use private link	1.0.0
Access Control	3.1.12	Monitor and control remote access sessions.	CosmosDB accounts should use private link	1.0.0
Access Control	3.1.13	Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.	CosmosDB accounts should use private link	1.0.0
Access Control	3.1.14	Route remote access via managed access control points.	CosmosDB accounts should use private link	1.0.0
Access Control	3.1.3	Control the flow of CUI in accordance with approved authorizations.	Azure Cosmos DB accounts should have firewall rules	2.0.0
Access Control	3.1.3	Control the flow of CUI in accordance with approved authorizations.	CosmosDB accounts should use private link	1.0.0
System and Communications Protection	3.13.1	Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.	Azure Cosmos DB accounts should have firewall rules	2.0.0
System and Communications Protection	3.13.1	Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.	CosmosDB accounts should use private link	1.0.0
System and Communications Protection	3.13.10	Establish and manage cryptographic keys for cryptography employed in organizational systems.	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0
System and Communications Protection	3.13.2	Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.	Azure Cosmos DB accounts should have firewall rules	2.0.0
System and Communications Protection	3.13.2	Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.	CosmosDB accounts should use private link	1.0.0
System and Communications Protection	3.13.5	Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.	Azure Cosmos DB accounts should have firewall rules	2.0.0
System and Communications Protection	3.13.5	Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.	CosmosDB accounts should use private link	1.0.0
System and Communications Protection	3.13.6	Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).	Azure Cosmos DB accounts should have firewall rules	2.0.0

NIST SP 800-53 Rev. 4

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 4. For more information about this compliance standard, see NIST SP 800-53 Rev. 4.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Access Control	AC-4	Information Flow Enforcement	Azure Cosmos DB accounts should have firewall rules	2.0.0
Access Control	AC-4	Information Flow Enforcement	CosmosDB accounts should use private link	1.0.0
Access Control	AC-17	Remote Access	CosmosDB accounts should use private link	1.0.0
Access Control	AC-17 (1)	Automated Monitoring / Control	CosmosDB accounts should use private link	1.0.0
System And Communications Protection	SC-7	Boundary Protection	Azure Cosmos DB accounts should have firewall rules	2.0.0
System And Communications Protection	SC-7	Boundary Protection	CosmosDB accounts should use private link	1.0.0
System And Communications Protection	SC-7 (3)	Access Points	Azure Cosmos DB accounts should have firewall rules	2.0.0
System And Communications Protection	SC-7 (3)	Access Points	CosmosDB accounts should use private link	1.0.0
System And Communications Protection	SC-12	Cryptographic Key Establishment And Management	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0

NIST SP 800-53 Rev. 5

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 5. For more information about this compliance standard, see NIST SP 800-53 Rev. 5.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Access Control	AC-4	Information Flow Enforcement	Azure Cosmos DB accounts should have firewall rules	2.0.0
Access Control	AC-4	Information Flow Enforcement	CosmosDB accounts should use private link	1.0.0
Access Control	AC-17	Remote Access	CosmosDB accounts should use private link	1.0.0
Access Control	AC-17 (1)	Monitoring and Control	CosmosDB accounts should use private link	1.0.0
System and Communications Protection	SC-7	Boundary Protection	Azure Cosmos DB accounts should have firewall rules	2.0.0
System and Communications Protection	SC-7	Boundary Protection	CosmosDB accounts should use private link	1.0.0
System and Communications Protection	SC-7 (3)	Access Points	Azure Cosmos DB accounts should have firewall rules	2.0.0
System and Communications Protection	SC-7 (3)	Access Points	CosmosDB accounts should use private link	1.0.0
System and Communications Protection	SC-12	Cryptographic Key Establishment and Management	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0

NL BIO Cloud Theme

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for NL BIO Cloud Theme. For more information about this compliance standard, see Baseline Information Security Government Cybersecurity - Digital Government (digitaleoverheid.nl).

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
U.05.2 Data protection - Cryptographic measures	U.05.2	Data stored in the cloud service shall be protected to the latest state of the art.	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0
U.07.1 Data separation - Isolated	U.07.1	Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner.	Azure Cosmos DB accounts should have firewall rules	2.0.0
U.07.1 Data separation - Isolated	U.07.1	Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner.	Azure Cosmos DB should disable public network access	1.0.0
U.07.1 Data separation - Isolated	U.07.1	Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner.	CosmosDB accounts should use private link	1.0.0
U.11.3 Cryptoservices - Encrypted	U.11.3	Sensitive data is always encrypted, with private keys managed by the CSC.	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0

Reserve Bank of India - IT Framework for NBFC

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Reserve Bank of India - IT Framework for NBFC. For more information about this compliance standard, see Reserve Bank of India - IT Framework for NBFC.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Information and Cyber Security	3.1.h	Public Key Infrastructure (PKI)-3.1	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0
IS Audit	5	Policy for Information System Audit (IS Audit)-5	Azure Cosmos DB accounts should have firewall rules	2.0.0

Reserve Bank of India IT Framework for Banks v2016

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RBI ITF Banks v2016. For more information about this compliance standard, see RBI ITF Banks v2016 (PDF).

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Metrics		Metrics-21.1	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0

RMIT Malaysia

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RMIT Malaysia. For more information about this compliance standard, see RMIT Malaysia.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Network Resilience	10.33	Network Resilience - 10.33	Cosmos DB should use a virtual network service endpoint	1.0.0

SWIFT CSP-CSCF v2021

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for SWIFT CSP-CSCF v2021. For more information about this compliance standard, see SWIFT CSP CSCF v2021.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
SWIFT Environment Protection	1.1	SWIFT Environment Protection	Cosmos DB should use a virtual network service endpoint	1.0.0
Detect Anomalous Activity to Systems or Transaction Records	6.3	Database Integrity	Cosmos DB should use a virtual network service endpoint	1.0.0

System and Organization Controls (SOC) 2

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for System and Organization Controls (SOC) 2. For more information about this compliance standard, see System and Organization Controls (SOC) 2.

Domain	Control ID	Control title	Policy (Azure portal)	Policy version (GitHub)
Logical and Physical Access Controls	CC6.1	Logical access security software, infrastructure, and architectures	Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest	1.1.0

Next steps

• Learn more about Azure Policy Regulatory Compliance.
• See the built-ins on the Azure Policy GitHub repo.