Azure Policy Regulatory Compliance controls for Azure Data Box
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 Data Box. 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.
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) |
---|---|---|---|---|
System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Azure Data Box jobs should enable double encryption for data at rest on the device | 1.0.0 |
System and Communications Protection | SC.3.191 | Protect the confidentiality of CUI at rest. | Azure Data Box jobs should enable double encryption for data at rest on the device | 1.0.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) |
---|---|---|---|---|
System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password | 1.0.0 |
System And Communications Protection | SC-28 | Protection Of Information At Rest | Azure Data Box jobs should enable double encryption for data at rest on the device | 1.0.0 |
System And Communications Protection | SC-28 (1) | Cryptographic Protection | Azure Data Box jobs should enable double encryption for data at rest on the device | 1.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) |
---|---|---|---|---|
System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password | 1.0.0 |
System And Communications Protection | SC-28 | Protection Of Information At Rest | Azure Data Box jobs should enable double encryption for data at rest on the device | 1.0.0 |
System And Communications Protection | SC-28 (1) | Cryptographic Protection | Azure Data Box jobs should enable double encryption for data at rest on the device | 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) |
---|---|---|---|---|
System and Communications Protection | 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password | 1.0.0 |
System and Communications Protection | 3.13.16 | Protect the confidentiality of CUI at rest. | Azure Data Box jobs should enable double encryption for data at rest on the device | 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) |
---|---|---|---|---|
System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password | 1.0.0 |
System And Communications Protection | SC-28 | Protection Of Information At Rest | Azure Data Box jobs should enable double encryption for data at rest on the device | 1.0.0 |
System And Communications Protection | SC-28 (1) | Cryptographic Protection | Azure Data Box jobs should enable double encryption for data at rest on the device | 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) |
---|---|---|---|---|
System and Communications Protection | SC-12 | Cryptographic Key Establishment and Management | Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password | 1.0.0 |
System and Communications Protection | SC-28 | Protection of Information at Rest | Azure Data Box jobs should enable double encryption for data at rest on the device | 1.0.0 |
System and Communications Protection | SC-28 (1) | Cryptographic Protection | Azure Data Box jobs should enable double encryption for data at rest on the device | 1.0.0 |
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.05.2 Data protection - Cryptographic measures | U.05.2 | Data stored in the cloud service shall be protected to the latest state of the art. | Azure Data Box jobs should enable double encryption for data at rest on the device | 1.0.0 |
U.05.2 Data protection - Cryptographic measures | U.05.2 | Data stored in the cloud service shall be protected to the latest state of the art. | Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password | 1.0.0 |
U.11.3 Cryptoservices - Encrypted | U.11.3 | Sensitive data is always encrypted, with private keys managed by the CSC. | Azure Data Box jobs should enable double encryption for data at rest on the device | 1.0.0 |
U.11.3 Cryptoservices - Encrypted | U.11.3 | Sensitive data is always encrypted, with private keys managed by the CSC. | Azure Data Box jobs should use a customer-managed key to encrypt the device unlock password | 1.0.0 |
Next steps
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.