🛡️ Azure Databricks Workspace Allow Public Network Access is not disabled🟢

• Contextual name: 🛡️ Databricks Workspace Allow Public Network Access is not disabled🟢
• ID: /ce/ca/azure/databricks/public-network-access
• Tags:
  • 🟢 Policy with categories
  • 🟢 Policy with type
  • 🟢 Production policy
• Policy Type: COMPLIANCE_POLICY
• Policy Categories: SECURITY

Stats

not available

Logic

• 🧠 prod.logic.yaml🟢
  • 📗 Azure Databricks Workspace
  • 🔌 Azure Databricks Workspace - object.extracts.yaml
  • 🧪 test-data.json

Similar Policies

• Internal: dec-x-78146505

Similar Internal Rules

Rule	Policies	Flags
✉️ dec-x-78146505	1

Description

Open File

Description

Disable public network access to prevent exposure to the internet and reduce the risk of unauthorized access. Use private endpoints to securely manage access within trusted networks.

Rationale

Disabling public network access improves security by ensuring that Azure Databricks workspaces are not exposed on the public internet.

Impact

Note: Before disabling public network access, it is strongly recommended that, for each workspace, either:

• virtual network integration is completed as described in "Ensure that Azure Databricks is deployed in a customer-managed virtual network (VNet)"

OR

• private endpoints or links are set up as described in "Ensure private endpoints are used to access Azure Databricks workspaces."

Disabling public network access restricts access to the service. This enhances security but requires the configuration of a virtual network and/or private endpoints for any services or users needing access within trusted networks.

Before public network access can be disabled, Azure Databricks workspaces must be deployed in a customer-managed virtual network (VNet injection). Refer to the recommendation Ensure that Azure Databricks is deployed in a customer-managed virtual network (VNet), and ensure requiredNsgRules is set to a value other than AllRules.

... see more

Remediation

Open File

Remediation

From Azure Portal

1. Go to Azure Databricks.
2. Click the name of a workspace.
3. Under Settings, click Networking.
4. Under Network access, next to Allow Public Network Access, click the radio button next to Disabled.
5. Click Save.
6. Repeat steps 1-5 for each workspace requiring remediation.

From Azure CLI

For each workspace requiring remediation, run the following command to set publicNetworkAccess to Disabled:

az databricks workspace update \
    --resource-group {{resource-group-name}} \
    --name {{workspace-name}} \
    --public-network-access Disabled

From PowerShell

For each workspace requiring remediation, run the following command to set PublicNetworkAccess to Disabled:

Update-AzDatabricksWorkspace `
    -ResourceGroupName {{resource-group-name}} `
    -Name {{workspace-name}} `
    -PublicNetworkAccess Disabled

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags	Compliance
💼 APRA CPG 234 → 💼 36f network design — to ensure authorised network traffic flows and to reduce the impact of security compromises;		76	107		no data
💼 APRA CPG 234 → 💼 45 An understanding of plausible worst case scenarios can help regulated entities identify and implement additional controls to prevent or reduce the impact of such scenarios. One example is malware that infects computers and encrypts data, both on the infected computer and any connected storage, including (corporate) networks and cloud storage. Such attacks reinforce the importance of protecting the backup environment in the event that the production environment is compromised. Common techniques to achieve this include network segmentation, highly restricted and segregated access controls and network traffic flow restrictions.		83	115		no data
💼 CIS Azure v5.0.0 → 💼 2.1.10 Ensure 'Allow Public Network Access' is set to 'Disabled' (Automated)			1		no data
💼 CIS Azure v6.0.0 → 💼 2.1.10 Ensure 'Allow Public Network Access' is set to 'Disabled' (Automated)			1		no data
💼 Cloudaware Framework → 💼 Network Exposure			137		no data
💼 FedRAMP High Security Controls → 💼 AC-4(21) Physical or Logical Separation of Information Flows (M)(H)		18	141		no data
💼 FedRAMP Moderate Security Controls → 💼 AC-4(21) Physical or Logical Separation of Information Flows (M)(H)			141		no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(21) Information Flow Enforcement _ Physical or Logical Separation of Information Flows		83	141		no data
💼 UK Cyber Essentials → 💼 1.2 Prevent access to the administrative interface from the internet		85	119		no data