🛡️ Azure Databricks Workspace Secure Cluster Connectivity is not enabled🟢

• Contextual name: 🛡️ Databricks Workspace Secure Cluster Connectivity is not enabled🟢
• ID: /ce/ca/azure/databricks/no-public-ip
• 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-7507a34e

Similar Internal Rules

Rule	Policies	Flags
✉️ dec-x-7507a34e	1

Description

Open File

Description

Enable secure cluster connectivity (also known as no public IP) on Azure Databricks workspaces to ensure that clusters do not have public IP addresses and communicate with the control plane over a secure connection.

Rationale

Enabling secure cluster connectivity limits exposure to the public internet, improving security and reducing the risk of external attacks.

Impact

Enabling secure cluster connectivity requires careful network configuration. Before secure cluster connectivity can be enabled, Azure Databricks workspaces must be deployed in a customer-managed virtual network (VNet injection). Refer to the policy Azure Databricks Workspace is not deployed in a customer-managed virtual network (VNet).

Audit

This policy flags an Azure Databricks Workspace as INCOMPLIANT if the Parameters JSON field does not contain the enableNoPublicIp parameter set to true.

Default Value

No Public IP is set to Enabled by default.

References

1. https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/secure-cluster-connectivity

... 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 Deploy Azure Databricks workspace with Secure Cluster Connectivity (No Public IP), click the radio button next to Enabled.
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 enableNoPublicIp to true:

az databricks workspace update \
    --resource-group {{resource-group-name}} \
    --name {{workspace-name}} \
    --enable-no-public-ip true

From PowerShell

For each workspace requiring remediation, run the following command to set EnableNoPublicIP to True:

Update-AzDatabricksWorkspace `
    -ResourceGroupName {{resource-group-name}} `
    -Name {{workspace-name}} `
    -EnableNoPublicIP $true

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.9 Ensure 'No Public IP' is set to 'Enabled' (Automated)			1		no data
💼 CIS Azure v6.0.0 → 💼 2.1.9 Ensure 'No Public IP' is Set to 'Enabled' (Automated)			1		no data
💼 Cloudaware Framework → 💼 Network Exposure			137		no data