用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-foundations-2-1-11命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-azure-foundations-2.1.11 |
| description | Ensure private endpoints are used to access Azure Databricks workspaces |
| category | cis-azure-foundations |
| version | 5.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","databricks","analytics"] |
| cis_id | 2.1.11 |
| cis_benchmark | CIS Microsoft Azure Foundations Benchmark v5.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | ["cis-azure-foundations-2.1.1","cis-azure-foundations-2.1.9","cis-azure-foundations-2.1.10"] |
| prerequisites | [] |
| severity_boost | {} |
Use private endpoints for Azure Databricks workspaces to allow clients and services to securely access data located over a network via an encrypted Private Link. To do this, the private endpoint uses an IP address from the VNet for each service. Network traffic between disparate services securely traverses encrypted over the VNet. This VNet can also link addressing space, extending your network and accessing resources on it. Similarly, it can be a tunnel through public networks to connect remote infrastructures together. This creates further security through segmenting network traffic and preventing outside sources from accessing it.
Using private endpoints for Azure Databricks workspaces ensures that all communication between clients, services, and data sources occurs over a secure, private IP space within an Azure Virtual Network (VNet). This approach eliminates exposure to the public internet, significantly reducing the attack surface and aligning with Zero Trust principles. Additionally, integrating Databricks with a VNet enables network segmentation, fine-grained access control, and hybrid connectivity through VNet peering or VPN/ExpressRoute.
If an Azure Virtual Network is not implemented correctly, this may result in the loss of critical network traffic.
Private endpoints are charged per hour of use. Refer to https://azure.microsoft.com/en-us/pricing/details/private-link/ and https://azure.microsoft.com/en-us/pricing/calculator/ to estimate potential costs.
Before a private endpoint can be configured, Azure Databricks workspaces:
Ensure that Azure Databricks is deployed in a customer-managed virtual network (VNet).Ensure 'Enable No Public IP' is set to 'Yes'.Ensure the requirements and concepts are considered carefully before applying this recommendation. Refer to https://learn.microsoft.com/en-us/azure/databricks/security/network/classic/private-link for more information.
Azure Databricks.Settings, click Networking.Private endpoint connections.Approved.Run the following command to list workspaces:
az databricks workspace list
For each workspace, run the following command to get the privateEndpointConnections configuration:
az databricks workspace show --resource-group <resource-group> --name <workspace> --query privateEndpointConnections
Ensure a private endpoint connection is returned with a privateLinkServiceConnectionState status of Approved.
Run the following command to list workspaces:
Get-AzDatabricksWorkspace
Run the following command to get the workspace in a resource group with a given name:
$workspace = Get-AzDatabricksWorkspace -ResourceGroupName <resource-group> -Name <workspace>
Run the following command to get the PrivateEndpointConnection configuration:
$workspace.PrivateEndpointConnection | Select-Object -Property Id,PrivateLinkServiceConnectionStateStatus
Ensure a private endpoint connection is returned with a PrivateLinkServiceConnectionStateStatus of Approved. Repeat for each workspace.
258823f2-4595-4b52-b333-cc96192710d8 - Name: 'Azure Databricks Workspaces should use private link'Each workspace should have at least one private endpoint connection with a privateLinkServiceConnectionState status of Approved. No public network paths should be the sole means of access.
Azure Databricks.Settings, click Networking.Private endpoint connections.+ Private endpoint.Project details, select a Subscription and a Resource group.Instance details, provide a Name, Network Interface Name, and select a Region.Next : Resource >.Target sub-resource.Next : Virtual Network >.Networking, select a Virtual network and a Subnet.Private IP configuration and Application security group.Next : DNS >.Private DNS integration.Next : Tags >.Next : Review + create >.Create.For each workspace requiring remediation, run the following command to create a private endpoint connection:
az network private-endpoint create --resource-group <resource-group> --name <private-endpoint> --location <location> --vnet-name <virtual-network> --subnet <subnet> --private-connection-resource-id <workspace> --connection-name <private-endpoint-connection> --group-id <browser_authentication|databricks_ui_api>
Private endpoints are not configured for Azure Databricks workspaces by default.
This recommendation is based on the Common Reference Recommendation Ensure Private Endpoints are used to access {service}, from the Common Reference Recommendations > Networking > Private Endpoints section.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 12.2 Establish and Maintain a Secure Network Architecture | x | x | |
| v7 | 14.1 Segment the Network Based on Sensitivity | x | x |
| Techniques / Sub-techniques | Tactics | Mitigations |
|---|---|---|
| T1537 | TA0010 | M1037 |
Level 2 | Automated