Skip to content

East-West Communication Map — Production Spoke

Status: Current as of 2026-04-16 Owner: Infrastructure Related: azure-network-topology.md, nseg-proposed-rules.md

This document captures the required east-west (spoke-to-spoke and intra-spoke) communication paths for the production environment. The purpose is to make explicit which traffic must be permitted across subnet boundaries so NSG and UDR rules can be tightened without breaking production workloads.

East-west enforcement happens at two layers:

  1. UDR route tables — all inter-spoke traffic is forced through the Palo Alto NVA at 10.99.2.4 for stateful inspection.
  2. NSG rules — subnet-level allow/deny rules supplement UDR enforcement.

Production Spoke CIDRs

Spoke / SubnetCIDRPurpose
Production VNet (vnet-prod)10.20.0.0/16Production workloads
- servers-subnet10.20.1.0/24Tier-1 application servers
- workers-subnet10.20.2.0/24Worker / compute nodes
Identity VNet10.10.0.0/16AD domain controllers
- ad-subnet10.10.1.0/24ACTDIRAP01, ACTDIRAP02, RODC
Dashboard VNet10.5.0.0/16Dashboard, reporting
Legacy Svcs (CiriusSvcsVNET)10.4.0.0/16ACTDIRAP04/05, WRKBIZAP payer traffic
Dev VNet10.30.0.0/16Non-prod
Firewall VNet hub10.99.0.0/16Palo Alto NVA, Twingate

Required East-West Flows (MUST be allowed)

Production to Identity (authentication, directory)

SourceDestinationProtocol / PortPurpose
10.20.0.0/1610.10.1.0/24TCP/UDP 88Kerberos
10.20.0.0/1610.10.1.0/24TCP/UDP 389LDAP
10.20.0.0/1610.10.1.0/24TCP 636LDAPS
10.20.0.0/1610.10.1.0/24TCP 3268, 3269Global Catalog
10.20.0.0/1610.10.1.0/24TCP/UDP 53DNS (AD-integrated)
10.20.0.0/1610.10.1.0/24TCP/UDP 464Kerberos password
10.20.0.0/1610.10.1.0/24TCP 445SMB (SYSVOL, GPO)
10.20.0.0/1610.10.1.0/24TCP 135, 49152-65535RPC / AD replication
10.10.1.0/2410.20.0.0/16TCP/UDP 88, 389, 636, 53Return authentication traffic

Production servers to Production workers (application traffic)

SourceDestinationProtocol / PortPurpose
10.20.1.0/24 (servers)10.20.2.0/24 (workers)TCP defined app portsApp-to-worker task dispatch
10.20.2.0/24 (workers)10.20.1.0/24 (servers)TCP defined app portsWorker-to-app result return

Application ports are workload-specific and documented in the Palo Alto App-ID mappings. NSGs allow the broader subnet-to-subnet flow; Palo Alto enforces App-ID on inter-subnet traffic that routes through the NVA.

Workers to RD Gateway (administrative access)

SourceDestinationProtocol / PortPurpose
10.20.2.0/24 (workers)CGIRDPAZP01 (10.20.2.10/32)TCP 3389RDP via RD Gateway only
10.99.5.0/24 (Twingate)CGIRDPAZP01 (10.20.2.10/32)TCP 443HTTPS to RD Gateway Web

Direct RDP from workstation to worker VM is blocked by Deny-RDP-From-Servers and Deny-RDP-From-Workers NSG rules.

Veeam to all VMs (backup)

SourceDestinationProtocol / PortPurpose
Veeam VMall prod VMsTCP 135, 445, 6162, 2500-3300Veeam backup proxy + VSS
Veeam VMall prod VMsTCP 10000-10100Data transfer

Legacy Svcs (CiriusSvcsVNET 10.4.0.0/16)

SourceDestinationProtocol / PortPurpose
10.4.0.0/16 (WRKBIZAP)payer external IPsTCP 443Medicare payer API
Prod workers10.4.0.0/16 (ACTDIRAP04/05)TCP 88, 389, 636Legacy AD queries

Target state H2 2026: migrate WRKBIZAP off CiriusSvcsVNET, decommission this VNet. See wrkbizap-migration-plan.md.

Blocked East-West (MUST be denied)

These flows are explicitly denied by NSG rules on both nsg-servers and nsg-workers to prevent lateral movement:

SourceDestinationProtocol / PortNSG Rule
10.20.2.0/24 (workers)10.20.1.0/24 (servers)TCP 3389servers_deny_rdp_from_workers (Deny, pri 3000)
10.20.2.0/24 (workers)10.20.1.0/24 (servers)TCP 5985, 5986servers_deny_winrm_from_workers (Deny, pri 3010)
10.20.2.0/24 (workers)10.20.1.0/24 (servers)TCP 135servers_deny_wmi_from_workers (Deny, pri 3020)
10.20.1.0/24 (servers)10.20.2.0/24 (workers)TCP 3389workers_deny_rdp_from_servers (Deny, pri 3000)
10.20.1.0/24 (servers)10.20.2.0/24 (workers)TCP 5985, 5986workers_deny_winrm_from_servers (Deny, pri 3010)
10.20.1.0/24 (servers)10.20.2.0/24 (workers)TCP 135workers_deny_wmi_from_servers (Deny, pri 3020)

Rationale: workers have no legitimate reason to RDP / WinRM / WMI into servers (and vice versa). These are the primary hands-on-keyboard lateral movement protocols. Administrative access comes through RD Gateway only.

Out-of-Scope (Cross-Spoke)

Non-production spokes (Dev, Legacy Svcs) MUST route through Palo Alto NVA even for intra-VNet peered traffic. UDRs at the subnet level send all non-local spoke CIDRs to next_hop = 10.99.2.4. See azure-network-topology.md section East-West Enforcement.

Change Log

DateChangeAuthor
2026-04-16Initial east-west communication mapKobe

Internal use only — Cirius Group