OpenParable
Skip to content
← Back to skills

Cis Azure Compute 15.4

DevOps & Security
cis-azure-compute-15.4

Cis Azure Compute 15.4 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure Private endpoints are considered for Batch accounts

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/CIS_Microsoft_Azure_Compute_Services_Benchmark_v2.0.0/cis-azure-compute-15.4/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-azure-compute-15-4, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Ensure Private endpoints are considered for Batch accounts

Description

Private endpoints for Azure Batch accounts ensure all network communication occurs over private networks rather than the public internet.

Rationale

Configuring private endpoints for Azure Batch accounts ensures all network traffic remains within the Microsoft Azure backbone network, eliminating exposure to public internet threats. This meets zero-trust security principles by enforcing network-level isolation and reducing the attack surface. The configuration also enables precise network monitoring through Azure Network Watcher and NSG flow logs.

Impact

Private endpoints come with an increased cost and complexity.

Audit Procedure

Using Azure Portal

  1. Login to Azure Portal https://portal.azure.com/
  2. Navigate to Batch Accounts

For each Batch Account, perform the following:

  1. Under Settings, click on Networking
  2. Click the Private access tab
  3. For each Private Endpoint listed, ensure that the connection state is Approved

Using Azure CLI

To list Private Endpoints from CLI:

az network private-endpoint list \
    --resource-group <RESOURCE_GROUP> \
    --query "[?privateLinkServiceConnections[?contains(properties.privateLinkServiceId, 'Microsoft.Batch/batchAccounts/<BATCH_ACCOUNT_NAME>')]]"

Expected: Should return at least one private endpoint configuration.

Using Azure PowerShell

To list Private Endpoints from PowerShell:

Get-AzPrivateEndpoint -ResourceGroupName <RESOURCE_GROUP> |
    Where-Object { $_.PrivateLinkServiceConnections.PrivateLinkServiceId -match "Microsoft.Batch/batchAccounts/<BATCH_ACCOUNT_NAME>" }

Expected Result

At least one private endpoint should be configured and in Approved connection state for each Batch account.

Remediation

Using Azure Portal

  1. Navigate to your Batch account
  2. Under the Settings drop down, click Networking
  3. Click the Private access tab
  4. Click + Private endpoint
  5. Configure:
    • Virtual network and subnet
    • DNS integration (auto-approved recommended)
    • Target subresource: batchAccount

Using Azure CLI

az network private-endpoint create \
  --name batch-pe \
  --resource-group <rg> \
  --vnet-name <vnet> \
  --subnet <subnet> \
  --private-connection-resource-id /subscriptions/<sub-id>/resourceGroups/<rg>/providers/Microsoft.Batch/batchAccounts/<account> \
  --group-id batchAccount \
  --connection-name batch-connection

Default Value

Private endpoints are not configured by default.

References

  1. https://docs.microsoft.com/en-us/azure/batch/private-connectivity

Profile

Level 2 | Automated