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.
Azure Security Benchmark
The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure 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 - Azure 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 |
| Identity Management | IM-1 | Use centralized identity and authentication system | Cosmos DB database accounts should have local authentication methods disabled | 1.0.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 |
Azure Security Benchmark v1
The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure 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 - Azure Security Benchmark.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Network Security | 1.1 | Protect resources using Network Security Groups or Azure Firewall on your Virtual Network | Cosmos DB should use a virtual network service endpoint | 1.0.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 |
New Zealand ISM Restricted
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - New Zealand ISM Restricted. For more information about this compliance standard, see New Zealand ISM Restricted.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Cryptography | CR-3 | 17.1.46 Reducing storage and physical transfer requirements | Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest | 1.1.0 |
| Gateway security | GS-3 | 19.1.12 Configuration of Gateways | Azure Cosmos DB accounts should have firewall rules | 2.0.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 |
NZ ISM Restricted v3.5
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NZ ISM Restricted v3.5. For more information about this compliance standard, see NZ ISM Restricted v3.5.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Cryptography | NZISM Security Benchmark CR-3 | 17.1.53 Reducing storage and physical transfer requirements | Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest | 1.1.0 |
| Gateway security | NZISM Security Benchmark GS-3 | 19.1.12 Configuration of Gateways | Azure Cosmos DB accounts should have firewall rules | 2.0.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 | RBI IT Framework 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 | RBI IT Framework 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 | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | Azure Cosmos DB accounts should use customer-managed keys to encrypt data at rest | 1.1.0 | |
| 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 | RMiT 10.33 | Network Resilience - 10.33 | Cosmos DB should use a virtual network service endpoint | 1.0.0 |
Next steps
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.
Feedback
Submit and view feedback for