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.
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 | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| Network Security | NS-2 | Secure cloud services with network controls | Azure Key Vault should have firewall enabled | 3.0.0 |
| 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 | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| Data Protection | DP-8 | Ensure security of key and certificate repository | Azure Key Vault should have firewall enabled | 3.0.0 |
| Data Protection | DP-8 | Ensure security of key and certificate repository | Key vaults should have purge protection enabled | 2.0.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 |
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 | Key Vault should use a virtual network service endpoint | 1.0.0 |
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in Key Vault should be enabled | 5.0.0 |
| Secure Configuration | 7.11 | Manage Azure secrets securely | Key vaults should have purge protection enabled | 2.0.0 |
| Data Recovery | 9.4 | Ensure protection of backups and customer managed keys | Key vaults should have purge protection enabled | 2.0.0 |
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 | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.7 | Ensure that logging for Azure KeyVault is 'Enabled' | Resource logs in Azure Key Vault Managed HSM should be enabled | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 8.4 | Ensure the key vault is recoverable | Key vaults should have purge protection enabled | 2.0.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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 8.4 | Ensure the key vault is recoverable | Key vaults should have purge protection enabled | 2.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.0.0 |
| 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.0.0 |
| 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.0.0 |
| Incident Response | IR.2.093 | Detect and report events. | Azure Key Vault should have firewall enabled | 3.0.0 |
| 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.0.0 |
| 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.0.0 |
| 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 purge protection enabled | 2.0.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 | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| Access Control | AC-4 | Information Flow Enforcement | Azure Key Vault should have firewall enabled | 3.0.0 |
| Access Control | AC-17 | Remote Access | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| Access Control | AC-17 (1) | Automated Monitoring / Control | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| 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 purge protection enabled | 2.0.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 | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Key Vault should have firewall enabled | 3.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Key Vault should have firewall enabled | 3.0.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 | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| Access Control | AC-4 | Information Flow Enforcement | Azure Key Vault should have firewall enabled | 3.0.0 |
| Access Control | AC-17 | Remote Access | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| Access Control | AC-17 (1) | Automated Monitoring / Control | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| 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 purge protection enabled | 2.0.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 | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| System And Communications Protection | SC-7 | Boundary Protection | Azure Key Vault should have firewall enabled | 3.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| System And Communications Protection | SC-7 (3) | Access Points | Azure Key Vault should have firewall enabled | 3.0.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 | 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.0.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 purge protection enabled | 2.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 purge protection enabled | 2.0.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-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 | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| Access Control | AC-4 | Information Flow Enforcement | Azure Key Vault should have firewall enabled | 3.0.0 |
| Access Control | AC-17 | Remote Access | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| Access Control | AC-17 (1) | Monitoring and Control | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| 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 purge protection enabled | 2.0.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 | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| System and Communications Protection | SC-7 | Boundary Protection | Azure Key Vault should have firewall enabled | 3.0.0 |
| System and Communications Protection | SC-7 (3) | Access Points | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| System and Communications Protection | SC-7 (3) | Access Points | Azure Key Vault should have firewall enabled | 3.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 | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Resource logs in Key Vault should be enabled | 5.0.0 |
| Cryptography | NZISM Security Benchmark CR-15 | 17.9.25 Contents of KMPs | Key Vault keys should have an expiration date | 1.0.2 |
| Cryptography | NZISM Security Benchmark CR-15 | 17.9.25 Contents of KMPs | Key Vault secrets should have an expiration date | 1.0.2 |
| Cryptography | NZISM Security Benchmark CR-2 | 17.1.52 Data Recovery | Key vaults should have purge protection enabled | 2.0.0 |
| Cryptography | NZISM Security Benchmark CR-2 | 17.1.52 Data Recovery | Key vaults should have soft delete enabled | 3.0.0 |
| Cryptography | NZISM Security Benchmark CR-5 | 17.2.24 Using RSA | Certificates using RSA cryptography should have the specified minimum key size | 2.1.0 |
| Gateway security | NZISM Security Benchmark 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 | RBI IT Framework 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 | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | [Preview]: Private endpoint should be configured for Key Vault | 1.1.0-preview |
| Information and Cyber Security | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | Azure Key Vault should have firewall enabled | 3.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | Key Vault keys should have an expiration date | 1.0.2 |
| Information and Cyber Security | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | Key Vault secrets should have an expiration date | 1.0.2 |
| Information and Cyber Security | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | Key vaults should have purge protection enabled | 2.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | Key vaults should have soft delete enabled | 3.0.0 |
| Information and Cyber Security | RBI IT Framework 3.8 | Digital Signatures-3.8 | [Preview]: Certificates should have the specified maximum validity period | 2.2.0-preview |
| Information and Cyber Security | RBI IT Framework 3.8 | Digital Signatures-3.8 | Certificates should be issued by the specified integrated certificate authority | 2.1.0 |
| Information and Cyber Security | RBI IT Framework 3.8 | Digital Signatures-3.8 | Certificates should use allowed key types | 2.1.0 |
| Information and Cyber Security | RBI IT Framework 3.8 | Digital Signatures-3.8 | Certificates using elliptic curve cryptography should have allowed curve names | 2.1.0 |
| Information and Cyber Security | RBI IT Framework 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).
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 | RMiT 10.16 | Cryptography - 10.16 | Azure Key Vault Managed HSM should have purge protection enabled | 1.0.0 |
| Cryptography | RMiT 10.16 | Cryptography - 10.16 | Key vaults should have purge protection enabled | 2.0.0 |
| Cryptography | RMiT 10.16 | Cryptography - 10.16 | Key vaults should have soft delete enabled | 3.0.0 |
| Cryptography | RMiT 10.19 | Cryptography - 10.19 | Key Vault should use a virtual network service endpoint | 1.0.0 |
| Security of Digital Services | RMiT 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 | RMiT 10.66 | Security of Digital Services - 10.66 | Resource logs in Azure Key Vault Managed HSM should be enabled | 1.0.0 |
| Security of Digital Services | RMiT 10.66 | Security of Digital Services - 10.66 | Resource logs in Key Vault should be enabled | 5.0.0 |
| Data Loss Prevention (DLP) | RMiT 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) | RMiT 11.15 | Data Loss Prevention (DLP) - 11.15 | Key vaults should have purge protection enabled | 2.0.0 |
| Data Loss Prevention (DLP) | RMiT 11.15 | Data Loss Prevention (DLP) - 11.15 | Key vaults should have soft delete enabled | 3.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