Azure Policy Regulatory Compliance controls for Azure IoT Hub
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 IoT Hub. 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) |
|---|---|---|---|---|
| Logging and Threat Detection | LT-3 | Enable logging for security investigation | Resource logs in IoT Hub should be enabled | 3.0.1 |
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) |
|---|---|---|---|---|
| Logging and Monitoring | 2.3 | Enable audit logging for Azure resources | Resource logs in IoT Hub should be enabled | 3.0.1 |
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.3 | Ensure that Diagnostic Logs are enabled for all services which support it. | Resource logs in IoT Hub should be enabled | 3.0.1 |
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) |
|---|---|---|---|---|
| Audit and Accountability | AU.3.048 | Collect audit information (e.g., logs) into one or more central repositories. | Resource logs in IoT Hub should be enabled | 3.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 | IoT Hub device provisioning service instances should use private link | 1.0.0 |
| Access Control | AC-17 | Remote Access | IoT Hub device provisioning service instances should use private link | 1.0.0 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | IoT Hub device provisioning service instances should use private link | 1.0.0 |
| Audit And Accountability | AU-6 (4) | Central Review And Analysis | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit And Accountability | AU-6 (5) | Integration / Scanning And Monitoring Capabilities | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit And Accountability | AU-12 | Audit Generation | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit And Accountability | AU-12 (1) | System-Wide / Time-Correlated Audit Trail | Resource logs in IoT Hub should be enabled | 3.0.1 |
| System And Communications Protection | SC-7 | Boundary Protection | IoT Hub device provisioning service instances should use private link | 1.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | IoT Hub device provisioning service instances should use private link | 1.0.0 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK) | 1.0.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.
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) |
|---|---|---|---|---|
| 12 Audit Logging & Monitoring | 1204.09aa1System.3-09.aa | 1204.09aa1System.3-09.aa 09.10 Monitoring | Resource logs in IoT Hub should be enabled | 3.0.1 |
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 IoT Hub should be enabled | 3.0.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 | IoT Hub device provisioning service instances should use private link | 1.0.0 |
| Access Control | AC-17 | Remote Access | IoT Hub device provisioning service instances should use private link | 1.0.0 |
| Access Control | AC-17 (1) | Monitoring and Control | IoT Hub device provisioning service instances should use private link | 1.0.0 |
| Audit and Accountability | AU-6 (4) | Central Review and Analysis | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit and Accountability | AU-6 (5) | Integrated Analysis of Audit Records | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit and Accountability | AU-12 | Audit Record Generation | Resource logs in IoT Hub should be enabled | 3.0.1 |
| Audit and Accountability | AU-12 (1) | System-wide and Time-correlated Audit Trail | Resource logs in IoT Hub should be enabled | 3.0.1 |
| System and Communications Protection | SC-7 | Boundary Protection | IoT Hub device provisioning service instances should use private link | 1.0.0 |
| System and Communications Protection | SC-7 (3) | Access Points | IoT Hub device provisioning service instances should use private link | 1.0.0 |
| System and Communications Protection | SC-12 | Cryptographic Key Establishment and Management | [Preview]: IoT Hub device provisioning service data should be encrypted using customer-managed keys (CMK) | 1.0.0-preview |
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 IoT Hub should be enabled | 3.0.1 |
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