Azure Policy Regulatory Compliance controls for Azure Key Vault
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 Key Vault. 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 1.1.0
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CIS Microsoft Azure Foundations Benchmark 1.1.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) |
|---|---|---|---|---|
| 5 Logging and Monitoring | 5.1.7 | Ensure that logging for Azure KeyVault is 'Enabled' | Resource logs in Azure Key Vault Managed HSM should be enabled | 1.1.0 |
| 5 Logging and Monitoring | 5.1.7 | Ensure that logging for Azure KeyVault is 'Enabled' | Resource logs in Key Vault should be enabled | 5.0.0 |
| 8 Other Security Considerations | 8.1 | Ensure that the expiration date is set on all keys | Key Vault keys should have an expiration date | 1.0.2 |
| 8 Other Security Considerations | 8.2 | Ensure that the expiration date is set on all Secrets | Key Vault secrets should have an expiration date | 1.0.2 |
| 8 Other Security Considerations | 8.4 | Ensure the key vault is recoverable | Azure Key Vault Managed HSM should have purge protection enabled | 1.0.0 |
| 8 Other Security Considerations | 8.4 | Ensure the key vault is recoverable | Key vaults should have deletion protection enabled | 2.1.0 |
CIS Microsoft Azure Foundations Benchmark 1.3.0
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CIS Microsoft Azure Foundations Benchmark 1.3.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) |
|---|---|---|---|---|
| 5 Logging and Monitoring | 5.1.5 | Ensure that logging for Azure KeyVault is 'Enabled' | Resource logs in Key Vault should be enabled | 5.0.0 |
| 5 Logging and Monitoring | 5.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in Key Vault should be enabled | 5.0.0 |
| 8 Other Security Considerations | 8.1 | Ensure that the expiration date is set on all keys | Key Vault keys should have an expiration date | 1.0.2 |
| 8 Other Security Considerations | 8.2 | Ensure that the expiration date is set on all Secrets | Key Vault secrets should have an expiration date | 1.0.2 |
| 8 Other Security Considerations | 8.4 | Ensure the key vault is recoverable | Key vaults should have deletion protection enabled | 2.1.0 |
CIS Microsoft Azure Foundations Benchmark 1.4.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 v1.4.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) |
|---|---|---|---|---|
| 5 Logging and Monitoring | 5.1.5 | Ensure that logging for Azure KeyVault is 'Enabled' | Resource logs in Key Vault should be enabled | 5.0.0 |
| 5 Logging and Monitoring | 5.3 | Ensure that Diagnostic Logs Are Enabled for All Services that Support it. | Resource logs in Key Vault should be enabled | 5.0.0 |
| 8 Other Security Considerations | 8.1 | Ensure that the Expiration Date is set for all Keys in RBAC Key Vaults | Key Vault keys should have an expiration date | 1.0.2 |
| 8 Other Security Considerations | 8.2 | Ensure that the Expiration Date is set for all Keys in Non-RBAC Key Vaults. | Key Vault keys should have an expiration date | 1.0.2 |
| 8 Other Security Considerations | 8.3 | Ensure that the Expiration Date is set for all Secrets in RBAC Key Vaults | Key Vault secrets should have an expiration date | 1.0.2 |
| 8 Other Security Considerations | 8.4 | Ensure that the Expiration Date is set for all Secrets in Non-RBAC Key Vaults | Key Vault secrets should have an expiration date | 1.0.2 |
| 8 Other Security Considerations | 8.6 | Ensure the key vault is recoverable | Key vaults should have deletion protection enabled | 2.1.0 |
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) |
|---|---|---|---|---|
| 5.1 | 5.1.5 | Ensure that logging for Azure Key Vault is 'Enabled' | Resource logs in Key Vault should be enabled | 5.0.0 |
| 5 | 5.4 | Ensure that Azure Monitor Resource Logging is Enabled for All Services that Support it | Resource logs in Key Vault should be enabled | 5.0.0 |
| 8 | 8.1 | Ensure that the Expiration Date is set for all Keys in RBAC Key Vaults | Key Vault keys should have an expiration date | 1.0.2 |
| 8 | 8.2 | Ensure that the Expiration Date is set for all Keys in Non-RBAC Key Vaults. | Key Vault keys should have an expiration date | 1.0.2 |
| 8 | 8.3 | Ensure that the Expiration Date is set for all Secrets in RBAC Key Vaults | Key Vault secrets should have an expiration date | 1.0.2 |
| 8 | 8.4 | Ensure that the Expiration Date is set for all Secrets in Non-RBAC Key Vaults | Key Vault secrets should have an expiration date | 1.0.2 |
| 8 | 8.5 | Ensure the Key Vault is Recoverable | Key vaults should have deletion protection enabled | 2.1.0 |
| 8 | 8.5 | Ensure the Key Vault is Recoverable | Key vaults should have soft delete enabled | 3.0.0 |
| 8 | 8.6 | Enable Role Based Access Control for Azure Key Vault | [Preview]: Azure Key Vault should use RBAC permission model | 1.0.0-preview |
| 8 | 8.7 | Ensure that Private Endpoints are Used for Azure Key Vault | Azure Key Vaults should use private link | 1.2.1 |
| 8 | 8.8 | Ensure Automatic Key Rotation is Enabled Within Azure Key Vault for the Supported Services | Keys should have a rotation policy ensuring that their rotation is scheduled within the specified number of days after creation. | 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) |
|---|---|---|---|---|
| Access Control | AC.1.001 | Limit information system access to authorized users, processes acting on behalf of authorized users, and devices (including other information systems). | Azure Key Vault should have firewall enabled | 3.2.1 |
| Access Control | AC.1.002 | Limit information system access to the types of transactions and functions that authorized users are permitted to execute. | Azure Key Vault should have firewall enabled | 3.2.1 |
| Configuration Management | CM.2.064 | Establish and enforce security configuration settings for information technology products employed in organizational systems. | Azure Key Vault should have firewall enabled | 3.2.1 |
| Incident Response | IR.2.093 | Detect and report events. | Azure Key Vault should have firewall enabled | 3.2.1 |
| System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Certificates using RSA cryptography should have the specified minimum key size | 2.1.0 |
| System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Keys should be the specified cryptographic type RSA or EC | 1.0.1 |
| System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Keys using elliptic curve cryptography should have the specified curve names | 1.0.1 |
| System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Keys using RSA cryptography should have a specified minimum key size | 1.0.1 |
| System and Communications Protection | SC.3.183 | Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). | Azure Key Vault should have firewall enabled | 3.2.1 |
| System and Communications Protection | SC.3.187 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Azure Key Vault should have firewall enabled | 3.2.1 |
| System and Communications Protection | SC.3.187 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Key Vault keys should have an expiration date | 1.0.2 |
| System and Communications Protection | SC.3.187 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Key vaults should have deletion protection enabled | 2.1.0 |
| System and Communications Protection | SC.3.187 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Key vaults should have soft delete enabled | 3.0.0 |
| System and Communications Protection | SC.3.187 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Keys should be the specified cryptographic type RSA or EC | 1.0.1 |
| System and Communications Protection | SC.3.187 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Keys using elliptic curve cryptography should have the specified curve names | 1.0.1 |
| System and Communications Protection | SC.3.187 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Keys using RSA cryptography should have a specified minimum key size | 1.0.1 |
| System and Communications Protection | SC.3.190 | Protect the authenticity of communications sessions. | Certificates using RSA cryptography should have the specified minimum key size | 2.1.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 Key Vault should have firewall enabled | 3.2.1 |
| Access Control | AC-4 | Information Flow Enforcement | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | AC-17 | Remote Access | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Azure Key Vaults should use private link | 1.2.1 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Key Vault should be enabled | 5.0.0 |
| Contingency Planning | CP-9 | Information System Backup | Key vaults should have deletion protection enabled | 2.1.0 |
| Contingency Planning | CP-9 | Information System Backup | Key vaults should have soft delete enabled | 3.0.0 |
| Identification And Authentication | IA-5 | Authenticator Management | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview |
| Identification And Authentication | IA-5 | Authenticator Management | Key Vault keys should have an expiration date | 1.0.2 |
| Identification And Authentication | IA-5 | Authenticator Management | Key Vault secrets should have an expiration date | 1.0.2 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Key Vault should have firewall enabled | 3.2.1 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Key Vaults should use private link | 1.2.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Key Vault should have firewall enabled | 3.2.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Key Vaults should use private link | 1.2.1 |
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 Key Vault should have firewall enabled | 3.2.1 |
| Access Control | AC-4 | Information Flow Enforcement | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | AC-17 | Remote Access | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Azure Key Vaults should use private link | 1.2.1 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Key Vault should be enabled | 5.0.0 |
| Contingency Planning | CP-9 | Information System Backup | Key vaults should have deletion protection enabled | 2.1.0 |
| Contingency Planning | CP-9 | Information System Backup | Key vaults should have soft delete enabled | 3.0.0 |
| Identification And Authentication | IA-5 | Authenticator Management | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview |
| Identification And Authentication | IA-5 | Authenticator Management | Key Vault keys should have an expiration date | 1.0.2 |
| Identification And Authentication | IA-5 | Authenticator Management | Key Vault secrets should have an expiration date | 1.0.2 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Key Vault should have firewall enabled | 3.2.1 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Key Vaults should use private link | 1.2.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Key Vault should have firewall enabled | 3.2.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Key Vaults should use private link | 1.2.1 |
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 | Key Vault 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 | Key Vault should use a virtual network service endpoint | 1.0.0 |
| 08 Network Protection | 0865.09m2Organizational.13-09.m | 0865.09m2Organizational.13-09.m 09.06 Network Security Management | Key Vault 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 | Key Vault should use a virtual network service endpoint | 1.0.0 |
| 12 Audit Logging & Monitoring | 1211.09aa3System.4-09.aa | 1211.09aa3System.4-09.aa 09.10 Monitoring | Resource logs in Azure Key Vault Managed HSM should be enabled | 1.1.0 |
| 12 Audit Logging & Monitoring | 1211.09aa3System.4-09.aa | 1211.09aa3System.4-09.aa 09.10 Monitoring | Resource logs in Key Vault should be enabled | 5.0.0 |
| 16 Business Continuity & Disaster Recovery | 1635.12b1Organizational.2-12.b | 1635.12b1Organizational.2-12.b 12.01 Information Security Aspects of Business Continuity Management | Azure Key Vault Managed HSM should have purge protection enabled | 1.0.0 |
| 16 Business Continuity & Disaster Recovery | 1635.12b1Organizational.2-12.b | 1635.12b1Organizational.2-12.b 12.01 Information Security Aspects of Business Continuity Management | Key vaults should have deletion protection enabled | 2.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 Key Vault should have firewall enabled | 3.2.1 |
| Network Security | NS-2 | Secure cloud services with network controls | Azure Key Vaults should use private link | 1.2.1 |
| Data Protection | DP-6 | Use a secure key management process | Key Vault keys should have an expiration date | 1.0.2 |
| Data Protection | DP-6 | Use a secure key management process | Key Vault secrets should have an expiration date | 1.0.2 |
| Data Protection | DP-7 | Use a secure certificate management process | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview |
| Data Protection | DP-8 | Ensure security of key and certificate repository | Azure Key Vault should have firewall enabled | 3.2.1 |
| Data Protection | DP-8 | Ensure security of key and certificate repository | Azure Key Vaults should use private link | 1.2.1 |
| Data Protection | DP-8 | Ensure security of key and certificate repository | Key vaults should have deletion protection enabled | 2.1.0 |
| Data Protection | DP-8 | Ensure security of key and certificate repository | Key vaults should have soft delete enabled | 3.0.0 |
| Data Protection | DP-8 | Ensure security of key and certificate repository | Resource logs in Key Vault should be enabled | 5.0.0 |
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in Key Vault should be enabled | 5.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) |
|---|---|---|---|---|
| Access Control and Passwords | AC-17 | 16.6.9 Events to be logged | Resource logs in Key Vault should be enabled | 5.0.0 |
| Cryptography | CR-2 | 17.1.45 Data Recovery | Key vaults should have deletion protection enabled | 2.1.0 |
| Cryptography | CR-2 | 17.1.45 Data Recovery | Key vaults should have soft delete enabled | 3.0.0 |
| Gateway security | GS-2 | 19.1.11 Using Gateways | Azure Key Vault Managed HSM should have purge protection enabled | 1.0.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). | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | 3.1.12 | Monitor and control remote access sessions. | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | 3.1.14 | Route remote access via managed access control points. | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | Azure Key Vault should have firewall enabled | 3.2.1 |
| Access Control | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | Azure Key Vaults should use private link | 1.2.1 |
| 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 Key Vault should have firewall enabled | 3.2.1 |
| 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 Key Vaults should use private link | 1.2.1 |
| 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 Key Vault should have firewall enabled | 3.2.1 |
| 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 Key Vaults should use private link | 1.2.1 |
| System and Communications Protection | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | Azure Key Vault should have firewall enabled | 3.2.1 |
| System and Communications Protection | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | Azure Key Vaults should use private link | 1.2.1 |
| 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 Key Vault should have firewall enabled | 3.2.1 |
| Audit and Accountability | 3.3.1 | Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit and Accountability | 3.3.2 | Ensure that the actions of individual system users can be uniquely traced to those users, so they can be held accountable for their actions. | Resource logs in Key Vault should be enabled | 5.0.0 |
| Identification and Authentication | 3.5.2 | Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems. | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview |
| Identification and Authentication | 3.5.2 | Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems. | Key Vault keys should have an expiration date | 1.0.2 |
| Identification and Authentication | 3.5.2 | Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems. | Key Vault secrets should have an expiration date | 1.0.2 |
| Media Protection | 3.8.9 | Protect the confidentiality of backup CUI at storage locations. | Key vaults should have deletion protection enabled | 2.1.0 |
| Media Protection | 3.8.9 | Protect the confidentiality of backup CUI at storage locations. | Key vaults should have soft delete enabled | 3.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 Key Vault should have firewall enabled | 3.2.1 |
| Access Control | AC-4 | Information Flow Enforcement | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | AC-17 | Remote Access | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Azure Key Vaults should use private link | 1.2.1 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in Key Vault should be enabled | 5.0.0 |
| Contingency Planning | CP-9 | Information System Backup | Key vaults should have deletion protection enabled | 2.1.0 |
| Contingency Planning | CP-9 | Information System Backup | Key vaults should have soft delete enabled | 3.0.0 |
| Identification And Authentication | IA-5 | Authenticator Management | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview |
| Identification And Authentication | IA-5 | Authenticator Management | Key Vault keys should have an expiration date | 1.0.2 |
| Identification And Authentication | IA-5 | Authenticator Management | Key Vault secrets should have an expiration date | 1.0.2 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Key Vault should have firewall enabled | 3.2.1 |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Key Vaults should use private link | 1.2.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Key Vault should have firewall enabled | 3.2.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Key Vaults should use private link | 1.2.1 |
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 Key Vault should have firewall enabled | 3.2.1 |
| Access Control | AC-4 | Information Flow Enforcement | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | AC-17 | Remote Access | Azure Key Vaults should use private link | 1.2.1 |
| Access Control | AC-17 (1) | Monitoring and Control | Azure Key Vaults should use private link | 1.2.1 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in Key Vault should be enabled | 5.0.0 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in Key Vault should be enabled | 5.0.0 |
| Contingency Planning | CP-9 | System Backup | Key vaults should have deletion protection enabled | 2.1.0 |
| Contingency Planning | CP-9 | System Backup | Key vaults should have soft delete enabled | 3.0.0 |
| Identification and Authentication | IA-5 | Authenticator Management | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview |
| Identification and Authentication | IA-5 | Authenticator Management | Key Vault keys should have an expiration date | 1.0.2 |
| Identification and Authentication | IA-5 | Authenticator Management | Key Vault secrets should have an expiration date | 1.0.2 |
| System and Communications Protection | SC-7 | Boundary Protection | Azure Key Vault should have firewall enabled | 3.2.1 |
| System and Communications Protection | SC-7 | Boundary Protection | Azure Key Vaults should use private link | 1.2.1 |
| System and Communications Protection | SC-7 (3) | Access Points | Azure Key Vault should have firewall enabled | 3.2.1 |
| System and Communications Protection | SC-7 (3) | Access Points | Azure Key Vaults should use private link | 1.2.1 |
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.04.1 Data and Cloud Service Recovery - Restore function | U.04.1 | The data and cloud services are restored within the agreed period and maximum data loss and made available to the CSC. | Key vaults should have deletion protection enabled | 2.1.0 |
| U.04.1 Data and Cloud Service Recovery - Restore function | U.04.1 | The data and cloud services are restored within the agreed period and maximum data loss and made available to the CSC. | Key vaults should have soft delete enabled | 3.0.0 |
| U.04.2 Data and Cloud Service Recovery - Restore function | U.04.2 | The continuous process of recoverable protection of data is monitored. | Key vaults should have deletion protection enabled | 2.1.0 |
| U.04.2 Data and Cloud Service Recovery - Restore function | U.04.2 | The continuous process of recoverable protection of data is monitored. | Key vaults should have soft delete enabled | 3.0.0 |
| U.04.3 Data and Cloud Service Recovery - Tested | U.04.3 | The functioning of recovery functions is periodically tested and the results are shared with the CSC. | Key vaults should have deletion protection enabled | 2.1.0 |
| U.04.3 Data and Cloud Service Recovery - Tested | U.04.3 | The functioning of recovery functions is periodically tested and the results are shared with the CSC. | Key vaults should have soft delete enabled | 3.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 Key Vault should have firewall enabled | 3.2.1 |
| 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 Key Vaults should use private link | 1.2.1 |
| U.15.1 Logging and monitoring - Events logged | U.15.1 | The violation of the policy rules is recorded by the CSP and the CSC. | Resource logs in Key Vault should be enabled | 5.0.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) |
|---|---|---|---|---|
| Access Control and Passwords | AC-18 | 16.6.9 Events to be logged | Resource logs in Key Vault should be enabled | 5.0.0 |
| Cryptography | CR-15 | 17.9.25 Contents of KMPs | Key Vault keys should have an expiration date | 1.0.2 |
| Cryptography | CR-15 | 17.9.25 Contents of KMPs | Key Vault secrets should have an expiration date | 1.0.2 |
| Cryptography | CR-2 | 17.1.52 Data Recovery | Key vaults should have deletion protection enabled | 2.1.0 |
| Cryptography | CR-2 | 17.1.52 Data Recovery | Key vaults should have soft delete enabled | 3.0.0 |
| Cryptography | CR-5 | 17.2.24 Using RSA | Certificates using RSA cryptography should have the specified minimum key size | 2.1.0 |
| Gateway security | GS-2 | 19.1.11 Using Gateways | Azure Key Vault Managed HSM should have purge protection enabled | 1.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 | 3.1.h | Public Key Infrastructure (PKI)-3.1 | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview |
| Information and Cyber Security | 3.1.h | Public Key Infrastructure (PKI)-3.1 | Azure Key Vault should have firewall enabled | 3.2.1 |
| Information and Cyber Security | 3.1.h | Public Key Infrastructure (PKI)-3.1 | Azure Key Vaults should use private link | 1.2.1 |
| Information and Cyber Security | 3.1.h | Public Key Infrastructure (PKI)-3.1 | Key Vault keys should have an expiration date | 1.0.2 |
| Information and Cyber Security | 3.1.h | Public Key Infrastructure (PKI)-3.1 | Key Vault secrets should have an expiration date | 1.0.2 |
| Information and Cyber Security | 3.1.h | Public Key Infrastructure (PKI)-3.1 | Key vaults should have deletion protection enabled | 2.1.0 |
| Information and Cyber Security | 3.1.h | Public Key Infrastructure (PKI)-3.1 | Key vaults should have soft delete enabled | 3.0.0 |
| Information and Cyber Security | 3.8 | Digital Signatures-3.8 | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview |
| Information and Cyber Security | 3.8 | Digital Signatures-3.8 | Certificates should be issued by the specified integrated certificate authority | 2.1.0 |
| Information and Cyber Security | 3.8 | Digital Signatures-3.8 | Certificates should use allowed key types | 2.1.0 |
| Information and Cyber Security | 3.8 | Digital Signatures-3.8 | Certificates using elliptic curve cryptography should have allowed curve names | 2.1.0 |
| Information and Cyber Security | 3.8 | Digital Signatures-3.8 | Certificates using RSA cryptography should have the specified minimum key size | 2.1.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 | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview | |
| Metrics | Metrics-21.1 | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Azure Key Vault should have firewall enabled | 3.2.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Azure Key Vault should have firewall enabled | 3.2.1 | |
| Metrics | Metrics-21.1 | Azure Key Vault should have firewall enabled | 3.2.1 | |
| Anti-Phishing | Anti-Phishing-14.1 | Azure Key Vault should have firewall enabled | 3.2.1 | |
| Metrics | Metrics-21.1 | Azure Key Vault should have firewall enabled | 3.2.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Azure Key Vaults should use private link | 1.2.1 | |
| Metrics | Metrics-21.1 | Azure Key Vaults should use private link | 1.2.1 | |
| Metrics | Metrics-21.1 | Azure Key Vaults should use private link | 1.2.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Azure Key Vaults should use private link | 1.2.1 | |
| Anti-Phishing | Anti-Phishing-14.1 | Azure Key Vaults should use private link | 1.2.1 | |
| Metrics | Metrics-21.1 | Key vaults should have deletion protection enabled | 2.1.0 | |
| Metrics | Metrics-21.1 | Key vaults should have deletion protection enabled | 2.1.0 | |
| Metrics | Metrics-21.1 | Key vaults should have soft delete enabled | 3.0.0 | |
| Metrics | Metrics-21.1 | Key vaults should have soft delete enabled | 3.0.0 | |
| Audit Log Settings | Audit Log Settings-17.1 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.3 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.3 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Application Security Life Cycle (Aslc) | Application Security Life Cycle (Aslc)-6.4 | Resource logs in Key Vault should be enabled | 5.0.0 | |
| Maintenance, Monitoring, And Analysis Of Audit Logs | Maintenance, Monitoring, And Analysis Of Audit Logs-16.3 | Resource logs in Key Vault should be enabled | 5.0.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) |
|---|---|---|---|---|
| Cryptography | 10.16 | Cryptography - 10.16 | Azure Key Vault Managed HSM should have purge protection enabled | 1.0.0 |
| Cryptography | 10.16 | Cryptography - 10.16 | Key vaults should have deletion protection enabled | 2.1.0 |
| Cryptography | 10.16 | Cryptography - 10.16 | Key vaults should have soft delete enabled | 3.0.0 |
| Cryptography | 10.19 | Cryptography - 10.19 | Key Vault should use a virtual network service endpoint | 1.0.0 |
| Security of Digital Services | 10.66 | Security of Digital Services - 10.66 | Deploy Diagnostic Settings for Key Vault to Log Analytics workspace | 3.0.0 |
| Security of Digital Services | 10.66 | Security of Digital Services - 10.66 | Resource logs in Azure Key Vault Managed HSM should be enabled | 1.1.0 |
| Security of Digital Services | 10.66 | Security of Digital Services - 10.66 | Resource logs in Key Vault should be enabled | 5.0.0 |
| Data Loss Prevention (DLP) | 11.15 | Data Loss Prevention (DLP) - 11.15 | Azure Key Vault Managed HSM should have purge protection enabled | 1.0.0 |
| Data Loss Prevention (DLP) | 11.15 | Data Loss Prevention (DLP) - 11.15 | Key vaults should have deletion protection enabled | 2.1.0 |
| Data Loss Prevention (DLP) | 11.15 | Data Loss Prevention (DLP) - 11.15 | Key vaults should have soft delete enabled | 3.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 | Azure Key Vault should have firewall enabled | 3.2.1 |
| SWIFT Environment Protection | 1.1 | SWIFT Environment Protection | Azure Key Vaults should use private link | 1.2.1 |
| SWIFT Environment Protection | 1.1 | SWIFT Environment Protection | Key Vault should use a virtual network service endpoint | 1.0.0 |
| Manage Identities and Segregate Privileges | 5.4 | Physical and Logical Password Storage | Key vaults should have deletion protection enabled | 2.1.0 |
| Detect Anomalous Activity to Systems or Transaction Records | 6.4 | Logging and Monitoring | Resource logs in Key Vault should be enabled | 5.0.0 |
SWIFT CSP-CSCF v2022
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 v2022. For more information about this compliance standard, see SWIFT CSP CSCF v2022.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | 1.1 | Ensure the protection of the user's local SWIFT infrastructure from potentially compromised elements of the general IT environment and external environment. | Azure Key Vault should have firewall enabled | 3.2.1 |
| 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | 1.1 | Ensure the protection of the user's local SWIFT infrastructure from potentially compromised elements of the general IT environment and external environment. | Key Vault should use a virtual network service endpoint | 1.0.0 |
| 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | 1.5A | Ensure the protection of the customer's connectivity infrastructure from external environment and potentially compromised elements of the general IT environment. | Azure Key Vault should have firewall enabled | 3.2.1 |
| 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | 1.5A | Ensure the protection of the customer's connectivity infrastructure from external environment and potentially compromised elements of the general IT environment. | Key Vault should use a virtual network service endpoint | 1.0.0 |
| 5. Manage Identities and Segregate Privileges | 5.4 | Protect physically and logically the repository of recorded passwords. | Key vaults should have deletion protection enabled | 2.1.0 |
| 6. Detect Anomalous Activity to Systems or Transaction Records | 6.4 | Record security events and detect anomalous actions and operations within the local SWIFT environment. | Resource logs in Key Vault should be enabled | 5.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