Implementing Data Center Macro Segmentation for Service-Based Zero Trust (Zero Trust Activity 5.3.1)
We’ve been steadily building our Zero Trust network. From basic network segmentation (5.2.3) to the fine-grained control of micro segmentation down to individual workloads (5.4.1), our goal is to eliminate lateral movement. Now, we step back to focus on securing the larger, critical boundaries within our datacenters and cloud environments. This brings us to Zero Trust Activity 5.3.1: Datacenter Macro segmentation.
This activity focuses on DoD Components leveraging service-based architectures to restrict lateral movement between public and private components of a solution’s architecture. Unlike micro segmentation (5.4.1) which isolates individual workloads, macro-segmentation divides your network into broad, logical security zones based on service tiers or criticality (e.g., separating your public-facing web servers from your internal application servers and then from your database servers). A crucial element is that proxy and/or enforcement checks are integrated with the SDN or alternative networking approach solution(s) based on device attributes and behavior. This ensures that even at these larger boundaries, access decisions are dynamic and context-aware, not just based on static network rules.
This activity is vital for containing broad attacks. If an attacker breaches your public-facing web tier, robust macro-segmentation ensures they cannot easily pivot to your sensitive internal application or database tiers without explicit re-verification.
The outcomes for Activity 5.3.1 highlight the establishment of these enforcement points:
- Establish proxy/enforcement checks of attributes (device, location, data), access and flow (client, tenant, traffic patterns), and Component principles (asset life cycle, compliance, policy).
The ultimate end state underscores a highly secure and efficient network architecture: SDN or alternative networking approach solutions incorporate proxy and enforcement checks based on device attributes and behavior, ensuring robust security. Application delivery control proxies, SIEM logging, UAM, and authentication decision points are integrated and operational. Segmentation gateways are deployed to enhance network security and efficiency. This signifies comprehensive control over broad service-level interactions.
Solutions for Achieving Datacenter Macro Segmentation
Implementing Activity 5.3.1 requires leveraging your programmable network infrastructure to define and enforce boundaries between major service tiers, driven by device attributes and behavior:
- Designing Service-Based Macro Segments:
- Process: Identify and define distinct logical zones for major service components within your datacenter and cloud environments (e.g., Internet DMZ, Web Tier, Application Tier, Database Tier, Management Networks, Development Environments).
- Data Flow Analysis: Map the communication flows between these broad tiers to understand necessary traffic.
- Implementing Network Segmentation Technologies:
- Utilize traditional network segmentation technologies, but manage them programmatically via your SDN:
- VLANs (Virtual Local Area Networks) & VRFs (Virtual Routing and Forwarding): For logical separation of networks and routing tables.
- Next Generation Firewalls (NGFWs) / Traditional Firewalls: Deployed at the boundaries between macro segments to enforce policies and block lateral movement.
- Access Control Lists (ACLs): Configured on routers and switches for basic traffic filtering.
- These technologies provide the underlying enforcement mechanism for macro-segmentation.
- Utilize traditional network segmentation technologies, but manage them programmatically via your SDN:
- Integrating Proxy and/or Enforcement Checks with SDN/Programmable Network:
- This is where Zero Trust principles are applied to macro-segmentation. Integrate specific enforcement points into your SDN or alternative networking approach (from 5.2.1, 5.2.2).
- Application Delivery Control Proxies (ADCs): (As per the end state) Deploy ADCs that manage traffic between service tiers (e.g., from Web to App tier). These ADCs, integrated with the SDN, can enforce policies based on device attributes and behavior, acting as intelligent proxies for inter-tier communication.
- Segmentation Gateways: (As per the end state) Configure segmentation gateways (often NGFWs) to receive dynamic policy updates from the SDN controller based on real-time device attributes and behavior, allowing them to dynamically permit or deny traffic between macro segments.
- Policy Decision Points (PDPs): The SDN or integrated policy engines act as PDPs, consuming device attributes (e.g., managed status, compliance score) and behavioral data (e.g., anomalies detected by UEBA) to make access decisions for traffic crossing macro-segment boundaries.
- Leveraging Device Attributes and Behavior for Enforcement:
- Ensure that the proxy/enforcement checks are informed by real-time device context:
- This allows policies to dynamically restrict or permit traffic between macro segments based on the current trustworthiness of the connecting device.
- Establishing Comprehensive Logging and Monitoring:
- SIEM Logging: Ensure all enforcement points (firewalls, ADCs, SDN components) log access and policy enforcement decisions. Feed these logs automatically into your SIEM (Activity 7.1.2) for centralized monitoring, correlation, and analysis.
- UAM Integration: Integrate User Activity Monitoring (UAM) to understand user behavior patterns related to resource access across segment boundaries.
How Zscaler Can Be Leveraged to Deliver Desired Outcomes and End State:
Zscaler’s cloud-native Zero Trust Exchange provides a unique and powerful way to achieve the goals of Datacenter Macro Segmentation, particularly by leveraging device attributes and behavior for policy enforcement, even if its architecture differs from traditional on-premises SDN.
- Service-Based Architecture (Logical Segmentation): Zscaler’s Zero Trust Network Access (ZTNA) and Cloud Firewall capabilities enable logical, service-based segmentation. Instead of direct network connections between “public” users/devices and “private” application tiers, Zscaler brokers access. Users and devices never directly touch the datacenter network. This inherently restricts lateral movement by making applications “dark” to unauthorized users. You define policies based on who, on what device, can access which specific application (service), effectively creating secure “service components” and controlling traffic between public (user/internet) and private (application) components.
- Proxy and Enforcement Checks based on Attributes/Behavior: Zscaler’s Zero Trust Exchange acts as the proxy/enforcement point. It inspects all traffic inline and enforces policies based on:
- Device Attributes: Integrates with UEM/EDR solutions (e.g. Trellix) to pull device posture, compliance, and managed status.
- Device Behavior: Consumes user and device risk scores (from IdP/UEBA, fed into SIEM) to inform policy decisions, ensuring robust security.
- This directly fulfills the outcome of establishing “proxy/enforcement checks of attributes (device, location), access and flow,” and aligns with “SDN or alternative networking approach solutions incorporate proxy and enforcement checks based on device attributes and behavior.”
- Integration with “SDN or alternative networking approach solution(s)”: Zscaler itself represents a leading “alternative networking approach solution.” Its cloud-native control plane manages its globally distributed enforcement points, allowing for programmatic policy changes via APIs, which is analogous to how an SDN controller manages its network.
- Leveraging Integrated Components for the End State:
- Application Delivery Control Proxies: Zscaler’s platform itself acts as an intelligent proxy that can dynamically control application delivery by brokering access based on policy.
- SIEM Logging & UAM: Zscaler’s comprehensive logging capabilities feed directly into your SIEM (e.g., Elastic Security), providing rich data for monitoring, analytics, and User Activity Monitoring (UAM) for traffic flowing through its platform.
- Authentication Decision Points: Zscaler integrates with your IdP (e.g., Okta) to verify identity and consume identity-based policy decisions.
- Segmentation Gateways: Zscaler’s Cloud Firewall and ZTNA act as logical segmentation gateways, enforcing policies between public/private access tiers.
Key Items to Consider:
- Defining Service Boundaries: Clearly define the logical boundaries of your service components (web, app, DB) for effective policy application, especially in complex and dynamic cloud-native environments.
- Integrating Device/Behavioral Context: Ensuring that your NAC/ZTNA/firewall enforcement points receive real-time, accurate device attributes and behavioral risk scores from UEM, EDR, and UEBA solutions.
- Policy Granularity: While macro-segmentation is broader, policies at these boundaries should still be granular enough to leverage identity and context, not just simple IP subnets.
- Performance Implications: Implementing inline proxy or enforcement checks, especially at high traffic volumes, requires robust solutions.
- Visibility and Monitoring: Ensure comprehensive logging from all enforcement points is fed into your SIEM for continuous monitoring of traffic crossing macro-segment boundaries and detecting policy violations.
- Hybrid Environment Management: For organizations with mixed on-premises datacenters and cloud environments, ensure consistent macro-segmentation policies and enforcement across both.
For the Technical Buyer
Activity 5.3.1 is about strategically segmenting your datacenter and cloud environments into logical zones based on service components, and then applying Zero Trust principles to control traffic between these zones. For technical buyers, this means moving beyond simple network segmentation to enforcing policies at these boundaries based on device attributes and behavior. Leveraging a cloud-native platform like Zscaler provides a powerful solution for this, enabling logical, service-based segmentation with proxy and enforcement checks driven by real-time context (device health, user identity). This ensures that lateral movement between your public-facing and private application tiers is strictly controlled, significantly enhancing the security and resilience of your mission-critical applications and data within your Zero Trust architecture.
Pillar: Network and Environment
Capability: 5.3 Macro Segmentation
Activity: 5.3.1 Datacenter Macro Segmentation
Phase: Target Level
Predecessor(s):
- 5.4.1 Implement Micro-segmentation
- 3.4.1 Resource Authorization Part 1
- 3.4.6 SDC Resource Authorization Part 1
Successor(s): None








