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 below is associated with one or more Azure Policy definitions. These policies may help you assess compliance with the control; however, there often is not 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 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 may 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-1 Implement security for internal traffic Azure Key Vault should disable public network access 2.0.0-preview
Network Security NS-2 Connect private networks together Private endpoint should be configured for Key Vault 1.1.0-preview
Network Security NS-3 Establish private network access to Azure services Private endpoint should be configured for Key Vault 1.1.0-preview
Network Security NS-4 Protect applications and services from external network attacks Azure Key Vault should disable public network access 2.0.0-preview
Identity Management IM-7 Eliminate unintended credential exposure Certificates should have the specified maximum validity period 2.1.0-preview
Identity Management IM-7 Eliminate unintended credential exposure Key Vault keys should have an expiration date 1.0.2
Identity Management IM-7 Eliminate unintended credential exposure Key Vault secrets should have an expiration date 1.0.2
Privileged Access PA-5 Automate entitlement management Certificates should have the specified maximum validity period 2.1.0-preview
Privileged Access PA-5 Automate entitlement management Key Vault keys should have an expiration date 1.0.2
Privileged Access PA-5 Automate entitlement management Key Vault secrets should have an expiration date 1.0.2
Logging and Threat Detection LT-4 Enable logging for Azure resources Resource logs in Key Vault should be enabled 5.0.0
Backup and Recovery BR-4 Mitigate risk of lost keys Key vaults should have purge protection enabled 2.0.0
Backup and Recovery BR-4 Mitigate risk of lost keys Key vaults should have soft delete enabled 2.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)
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.0.0
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
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
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
Other Security Considerations 8.4 Ensure the key vault is recoverable Azure Key Vault Managed HSM should have purge protection enabled 1.0.0
Other Security Considerations 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)
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
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
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
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
Other Security Considerations 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 disable public network access 2.0.0-preview
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 disable public network access 2.0.0-preview
Configuration Management CM.2.064 Establish and enforce security configuration settings for information technology products employed in organizational systems. Azure Key Vault should disable public network access 2.0.0-preview
Incident Response IR.2.093 Detect and report events. Azure Key Vault should disable public network access 2.0.0-preview
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.0.1
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 disable public network access 2.0.0-preview
System and Communications Protection SC.3.187 Establish and manage cryptographic keys for cryptography employed in organizational systems. Azure Key Vault should disable public network access 2.0.0-preview
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 2.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.0.1

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 disable public network access 2.0.0-preview
Access Control AC-4 Information Flow Enforcement Private endpoint should be configured for Key Vault 1.1.0-preview
Access Control AC-17 Remote Access Private endpoint should be configured for Key Vault 1.1.0-preview
Access Control AC-17 (1) Automated Monitoring / Control 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 2.0.0
Identification and Authentication IA-5 Authenticator Management Certificates should have the specified maximum validity period 2.1.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 disable public network access 2.0.0-preview
System and Communications Protection SC-7 Boundary Protection 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 disable public network access 2.0.0-preview
System and Communications Protection SC-7 (3) Access Points Private endpoint should be configured for Key Vault 1.1.0-preview

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 disable public network access 2.0.0-preview
Access Control AC-4 Information Flow Enforcement Private endpoint should be configured for Key Vault 1.1.0-preview
Access Control AC-17 Remote Access Private endpoint should be configured for Key Vault 1.1.0-preview
Access Control AC-17 (1) Automated Monitoring / Control 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 2.0.0
Identification and Authentication IA-5 Authenticator Management Certificates should have the specified maximum validity period 2.1.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 disable public network access 2.0.0-preview
System and Communications Protection SC-7 Boundary Protection 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 disable public network access 2.0.0-preview
System and Communications Protection SC-7 (3) Access Points Private endpoint should be configured for Key Vault 1.1.0-preview

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)
Segregation in Networks 0805.01m1Organizational.12 - 01.m The organization's security gateways (e.g. firewalls) enforce security policies and are configured to filter traffic between domains, block unauthorized access, and are used to maintain segregation between internal wired, internal wireless, and external network segments (e.g., the Internet) including DMZs and enforce access control policies for each of the domains. Key Vault should use a virtual network service endpoint 1.0.0
Segregation in Networks 0806.01m2Organizational.12356 - 01.m The organizations network is logically and physically segmented with a defined security perimeter and a graduated set of controls, including subnetworks for publicly accessible system components that are logically separated from the internal network, based on organizational requirements; and traffic is controlled based on functionality required and classification of the data/systems based on a risk assessment and their respective security requirements. Key Vault should use a virtual network service endpoint 1.0.0
Segregation in Networks 0894.01m2Organizational.7 - 01.m Networks are segregated from production-level networks when migrating physical servers, applications or data to virtualized servers. Key Vault should use a virtual network service endpoint 1.0.0
Audit Logging 1211.09aa3System.4 - 09.aa The organization verifies every ninety (90) days for each extract of covered information recorded that the data is erased or its use is still required. Resource logs in Azure Key Vault Managed HSM should be enabled 1.0.0
Audit Logging 1211.09aa3System.4 - 09.aa The organization verifies every ninety (90) days for each extract of covered information recorded that the data is erased or its use is still required. Resource logs in Key Vault should be enabled 5.0.0
Network Controls 0865.09m2Organizational.13 - 09.m The organization (i) authorizes connections from the information system to other information systems outside of the organization through the use of interconnection security agreements or other formal agreement; (ii) documents each connection, the interface characteristics, security requirements, and the nature of the information communicated; (iii) employs a deny all, permit by exception policy for allowing connections from the information system to other information systems outside of the organization; and (iv) applies a default-deny rule that drops all traffic via host-based firewalls or port filtering tools on its endpoints (workstations, servers, etc.), except those services and ports that are explicitly allowed. Key Vault should use a virtual network service endpoint 1.0.0
Business Continuity and Risk Assessment 1635.12b1Organizational.2 - 12.b Information security aspects of business continuity are (i) based on identifying events (or sequence of events) that can cause interruptions to the organization's critical business processes (e.g., equipment failure, human errors, theft, fire, natural disasters acts of terrorism); (ii) followed by a risk assessment to determine the probability and impact of such interruptions, in terms of time, damage scale and recovery period; (iii) based on the results of the risk assessment, a business continuity strategy is developed to identify the overall approach to business continuity; and (iv) once this strategy has been created, endorsement is provided by management, and a plan created and endorsed to implement this strategy. Azure Key Vault Managed HSM should have purge protection enabled 1.0.0
Business Continuity and Risk Assessment 1635.12b1Organizational.2 - 12.b Information security aspects of business continuity are (i) based on identifying events (or sequence of events) that can cause interruptions to the organization's critical business processes (e.g., equipment failure, human errors, theft, fire, natural disasters acts of terrorism); (ii) followed by a risk assessment to determine the probability and impact of such interruptions, in terms of time, damage scale and recovery period; (iii) based on the results of the risk assessment, a business continuity strategy is developed to identify the overall approach to business continuity; and (iv) once this strategy has been created, endorsement is provided by management, and a plan created and endorsed to implement this strategy. 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 2.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. 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 disable public network access 2.0.0-preview
Access Control AC-4 Information Flow Enforcement Private endpoint should be configured for Key Vault 1.1.0-preview
Access Control AC-17 Remote Access Private endpoint should be configured for Key Vault 1.1.0-preview
Access Control AC-17 (1) Automated Monitoring / Control 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 2.0.0
Identification and Authentication IA-5 Authenticator Management Certificates should have the specified maximum validity period 2.1.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 disable public network access 2.0.0-preview
System and Communications Protection SC-7 Boundary Protection 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 disable public network access 2.0.0-preview
System and Communications Protection SC-7 (3) Access Points Private endpoint should be configured for Key Vault 1.1.0-preview

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 disable public network access 2.0.0-preview
Access Control AC-4 Information Flow Enforcement Private endpoint should be configured for Key Vault 1.1.0-preview
Access Control AC-17 Remote Access Private endpoint should be configured for Key Vault 1.1.0-preview
Access Control AC-17 (1) Monitoring and Control 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 2.0.0
Identification and Authentication IA-5 Authenticator Management Certificates should have the specified maximum validity period 2.1.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 disable public network access 2.0.0-preview
System and Communications Protection SC-7 Boundary Protection 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 disable public network access 2.0.0-preview
System and Communications Protection SC-7 (3) Access Points Private endpoint should be configured for Key Vault 1.1.0-preview

Next steps