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 |
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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 |
CIS Microsoft Azure Foundations Benchmark 1.4.0
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 CIS v1.4.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 | 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 | 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 | 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 | 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 | 3.7 | Ensure 'Trusted Microsoft Services' are Enabled for Storage Account Access | Storage accounts should allow access from trusted Microsoft services | 1.0.0 |
| 3 Storage Accounts | 3.9 | Ensure Storage for Critical Data are Encrypted with Customer Managed Keys | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| 5 Logging and Monitoring | 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 | 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 |
CIS Microsoft Azure Foundations Benchmark 2.0.0
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 CIS v2.0.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 | 3.1 | Ensure that 'Secure transfer required' is set to 'Enabled' | Secure transfer to storage accounts should be enabled | 2.0.0 |
| 3 | 3.10 | Ensure Private Endpoints are used to access Storage Accounts | Storage accounts should use private link | 2.0.0 |
| 3 | 3.12 | Ensure Storage for Critical Data are Encrypted with Customer Managed Keys | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| 3 | 3.15 | Ensure the "Minimum TLS version" for storage accounts is set to "Version 1.2" | Storage accounts should have the specified minimum TLS version | 1.0.0 |
| 3 | 3.2 | Ensure that ‘Enable Infrastructure Encryption' for Each Storage Account in Azure Storage is Set to ‘enabled' | Storage accounts should have infrastructure encryption | 1.0.0 |
| 3 | 3.7 | Ensure that 'Public access level' is disabled for storage accounts with blob containers | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| 3 | 3.8 | Ensure Default Network Access Rule for Storage Accounts is Set to Deny | Storage accounts should restrict network access | 1.1.1 |
| 3 | 3.8 | 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 | 3.9 | Ensure 'Allow Azure services on the trusted services list to access this storage account' is Enabled for Storage Account Access | Storage accounts should allow access from trusted Microsoft services | 1.0.0 |
| 5.1 | 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.1 | 5.1.4 | Ensure the storage account containing the container with activity logs is encrypted with Customer Managed 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 Defender for Storage (Classic) on storage accounts | 1.0.1 |
| 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 |
Microsoft Cloud for Sovereignty Baseline Confidential Policies
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 MCfS Sovereignty Baseline Confidential Policies. For more information about this compliance standard, see Microsoft Cloud for Sovereignty Policy portfolio.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| SO.3 - Customer-Managed Keys | SO.3 | Azure products must be configured to use Customer-Managed Keys when possible. | Queue Storage should use customer-managed key for encryption | 1.0.0 |
| SO.3 - Customer-Managed Keys | SO.3 | Azure products must be configured to use Customer-Managed Keys when possible. | Storage account encryption scopes should use customer-managed keys to encrypt data at rest | 1.0.0 |
| SO.3 - Customer-Managed Keys | SO.3 | Azure products must be configured to use Customer-Managed Keys when possible. | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| SO.3 - Customer-Managed Keys | SO.3 | Azure products must be configured to use Customer-Managed Keys when possible. | Table Storage should use customer-managed key for encryption | 1.0.0 |
Microsoft cloud security benchmark
The Microsoft cloud security benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Microsoft cloud 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 - Microsoft cloud 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 |
| Identity Management | IM-1 | Use centralized identity and authentication system | Storage accounts should prevent shared key access | 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 |
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) |
|---|---|---|---|---|
| Access Control | 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Access Control | 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). | Storage accounts should restrict network access | 1.1.1 |
| Access Control | 3.1.1 | Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). | Storage accounts should use private link | 2.0.0 |
| Access Control | 3.1.12 | Monitor and control remote access sessions. | Storage accounts should restrict network access | 1.1.1 |
| Access Control | 3.1.12 | Monitor and control remote access sessions. | Storage accounts should use private link | 2.0.0 |
| Access Control | 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. | Storage accounts should restrict network access | 1.1.1 |
| Access Control | 3.1.13 | Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. | Storage accounts should use private link | 2.0.0 |
| Access Control | 3.1.14 | Route remote access via managed access control points. | Storage accounts should restrict network access | 1.1.1 |
| Access Control | 3.1.14 | Route remote access via managed access control points. | Storage accounts should use private link | 2.0.0 |
| Access Control | 3.1.2 | Limit system access to the types of transactions and functions that authorized users are permitted to execute. | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Access Control | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| Access Control | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | Storage accounts should restrict network access | 1.1.1 |
| Access Control | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| Access Control | 3.1.3 | Control the flow of CUI in accordance with approved authorizations. | Storage accounts should use private link | 2.0.0 |
| System and Communications Protection | 3.13.1 | 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 | 3.13.1 | 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 | 3.13.1 | 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 using virtual network rules | 1.0.1 |
| System and Communications Protection | 3.13.1 | 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 use private link | 2.0.0 |
| System and Communications Protection | 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Storage account encryption scopes should use customer-managed keys to encrypt data at rest | 1.0.0 |
| System and Communications Protection | 3.13.10 | Establish and manage cryptographic keys for cryptography employed in organizational systems. | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| System and Communications Protection | 3.13.16 | Protect the confidentiality of CUI at rest. | Storage accounts should have infrastructure encryption | 1.0.0 |
| System and Communications Protection | 3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| System and Communications Protection | 3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | Storage accounts should restrict network access | 1.1.1 |
| System and Communications Protection | 3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| System and Communications Protection | 3.13.2 | Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. | Storage accounts should use private link | 2.0.0 |
| System and Communications Protection | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| System and Communications Protection | 3.13.5 | 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 | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| System and Communications Protection | 3.13.5 | Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. | Storage accounts should use private link | 2.0.0 |
| System and Communications Protection | 3.13.6 | 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 | 3.13.6 | 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 | 3.13.6 | 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 using virtual network rules | 1.0.1 |
| System and Communications Protection | 3.13.8 | 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 |
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-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 |
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 |
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) |
|---|---|---|---|---|
| B.09.1 Privacy and protection of personal data - Security aspects and stages | B.09.1 | Availability, integrity and confidentiality measures have been taken. | Secure transfer to storage accounts should be enabled | 2.0.0 |
| U.05.1 Data protection - Cryptographic measures | U.05.1 | Data transport is secured with cryptography where key management is carried out by the CSC itself if possible. | Secure transfer to storage accounts should be enabled | 2.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. | Storage account encryption scopes should use customer-managed keys to encrypt data at rest | 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. | Storage accounts should have infrastructure encryption | 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. | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| U.07.1 Data separation - Isolated | U.07.1 | Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner. | [Preview]: Storage account public access should be disallowed | 3.1.0-preview |
| U.07.1 Data separation - Isolated | U.07.1 | Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner. | Storage accounts should restrict network access | 1.1.1 |
| U.07.1 Data separation - Isolated | U.07.1 | Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner. | Storage accounts should restrict network access using virtual network rules | 1.0.1 |
| U.07.1 Data separation - Isolated | U.07.1 | Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner. | Storage accounts should use private link | 2.0.0 |
| U.07.3 Data separation - Management features | U.07.3 | U.07.3 - The privileges to view or modify CSC data and/or encryption keys are granted in a controlled manner and use is logged. | Storage accounts should prevent shared key access | 2.0.0 |
| U.10.2 Access to IT services and data - Users | U.10.2 | Under the responsibility of the CSP, access is granted to administrators. | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| U.10.2 Access to IT services and data - Users | U.10.2 | Under the responsibility of the CSP, access is granted to administrators. | Storage accounts should prevent shared key access | 2.0.0 |
| U.10.3 Access to IT services and data - Users | U.10.3 | Only users with authenticated equipment can access IT services and data. | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| U.10.3 Access to IT services and data - Users | U.10.3 | Only users with authenticated equipment can access IT services and data. | Storage accounts should prevent shared key access | 2.0.0 |
| U.10.5 Access to IT services and data - Competent | U.10.5 | Access to IT services and data is limited by technical measures and has been implemented. | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| U.10.5 Access to IT services and data - Competent | U.10.5 | Access to IT services and data is limited by technical measures and has been implemented. | Storage accounts should prevent shared key access | 2.0.0 |
| U.11.1 Cryptoservices - Policy | U.11.1 | In the cryptography policy, at least the subjects in accordance with BIO have been elaborated. | Secure transfer to storage accounts should be enabled | 2.0.0 |
| U.11.2 Cryptoservices - Cryptographic measures | U.11.2 | In case of PKIoverheid certificates use PKIoverheid requirements for key management. In other situations use ISO11770. | Secure transfer to storage accounts should be enabled | 2.0.0 |
| U.11.3 Cryptoservices - Encrypted | U.11.3 | Sensitive data is always encrypted, with private keys managed by the CSC. | Storage account encryption scopes should use customer-managed keys to encrypt data at rest | 1.0.0 |
| U.11.3 Cryptoservices - Encrypted | U.11.3 | Sensitive data is always encrypted, with private keys managed by the CSC. | Storage accounts should have infrastructure encryption | 1.0.0 |
| U.11.3 Cryptoservices - Encrypted | U.11.3 | Sensitive data is always encrypted, with private keys managed by the CSC. | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| U.12.1 Interfaces - Network connections | U.12.1 | In connection points with external or untrusted zones, measures are taken against attacks. | Storage accounts should restrict network access | 1.1.1 |
| U.12.2 Interfaces - Network connections | U.12.2 | Network components are such that network connections between trusted and untrusted networks are limited. | Storage accounts should restrict network access | 1.1.1 |
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 | 1.3.2 | PCI DSS requirement 1.3.2 | Storage accounts should restrict network access | 1.1.1 |
| Requirement 1 | 1.3.4 | PCI DSS requirement 1.3.4 | Storage accounts should restrict network access | 1.1.1 |
| Requirement 10 | 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 | 3.4 | PCI DSS requirement 3.4 | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Requirement 4 | 4.1 | PCI DSS requirement 4.1 | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Requirement 6 | 6.5.3 | PCI DSS requirement 6.5.3 | Secure transfer to storage accounts should be enabled | 2.0.0 |
PCI DSS v4.0
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 DSS v4.0. For more information about this compliance standard, see PCI DSS v4.0.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Requirement 01: Install and Maintain Network Security Controls | 1.3.2 | Network access to and from the cardholder data environment is restricted | Storage accounts should restrict network access | 1.1.1 |
| Requirement 01: Install and Maintain Network Security Controls | 1.4.2 | Network connections between trusted and untrusted networks are controlled | Storage accounts should restrict network access | 1.1.1 |
| Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | 10.2.2 | Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Requirement 10: Log and Monitor All Access to System Components and Cardholder Data | 10.3.3 | Audit logs are protected from destruction and unauthorized modifications | Storage accounts should be migrated to new Azure Resource Manager resources | 1.0.0 |
| Requirement 03: Protect Stored Account Data | 3.5.1 | Primary account number (PAN) is secured wherever it is stored | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Requirement 06: Develop and Maintain Secure Systems and Software | 6.2.4 | Bespoke and custom software are developed securely | 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 | 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 | 3.1.h | Public Key Infrastructure (PKI)-3.1 | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Information and Cyber Security | 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 | 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 | 3.1.h | Public Key Infrastructure (PKI)-3.1 | Storage accounts should have infrastructure encryption | 1.0.0 |
| Information and Cyber Security | 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 | |
| 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 | |
| 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 | |
| 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 |
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.
SWIFT CSP-CSCF v2021
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 SWIFT CSP-CSCF v2021. For more information about this compliance standard, see SWIFT CSP CSCF v2021.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| SWIFT Environment Protection | 1.1 | SWIFT Environment Protection | Storage accounts should restrict network access | 1.1.1 |
| SWIFT Environment Protection | 1.1 | SWIFT Environment Protection | Storage Accounts should use a virtual network service endpoint | 1.0.0 |
| Reduce Attack Surface and Vulnerabilities | 2.5A | External Transmission Data Protection | Geo-redundant storage should be enabled for Storage Accounts | 1.0.0 |
| Reduce Attack Surface and Vulnerabilities | 2.5A | External Transmission Data Protection | Secure transfer to storage accounts should be enabled | 2.0.0 |
SWIFT CSP-CSCF v2022
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 SWIFT CSP-CSCF v2022. For more information about this compliance standard, see SWIFT CSP CSCF v2022.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | 1.1 | Ensure the protection of the user's local SWIFT infrastructure from potentially compromised elements of the general IT environment and external environment. | Storage accounts should restrict network access | 1.1.1 |
| 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | 1.1 | Ensure the protection of the user's local SWIFT infrastructure from potentially compromised elements of the general IT environment and external environment. | Storage Accounts should use a virtual network service endpoint | 1.0.0 |
| 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | 1.5A | Ensure the protection of the customer's connectivity infrastructure from external environment and potentially compromised elements of the general IT environment. | Storage accounts should restrict network access | 1.1.1 |
| 1. Restrict Internet Access & Protect Critical Systems from General IT Environment | 1.5A | Ensure the protection of the customer's connectivity infrastructure from external environment and potentially compromised elements of the general IT environment. | Storage Accounts should use a virtual network service endpoint | 1.0.0 |
| 2. Reduce Attack Surface and Vulnerabilities | 2.5A | External Transmission Data Protection | Geo-redundant storage should be enabled for Storage Accounts | 1.0.0 |
| 2. Reduce Attack Surface and Vulnerabilities | 2.5A | External Transmission Data Protection | Secure transfer to storage accounts should be enabled | 2.0.0 |
| 6. Detect Anomalous Activity to Systems or Transaction Records | 6.4 | Record security events and detect anomalous actions and operations within the local SWIFT environment. | Storage account containing the container with activity logs must be encrypted with BYOK | 1.0.0 |
System and Organization Controls (SOC) 2
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 System and Organization Controls (SOC) 2. For more information about this compliance standard, see System and Organization Controls (SOC) 2.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Logical and Physical Access Controls | CC6.1 | Logical access security software, infrastructure, and architectures | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Logical and Physical Access Controls | CC6.1 | Logical access security software, infrastructure, and architectures | Storage account containing the container with activity logs must be encrypted with BYOK | 1.0.0 |
| Logical and Physical Access Controls | CC6.1 | Logical access security software, infrastructure, and architectures | Storage accounts should use customer-managed key for encryption | 1.0.3 |
| Logical and Physical Access Controls | CC6.6 | Security measures against threats outside system boundaries | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Logical and Physical Access Controls | CC6.7 | Restrict the movement of information to authorized users | Secure transfer to storage accounts should be enabled | 2.0.0 |
| Logical and Physical Access Controls | CC6.8 | Prevent or detect against unauthorized or malicious software | Storage accounts should allow access from trusted Microsoft services | 1.0.0 |
| Change Management | CC8.1 | Changes to infrastructure, data, and software | Storage accounts should allow access from trusted Microsoft services | 1.0.0 |
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
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for