Azure Policy Regulatory Compliance controls for Azure Storage
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 Storage. 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.
Australian Government ISM PROTECTED
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Australian Government ISM PROTECTED. For more information about this compliance standard, see Australian Government ISM PROTECTED.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Guidelines for Networking - Network design and configuration | 520 | Network access controls - 520 | Storage accounts should restrict network access | 1.1.1 |
| Guidelines for Networking - Network design and configuration | 1182 | Network access controls - 1182 | Storage accounts should restrict network access | 1.1.1 |
| Guidelines for Database Systems - Database servers | 1277 | Communications between database servers and web servers - 1277 | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Guidelines for System Hardening - Authentication hardening | 1546 | Authenticating to systems - 1546 | Storage accounts should restrict network access | 1.1.1 |
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]: Storage account public access should be disallowed | 3.1.0-preview |
| Network Security | NS-2 | Secure cloud services with network controls | Storage accounts should restrict network access | 1.1.1 |
| Network Security | NS-2 | Secure cloud services with network controls | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| Network Security | NS-2 | Secure cloud services with network controls | Storage accounts should use private link | 2.0.0 |
| Data Protection | DP-3 | Encrypt sensitive data in transit | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Data Protection | DP-5 | Use customer-managed key option in data at rest encryption when required | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| Asset Management | AM-2 | Use only approved services | ||
| Storage accounts should be migrated to new Azure Resource Manager resources | 1.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 | Storage accounts should restrict network access | 1.1.1 |
| Network Security | 1.1 | Protect resources using Network Security Groups or Azure Firewall on your Virtual Network | Storage Accounts should use a virtual network service endpoint | 1.0.0 |
| Data Protection | 4.4 | Encrypt all sensitive information in transit | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Inventory and Asset Management | 6.9 | Use only approved Azure services | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
Canada Federal PBMM
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Canada Federal PBMM. For more information about this compliance standard, see Canada Federal PBMM.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | AC-17(1) | Remote Access | Automated Monitoring / Control | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | SC-7 | Boundary Protection | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | SC-8(1) | Transmission Confidentiality and Integrity | Cryptographic or Alternate Physical Protection | Secure transfer to storage accounts should be 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) |
|---|---|---|---|---|
| 3 Storage Accounts | CIS Microsoft Azure Foundations Benchmark recommendation 3.1 | Ensure that 'Secure transfer required' is set to 'Enabled' | Secure transfer to storage accounts should be enabled | 2.0.0 |
| 3 Storage Accounts | CIS Microsoft Azure Foundations Benchmark recommendation 3.6 | Ensure that 'Public access level' is set to Private for blob containers | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| 3 Storage Accounts | CIS Microsoft Azure Foundations Benchmark recommendation 3.7 | Ensure default network access rule for Storage Accounts is set to deny | Storage accounts should restrict network access | 1.1.1 |
| 3 Storage Accounts | CIS Microsoft Azure Foundations Benchmark recommendation 3.8 | Ensure 'Trusted Microsoft Services' is enabled for Storage Account access | Storage accounts should allow access from trusted Microsoft services | 1.0.0 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.5 | Ensure the storage container storing the activity logs is not publicly accessible | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.6 | Ensure the storage account containing the container with activity logs is encrypted with BYOK (Use Your Own Key) | Storage account containing the container with activity logs must be encrypted with BYOK | 1.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) |
|---|---|---|---|---|
| 3 Storage Accounts | CIS Microsoft Azure Foundations Benchmark recommendation 3.1 | Ensure that 'Secure transfer required' is set to 'Enabled' | Secure transfer to storage accounts should be enabled | 2.0.0 |
| 3 Storage Accounts | CIS Microsoft Azure Foundations Benchmark recommendation 3.5 | Ensure that 'Public access level' is set to Private for blob containers | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| 3 Storage Accounts | CIS Microsoft Azure Foundations Benchmark recommendation 3.6 | Ensure default network access rule for Storage Accounts is set to deny | Storage accounts should restrict network access | 1.1.1 |
| 3 Storage Accounts | CIS Microsoft Azure Foundations Benchmark recommendation 3.6 | Ensure default network access rule for Storage Accounts is set to deny | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| 3 Storage Accounts | CIS Microsoft Azure Foundations Benchmark recommendation 3.7 | Ensure 'Trusted Microsoft Services' is enabled for Storage Account access | Storage accounts should allow access from trusted Microsoft services | 1.0.0 |
| 3 Storage Accounts | CIS Microsoft Azure Foundations Benchmark recommendation 3.9 | Ensure storage for critical data are encrypted with Customer Managed Key | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.3 | Ensure the storage container storing the activity logs is not publicly accessible | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| 5 Logging and Monitoring | CIS Microsoft Azure Foundations Benchmark recommendation 5.1.4 | Ensure the storage account containing the container with activity logs is encrypted with BYOK (Use Your Own Key) | Storage account containing the container with activity logs must be encrypted with BYOK | 1.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). | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| 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). | Storage accounts should allow access from trusted Microsoft services | 1.0.0 |
| 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). | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC.1.002 | Limit information system access to the types of transactions and functions that authorized users are permitted to execute. | [Preview]: Storage account public access should be disallowed | 3.1.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. | Secure transfer to storage accounts should be enabled | 2.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. | Storage accounts should allow access from trusted Microsoft services | 1.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. | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC.2.013 | Monitor and control remote access sessions. | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC.2.016 | Control the flow of CUI in accordance with approved authorizations. | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| Access Control | AC.2.016 | Control the flow of CUI in accordance with approved authorizations. | Storage accounts should restrict network access | 1.1.1 |
| Configuration Management | CM.3.068 | Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| Configuration Management | CM.3.068 | Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. | Storage accounts should restrict network access | 1.1.1 |
| Incident Response | IR.2.093 | Detect and report events. | Deploy Advanced Threat Protection on storage accounts | 1.0.0 |
| System and Communications Protection | SC.1.175 | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| System and Communications Protection | SC.1.175 | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | Secure transfer to storage accounts should be enabled | 2.0.0 |
| System and Communications Protection | SC.1.175 | Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | SC.1.176 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Storage accounts should have infrastructure encryption | 1.0.0 |
| System and Communications Protection | SC.3.177 | Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| 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). | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| 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). | Storage accounts should allow access from trusted Microsoft services | 1.0.0 |
| 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). | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | SC.3.185 | Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. | Secure transfer to storage accounts should be enabled | 2.0.0 |
| System and Communications Protection | SC.3.185 | Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | SC.3.191 | Protect the confidentiality of CUI at rest. | Storage accounts should have infrastructure encryption | 1.0.0 |
| System and Communications Protection | SC.3.191 | Protect the confidentiality of CUI at rest. | Storage accounts should restrict network access | 1.1.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-3 | Access Enforcement | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Access Control | AC-4 | Information Flow Enforcement | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| Access Control | AC-4 | Information Flow Enforcement | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC-4 | Information Flow Enforcement | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| Access Control | AC-4 | Information Flow Enforcement | Storage accounts should use private link | 2.0.0 |
| Access Control | AC-17 | Remote Access | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC-17 | Remote Access | Storage accounts should use private link | 2.0.0 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Storage accounts should use private link | 2.0.0 |
| Contingency Planning | CP-6 | Alternate Storage Site | Geo-redundant storage should be enabled for Storage Accounts | 1.0.0 |
| Contingency Planning | CP-6 (1) | Separation From Primary Site | Geo-redundant storage should be enabled for Storage Accounts | 1.0.0 |
| System And Communications Protection | SC-7 | Boundary Protection | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| System And Communications Protection | SC-7 | Boundary Protection | Storage accounts should restrict network access | 1.1.1 |
| System And Communications Protection | SC-7 | Boundary Protection | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| System And Communications Protection | SC-7 | Boundary Protection | Storage accounts should use private link | 2.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| System And Communications Protection | SC-7 (3) | Access Points | Storage accounts should restrict network access | 1.1.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Storage accounts should use private link | 2.0.0 |
| System And Communications Protection | SC-8 | Transmission Confidentiality And Integrity | Secure transfer to storage accounts should be enabled | 2.0.0 |
| System And Communications Protection | SC-8 (1) | Cryptographic Or Alternate Physical Protection | Secure transfer to storage accounts should be enabled | 2.0.0 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Storage account encryption scopes should use customer-managed keys to encrypt data at rest | 1.0.0 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| System And Communications Protection | SC-28 | Protection Of Information At Rest | Storage accounts should have infrastructure encryption | 1.0.0 |
| System And Communications Protection | SC-28 (1) | Cryptographic Protection | Storage accounts should have infrastructure encryption | 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) |
|---|---|---|---|---|
| Access Control | AC-3 | Access Enforcement | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Access Control | AC-4 | Information Flow Enforcement | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| Access Control | AC-4 | Information Flow Enforcement | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC-4 | Information Flow Enforcement | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| Access Control | AC-4 | Information Flow Enforcement | Storage accounts should use private link | 2.0.0 |
| Access Control | AC-17 | Remote Access | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC-17 | Remote Access | Storage accounts should use private link | 2.0.0 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC-17 (1) | Automated Monitoring / Control | Storage accounts should use private link | 2.0.0 |
| Contingency Planning | CP-6 | Alternate Storage Site | Geo-redundant storage should be enabled for Storage Accounts | 1.0.0 |
| Contingency Planning | CP-6 (1) | Separation From Primary Site | Geo-redundant storage should be enabled for Storage Accounts | 1.0.0 |
| System And Communications Protection | SC-7 | Boundary Protection | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| System And Communications Protection | SC-7 | Boundary Protection | Storage accounts should restrict network access | 1.1.1 |
| System And Communications Protection | SC-7 | Boundary Protection | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| System And Communications Protection | SC-7 | Boundary Protection | Storage accounts should use private link | 2.0.0 |
| System And Communications Protection | SC-7 (3) | Access Points | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| System And Communications Protection | SC-7 (3) | Access Points | Storage accounts should restrict network access | 1.1.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| System And Communications Protection | SC-7 (3) | Access Points | Storage accounts should use private link | 2.0.0 |
| System And Communications Protection | SC-8 | Transmission Confidentiality And Integrity | Secure transfer to storage accounts should be enabled | 2.0.0 |
| System And Communications Protection | SC-8 (1) | Cryptographic Or Alternate Physical Protection | Secure transfer to storage accounts should be enabled | 2.0.0 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Storage account encryption scopes should use customer-managed keys to encrypt data at rest | 1.0.0 |
| System And Communications Protection | SC-12 | Cryptographic Key Establishment And Management | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| System And Communications Protection | SC-28 | Protection Of Information At Rest | Storage accounts should have infrastructure encryption | 1.0.0 |
| System And Communications Protection | SC-28 (1) | Cryptographic Protection | Storage accounts should have infrastructure encryption | 1.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) |
|---|---|---|---|---|
| Identification of Risks Related to External Parties | 1401.05i1Organizational.1239 - 05.i | Access to the organizations information and systems by external parties is not permitted until due diligence has been conducted, the appropriate controls have been implemented, and a contract/agreement reflecting the security requirements is signed acknowledging they understand and accept their obligations. | Secure transfer to storage accounts should be enabled | 2.0.0 |
| 08 Network Protection | 0805.01m1Organizational.12-01.m | 0805.01m1Organizational.12-01.m 01.04 Network Access Control | Storage Accounts 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 | Storage Accounts should use a virtual network service endpoint | 1.0.0 |
| 08 Network Protection | 0809.01n2Organizational.1234-01.n | 0809.01n2Organizational.1234-01.n 01.04 Network Access Control | Secure transfer to storage accounts should be enabled | 2.0.0 |
| 08 Network Protection | 0810.01n2Organizational.5-01.n | 0810.01n2Organizational.5-01.n 01.04 Network Access Control | Secure transfer to storage accounts should be enabled | 2.0.0 |
| 08 Network Protection | 0811.01n2Organizational.6-01.n | 0811.01n2Organizational.6-01.n 01.04 Network Access Control | Secure transfer to storage accounts should be enabled | 2.0.0 |
| 08 Network Protection | 0812.01n2Organizational.8-01.n | 0812.01n2Organizational.8-01.n 01.04 Network Access Control | Secure transfer to storage accounts should be enabled | 2.0.0 |
| 08 Network Protection | 0814.01n1Organizational.12-01.n | 0814.01n1Organizational.12-01.n 01.04 Network Access Control | Secure transfer to storage accounts should be enabled | 2.0.0 |
| 08 Network Protection | 0866.09m3Organizational.1516-09.m | 0866.09m3Organizational.1516-09.m 09.06 Network Security Management | Storage accounts should restrict network access | 1.1.1 |
| 08 Network Protection | 0894.01m2Organizational.7-01.m | 0894.01m2Organizational.7-01.m 01.04 Network Access Control | Storage Accounts should use a virtual network service endpoint | 1.0.0 |
| Network Controls | 0867.09m3Organizational.17 - 09.m | Wireless access points are placed in secure areas and shut down when not in use (e.g. nights, weekends). | Storage Accounts should use a virtual network service endpoint | 1.0.0 |
| 09 Transmission Protection | 0943.09y1Organizational.1-09.y | 0943.09y1Organizational.1-09.y 09.09 Electronic Commerce Services | Secure transfer to storage accounts should be enabled | 2.0.0 |
IRS 1075 September 2016
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - IRS 1075 September 2016. For more information about this compliance standard, see IRS 1075 September 2016.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control | 9.3.1.12 | Remote Access (AC-17) | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | 9.3.16.5 | Boundary Protection (SC-7) | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | 9.3.16.6 | Transmission Confidentiality and Integrity (SC-8) | Secure transfer to storage accounts should be enabled | 2.0.0 |
ISO 27001:2013
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - ISO 27001:2013. For more information about this compliance standard, see ISO 27001:2013.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Cryptography | 10.1.1 | Policy on the use of cryptographic controls | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Communications Security | 13.1.1 | Network controls | Storage accounts should restrict network access | 1.1.1 |
| Communications Security | 13.2.1 | Information transfer policies and procedures | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Access Control | 9.1.2 | Access to networks and network services | Storage accounts should be migrated to new Azure Resource Manager resources | 1.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) |
|---|---|---|---|---|
| Physical Security | PS-4 | 8.3.5 Network infrastructure in unsecure areas | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Infrastructure | INF-9 | 10.8.35 Security Architecture | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| Infrastructure | INF-9 | 10.8.35 Security Architecture | Storage accounts should use private link | 2.0.0 |
| Cryptography | CR-3 | 17.1.46 Reducing storage and physical transfer requirements | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| Gateway security | GS-2 | 19.1.11 Using Gateways | Storage account keys should not be expired | 3.0.0 |
| Gateway security | GS-3 | 19.1.12 Configuration of Gateways | Storage accounts should restrict network access | 1.1.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-3 | Access Enforcement | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Access Control | AC-4 | Information Flow Enforcement | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| Access Control | AC-4 | Information Flow Enforcement | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC-4 | Information Flow Enforcement | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| Access Control | AC-4 | Information Flow Enforcement | Storage accounts should use private link | 2.0.0 |
| Access Control | AC-17 | Remote Access | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC-17 | Remote Access | Storage accounts should use private link | 2.0.0 |
| Access Control | AC-17 (1) | Monitoring and Control | Storage accounts should restrict network access | 1.1.1 |
| Access Control | AC-17 (1) | Monitoring and Control | Storage accounts should use private link | 2.0.0 |
| Contingency Planning | CP-6 | Alternate Storage Site | Geo-redundant storage should be enabled for Storage Accounts | 1.0.0 |
| Contingency Planning | CP-6 (1) | Separation from Primary Site | Geo-redundant storage should be enabled for Storage Accounts | 1.0.0 |
| System and Communications Protection | SC-7 | Boundary Protection | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| System and Communications Protection | SC-7 | Boundary Protection | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | SC-7 | Boundary Protection | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| System and Communications Protection | SC-7 | Boundary Protection | Storage accounts should use private link | 2.0.0 |
| System and Communications Protection | SC-7 (3) | Access Points | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| System and Communications Protection | SC-7 (3) | Access Points | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | SC-7 (3) | Access Points | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| System and Communications Protection | SC-7 (3) | Access Points | Storage accounts should use private link | 2.0.0 |
| System and Communications Protection | SC-8 | Transmission Confidentiality and Integrity | Secure transfer to storage accounts should be enabled | 2.0.0 |
| System and Communications Protection | SC-8 (1) | Cryptographic Protection | Secure transfer to storage accounts should be enabled | 2.0.0 |
| System and Communications Protection | SC-12 | Cryptographic Key Establishment and Management | Storage account encryption scopes should use customer-managed keys to encrypt data at rest | 1.0.0 |
| System and Communications Protection | SC-12 | Cryptographic Key Establishment and Management | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| System and Communications Protection | SC-28 | Protection of Information at Rest | Storage accounts should have infrastructure encryption | 1.0.0 |
| System and Communications Protection | SC-28 (1) | Cryptographic Protection | Storage accounts should have infrastructure encryption | 1.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-19 | 16.6.12 Event log protection | Storage account containing the container with activity logs must be encrypted with BYOK | 1.0.0 |
| Cryptography | NZISM Security Benchmark CR-3 | 17.1.53 Reducing storage and physical transfer requirements | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| Gateway security | NZISM Security Benchmark GS-2 | 19.1.11 Using Gateways | Storage account keys should not be expired | 3.0.0 |
| Gateway security | NZISM Security Benchmark GS-3 | 19.1.12 Configuration of Gateways | Storage accounts should restrict network access | 1.1.1 |
| Infrastructure | NZISM Security Benchmark INF-9 | 10.8.35 Security Architecture | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| Infrastructure | NZISM Security Benchmark INF-9 | 10.8.35 Security Architecture | Storage accounts should use private link | 2.0.0 |
| Physical Security | NZISM Security Benchmark PS-4 | 8.3.5 Network infrastructure in unsecure areas | Secure transfer to storage accounts should be enabled | 2.0.0 |
PCI DSS 3.2.1
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see PCI DSS 3.2.1. For more information about this compliance standard, see PCI DSS 3.2.1.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Requirement 1 | PCI DSS v3.2.1 1.3.2 | PCI DSS requirement 1.3.2 | Storage accounts should restrict network access | 1.1.1 |
| Requirement 1 | PCI DSS v3.2.1 1.3.4 | PCI DSS requirement 1.3.4 | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Requirement 1 | PCI DSS v3.2.1 1.3.4 | PCI DSS requirement 1.3.4 | Storage accounts should restrict network access | 1.1.1 |
| Requirement 10 | PCI DSS v3.2.1 10.5.4 | PCI DSS requirement 10.5.4 | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Requirement 3 | PCI DSS v3.2.1 3.4 | PCI DSS requirement 3.4 | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Requirement 4 | PCI DSS v3.2.1 4.1 | PCI DSS requirement 4.1 | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Requirement 6 | PCI DSS v3.2.1 6.5.3 | PCI DSS requirement 6.5.3 | Secure transfer to storage accounts should be enabled | 2.0.0 |
PCI v3.2.1:2018
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 PCI v3.2.1:2018. For more information about this compliance standard, see PCI v3.2.1 2018.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Requirement 1 | PCI DSS v3.2.1 1.3.2 | PCI DSS requirement 1.3.2 | Storage accounts should restrict network access | 1.1.1 |
| Requirement 1 | PCI DSS v3.2.1 1.3.4 | PCI DSS requirement 1.3.4 | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Requirement 1 | PCI DSS v3.2.1 1.3.4 | PCI DSS requirement 1.3.4 | Storage accounts should restrict network access | 1.1.1 |
| Requirement 10 | PCI DSS v3.2.1 10.5.4 | PCI DSS requirement 10.5.4 | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Requirement 3 | PCI DSS v3.2.1 3.4 | PCI DSS requirement 3.4 | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Requirement 4 | PCI DSS v3.2.1 4.1 | PCI DSS requirement 4.1 | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Requirement 6 | PCI DSS v3.2.1 6.5.3 | PCI DSS requirement 6.5.3 | Secure transfer to storage accounts should be enabled | 2.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.g | Trails-3.1 | Storage account containing the container with activity logs must be encrypted with BYOK | 1.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | Storage account encryption scopes should use customer-managed keys to encrypt data at rest | 1.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | Storage account encryption scopes should use double encryption for data at rest | 1.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | Storage accounts should have infrastructure encryption | 1.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.h | Public Key Infrastructure (PKI)-3.1 | Storage accounts should use customer-managed key for encryption | 1.0.3 |
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).
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | [Preview]: Storage account public access should be disallowed | 3.1.0-preview | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | [Preview]: Storage account public access should be disallowed | 3.1.0-preview | |
| Anti-Phishing | Anti-Phishing-14.1 | [Preview]: Storage account public access should be disallowed | 3.1.0-preview | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | Secure transfer to storage accounts should be enabled | 2.0.0 | |
| Secure Mail And Messaging Systems | Secure Mail And Messaging Systems-10.2 | Secure transfer to storage accounts should be enabled | 2.0.0 | |
| Secure Mail And Messaging Systems | Secure Mail And Messaging Systems-10.1 | Secure transfer to storage accounts should be enabled | 2.0.0 | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.1 | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.2 | Storage accounts should disable public network access | 1.0.1 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.2 | Storage accounts should disable public network access | 1.0.1 | |
| Anti-Phishing | Anti-Phishing-14.1 | Storage accounts should restrict network access | 1.1.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Storage accounts should restrict network access | 1.1.1 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.1 | Storage accounts should restrict network access | 1.1.1 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.1 | Storage accounts should restrict network access | 1.1.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Storage accounts should restrict network access | 1.1.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Storage accounts should restrict network access using virtual network rules | 1.0.1 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.2 | Storage accounts should restrict network access using virtual network rules | 1.0.1 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.2 | Storage accounts should restrict network access using virtual network rules | 1.0.1 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Storage accounts should restrict network access using virtual network rules | 1.0.1 | |
| Anti-Phishing | Anti-Phishing-14.1 | Storage accounts should restrict network access using virtual network rules | 1.0.1 | |
| Metrics | Metrics-21.1 | Storage accounts should use customer-managed key for encryption | 1.0.3 | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | Storage accounts should use customer-managed key for encryption | 1.0.3 | |
| Metrics | Metrics-21.1 | Storage accounts should use customer-managed key for encryption | 1.0.3 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Storage accounts should use private link | 2.0.0 | |
| Anti-Phishing | Anti-Phishing-14.1 | Storage accounts should use private link | 2.0.0 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Storage accounts should use private link | 2.0.0 |
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.
UK OFFICIAL and UK NHS
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - UK OFFICIAL and UK NHS. For more information about this compliance standard, see UK OFFICIAL.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Data in transit protection | 1 | Data in transit protection | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Identity and authentication | 10 | Identity and authentication | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| External interface protection | 11 | External interface protection | Storage accounts should restrict network access | 1.1.1 |
| Operational security | 5.3 | Protective Monitoring | Storage accounts should restrict network access | 1.1.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