Azure Policy built-in definitions for Azure IoT Hub
For IoT Hub sample code that shows how to implement common IoT scenarios, see the IoT Hub quickstarts. There are quickstarts for multiple programming languages including C, Node.js, and Python.
This page is an index of Azure Policy built-in policy definitions for Azure IoT Hub. For additional Azure Policy built-ins for other services, see Azure Policy built-in definitions.
The name of each built-in policy definition links to the policy definition in the Azure portal. Use the link in the Version column to view the source on the Azure Policy GitHub repo.
Azure IoT Hub
|[Preview]: [Preview]: Azure IoT Hub should use customer-managed key to encrypt data at rest||Encryption of data at rest in IoT Hub with customer-managed key adds a second layer of encryption on top of the default service-managed keys, enables customer control of keys, custom rotation policies, and ability to manage access to data through key access control. Customer-managed keys must be configured during creation of IoT Hub. For more information on how to configure customer-managed keys, see https://aka.ms/iotcmk.||Audit, Deny, Disabled||1.0.0-preview|
|[Preview]: [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK)||Use customer-managed keys to manage the encryption at rest of your IoT Hub device provisioning service. The data is automatically encrypted at rest with service-managed keys, but customer-managed keys (CMK) are commonly required to meet regulatory compliance standards. CMKs enable the data to be encrypted with an Azure Key Vault key created and owned by you. Learn more about CMK encryption at https://aka.ms/dps/CMK.||Audit, Deny, Disabled||1.0.0-preview|
|Azure IoT Hub should have local authentication methods disabled for Service Apis||Disabling local authentication methods improves security by ensuring that Azure IoT Hub exclusively require Azure Active Directory identities for Service Api authentication. Learn more at: https://aka.ms/iothubdisablelocalauth.||Audit, Deny, Disabled||1.0.0|
|Configure Azure IoT Hub to disable local authentication||Disable local authentication methods so that your Azure IoT Hub exclusively require Azure Active Directory identities for authentication. Learn more at: https://aka.ms/iothubdisablelocalauth.||Modify, Disabled||1.0.0|
|Configure IoT Hub device provisioning service instances to disable public network access||Disable public network access for your IoT Hub device provisioning instance so that it's not accessible over the public internet. This can reduce data leakage risks. Learn more at: https://aka.ms/iotdpsvnet.||Modify, Disabled||1.0.0|
|Configure IoT Hub device provisioning service instances with private endpoints||Private endpoints connect your virtual network to Azure services without a public IP address at the source or destination. By mapping private endpoints to IoT Hub device provisioning service, you can reduce data leakage risks. Learn more about private links at: https://aka.ms/iotdpsvnet.||DeployIfNotExists, Disabled||1.0.0|
|Deploy - Configure Azure IoT Hubs with private endpoints||A private endpoint is a private IP address allocated inside a customer-owned virtual network via which an Azure resource is reachable. This policy deploys a private endpoint for your IoT hub to allow services inside your virtual network to reach IoT Hub without requiring traffic to be sent to IoT Hub's public endpoint.||DeployIfNotExists, Disabled||1.0.0|
|IoT Hub device provisioning service instances should disable public network access||Disabling public network access improves security by ensuring that IoT Hub device provisioning service instance isn't exposed on the public internet. Creating private endpoints can limit exposure of the IoT Hub device provisioning instances. Learn more at: https://aka.ms/iotdpsvnet.||Audit, Deny, Disabled||1.0.0|
|IoT Hub device provisioning service instances should use private link||Azure Private Link lets you connect your virtual network to Azure services without a public IP address at the source or destination. The Private Link platform handles the connectivity between the consumer and services over the Azure backbone network. By mapping private endpoints to the IoT Hub device provisioning service, data leakage risks are reduced. Learn more about private links at: https://aka.ms/iotdpsvnet.||Audit, Disabled||1.0.0|
|Modify - Configure Azure IoT Hubs to disable public network access||Disabling the public network access property improves security by ensuring your Azure IoT Hub can only be accessed from a private endpoint. This policy disables public network access on IoT Hub resources.||Modify, Disabled||1.0.0|
|Private endpoint should be enabled for IoT Hub||Private endpoint connections enforce secure communication by enabling private connectivity to IoT Hub. Configure a private endpoint connection to enable access to traffic coming only from known networks and prevent access from all other IP addresses, including within Azure.||Audit, Disabled||1.0.0|
|Public network access on Azure IoT Hub should be disabled||Disabling the public network access property improves security by ensuring your Azure IoT Hub can only be accessed from a private endpoint.||Audit, Deny, Disabled||1.0.0|
|Resource logs in IoT Hub should be enabled||Audit enabling of resource logs. This enables you to recreate activity trails to use for investigation purposes; when a security incident occurs or when your network is compromised||AuditIfNotExists, Disabled||3.0.1|
- See the built-ins on the Azure Policy GitHub repo.
- Review the Azure Policy definition structure.
- Review Understanding policy effects.
Submit and view feedback for