Skip to main content

🛡️ Azure Storage Account Trusted Azure Services are not enabled as networking exceptions🟢

  • Contextual name: 🛡️ Trusted Azure Services are not enabled as networking exceptions🟢
  • ID: /ce/ca/azure/storage/trusted-azure-services-exceptions
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: SECURITY

Stats​

not available

Logic​

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-3179d53c1

Description​

Open File

Description​

NOTE: This recommendation assumes that the Public network access parameter is set to Enabled from selected virtual networks and IP addresses. Ensure the prerequisite recommendation has been implemented before proceeding:

  • Ensure Default Network Access Rule for Storage Accounts is Set to Deny

Some Azure services that interact with storage accounts operate from networks that can't be granted access through network rules. To help this type of service work as intended, allow the set of trusted Azure services to bypass the network rules. These services will then use strong authentication to access the storage account. If the Allow Azure services on the trusted services list to access this storage account exception is enabled, the following services are granted access to the storage account:

  • Azure Backup,
  • Azure Data Box,
  • Azure DevTest Labs,
  • Azure Event Grid,
  • Azure Event Hubs,
  • Azure File Sync,
  • Azure HDInsight,
  • Azure Import/Export,
  • Azure Monitor,
  • Azure Networking Services, and
  • Azure Site Recovery (when registered in the subscription).

... see more

Remediation​

Open File

Remediation​

From Azure Portal​

  1. Go to Storage Accounts.
  2. For each storage account, under Security + networking, click Networking.
  3. Click on the Firewalls and virtual networks heading.
  4. Under Exceptions, check the box next to Allow Azure services on the trusted services list to access this storage account.
  5. Click Save.

From Azure CLI​

Use the following command to update bypass to Azure services:

az storage account update \
    --name {{storage-account-name}} \
    --resource-group {{resource-group-name}} \
    --bypass AzureServices

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS Azure v1.1.0 → 💼 3.8 Ensure 'Trusted Microsoft Services' is enabled for Storage Account access11no data
💼 CIS Azure v1.3.0 → 💼 3.7 Ensure 'Trusted Microsoft Services' is enabled for Storage Account access - Level 2 (Manual)11no data
💼 CIS Azure v1.4.0 → 💼 3.7 Ensure 'Trusted Microsoft Services' are Enabled for Storage Account Access - Level 2 (Automated)11no data
💼 CIS Azure v1.5.0 → 💼 3.9 Ensure 'Allow Azure services on the trusted services list to access this storage account' is Enabled for Storage Account Access - Level 2 (Automated)11no data
💼 CIS Azure v2.0.0 → 💼 3.9 Ensure 'Allow Azure services on the trusted services list to access this storage account' is Enabled for Storage Account Access - Level 2 (Automated)11no data
💼 CIS Azure v2.1.0 → 💼 3.9 Ensure 'Allow Azure services on the trusted services list to access this storage account' is Enabled for Storage Account Access - Level 2 (Automated)11no data
💼 CIS Azure v3.0.0 → 💼 4.8 Ensure 'Allow Azure services on the trusted services list to access this storage account' is Enabled for Storage Account Access (Automated)1no data
💼 CIS Azure v4.0.0 → 💼 10.3.5 Ensure 'Allow Azure services on the trusted services list to access this storage account' is Enabled for Storage Account Access (Automated)1no data
💼 CIS Azure v5.0.0 → 💼 9.3.5 Ensure 'Allow Azure services on the trusted services list to access this storage account' is Enabled for Storage Account Access (Automated)1no data
💼 CIS Azure v6.0.0 → 💼 9.3.5 Ensure 'Allow trusted Microsoft services to access this resource' is Enabled for Storage Account Access (Automated)1no data
💼 Cloudaware Framework → 💼 Network Exposure137no data
💼 FedRAMP High Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)49103no data
💼 FedRAMP High Security Controls → 💼 AC-17(1) Monitoring and Control (M)(H)1no data
💼 FedRAMP Low Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)103no data
💼 FedRAMP Moderate Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)103no data
💼 FedRAMP Moderate Security Controls → 💼 AC-17(1) Monitoring and Control (M)(H)1no data
💼 ISO/IEC 27001:2013 → 💼 A.9.1.2 Access to networks and network services2767no data
💼 ISO/IEC 27001:2022 → 💼 5.10 Acceptable use of information and other associated assets1434no data
💼 ISO/IEC 27001:2022 → 💼 5.15 Access control1738no data
💼 ISO/IEC 27001:2022 → 💼 6.7 Remote working518no data
💼 ISO/IEC 27001:2022 → 💼 8.1 User end point devices1431no data
💼 ISO/IEC 27001:2022 → 💼 8.3 Information access restriction1331no data
💼 ISO/IEC 27001:2022 → 💼 8.4 Access to source code1129no data
💼 NIST CSF v1.1 → 💼 PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties48127no data
💼 NIST CSF v1.1 → 💼 PR.DS-5: Protections against data leaks are implemented89152no data
💼 NIST CSF v1.1 → 💼 PR.PT-3: The principle of least functionality is incorporated by configuring systems to provide only essential capabilities3179no data
💼 NIST CSF v2.0 → 💼 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties199no data
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected248no data
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected219no data
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected249no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-17(1) Remote Access _ Monitoring and Control11no data
💼 SOC 2 → 💼 CC6.1-8 Manages Identification and Authentication2234no data