INTRODUÇÃO
This service description document (“Service Description”) outlines the Illumio Environmental Separation Services (“Services”). Illumio will provide Services on the Customer’s existing security infrastructure to Illumio’s software offerings (collectively "Products").
Overview
The Environmental Separation add-on restricts traffic between environments. Typical examples are blocking communication between development and production, or isolating test, lab, and DMZ environments from critical production systems.
Non-production environments usually have weaker security controls, looser access, and less monitoring than production, which makes them a common entry point for attackers moving laterally. Separating environments is one of the fastest ways to reduce that risk. It gives large enterprises a meaningful east-west control without having to segment every application first.
Separation rules are simple to write, but applying them without analysis is risky. Traffic between environments is often legitimate: a shared service, a workload that was labeled incorrectly, or infrastructure sitting in the wrong data center or VLAN. Blocking it outright can disrupt production. For that reason, this add-on requires the core-services policy framework from Basic Policy – Core Services + Ransomware to be in place first, and it starts with a review of the traffic that actually crosses each boundary.
Illumio Professional Services analyzes that cross-boundary traffic, finds any legitimate or required communication, and builds a mitigation plan. The plan either allows the traffic, permanently or temporarily, or corrects the underlying issue. PS then develops the separation policy and prepares it for customer review and provisioning.
The outcome is restricted cross-environment traffic between two unique labeled environments that protects High-trust environments from lower-trust environments. Environmental Separation works alongside ransomware containment and application ringfencing as a complementary control. Used together, these three layers form a complete segmentation strategy: port-level containment, environment-level separation, and application-level ringfencing.
Illumio Part Names covered by this Service Description are:
IL-SVCS-PEOPT-ENV-SEP-ADDON-S
IL-SVCS-PEOPT-ENV-SEP-ADDON-M
IL-SVCS-PEOPT-ENV-SEP-ADDON-L
IL-SVCS-PEOPT-ENV-SEP-ADDON-XL
Who should engage?
This add-on is intended for enterprise customers who have core-services and containment policy in place and want to reduce the risk that non-production environments pose to production.
Recommended stakeholders:
- Security architects and security engineers
- Illumio platform administrators
- Infrastructure and systems administrators
- Network architects and network engineers
- Data center and cloud operations teams
- Application owners whose applications span environments
- Development, test, and release engineering teams
- Change-management stakeholders
- Project managers
Infrastructure and application owners need to be involved. They are best placed to confirm whether cross-boundary traffic is legitimate and to own any label correction or infrastructure move the mitigation plan calls for.
Prerequisites
Package Dependencies
- Basic Policy – Core Services + Ransomware, or the Containment or Segmentation Bundle
- Core-services policy is a mandatory prerequisite. Shared infrastructure services often legitimately cross environment boundaries, and separation rules applied before those services are represented in policy are very likely to block required traffic.
Technical Readiness
- Operational Illumio platform with workloads paired and reporting
- Environment labels applied to in-scope workloads
- Core-services policy framework implemented
- Enough traffic history to analyze communication across the in-scope boundaries
- Required policy objects present, including IP Lists and Unmanaged Workloads
- Administrative access to the PCE for Illumio Professional Services
Customer Readiness
- Project manager or primary point of contact assigned
- Environments and boundaries to be separated identified
- Infrastructure, network, and application owners available
- Change-management process documented
Covered Services
Boundary Definition
- Confirm the environments and the boundaries between them that are in scope, for example development to production, or test, lab, and DMZ to production.
- Confirm how each in-scope environment is represented in the label schema.
- Confirm the workloads and systems that belong to each environment.
- Agree the separation objective for each boundary with customer stakeholders.
Customer Outcome
The customer has an agreed, documented definition of which environments will be separated and which workloads belong to each.
Cross-Boundary Traffic Analysis
- Review observed traffic that crosses each in-scope boundary.
- Identify legitimate or required communication crossing the boundary.
- Identify workloads that appear to be labeled with the wrong environment.
- Identify infrastructure that appears to sit in the wrong environment, data center, or VLAN. Identify shared services that need to be reachable across environments.
- Review findings with infrastructure and application owners to confirm business purpose.
Customer Outcome
The customer knows exactly what traffic crosses its environment boundaries and which of it is legitimate, required, or caused by misclassification or misplacement.
Mitigation Planning
- Build a mitigation plan for each confirmed cross-boundary finding.
- Classify each finding as:
- Traffic to allow permanently
- Traffic to allow temporarily, pending remediation
- A label correction An infrastructure change needed, such as moving a system out of the wrong environment, data center, or VLAN Document the owner, rationale, and recommended action for each finding. Record temporary exceptions so they can be tracked and removed later. Agree the mitigation plan with customer stakeholders.
Customer Outcome
The customer has an agreed plan for every cross-boundary dependency, so separation can go ahead without blocking legitimate production traffic.
Separation Policy Development
- Develop environment separation policy for the agreed boundaries.
- Build approved permanent and temporary exceptions into the policy.
- Validate the policy against the existing core-services and ransomware containment framework.
- Organize the policy structure and related policy objects.
- Create the separation policy in draft so the customer can review it before provisioning.
Customer Outcome
The customer receives draft environment separation policy that restricts cross-environment traffic while preserving approved dependencies, ready for customer review and provisioning.
Documentation and Handoff
- Provide an as-built record of the separation policy, covering boundaries, rules, related objects, and approved exceptions.
- Provide the mitigation plan and a register of temporary exceptions.
- Document the recommended path from draft policy through provisioning, validation, and enforcement.
- Document how Environmental Separation works with ransomware containment and ringfencing policy.
- Document guidance for adding new boundaries and maintaining separation policy.
- Review the policy and documentation with customer stakeholders.
Customer Outcome
The customer has documented separation policy, a tracked plan for closing out temporary exceptions, and a clear path to provisioning and enforcement through its own change-management process.
Assumptions
Core-services policy is implemented before this add-on begins.
Environment labels are applied to in-scope workloads.
Observed traffic represents a point-in-time view.
Infrequent, seasonal, failover, or event-driven communication may not appear in the reviewed data.
The customer confirms the business purpose of traffic that crosses boundaries.
The customer approves and applies label corrections identified in the mitigation plan.
The customer performs any infrastructure changes identified in the mitigation plan, including moving systems between environments, data centers, or VLANs.
The customer tracks and removes temporary exceptions once the related remediation is complete.
The customer reviews and approves separation policy before provisioning to production.
Enforcement cut-over is led by the customer.
The in-scope environment stays materially stable during the engagement.
The customer determines its security objectives and tactical decisions.
Illumio provides best-practice guidance on achieving those objectives.
Customer Requirements
The customer will:
Assign a project manager or primary point of contact.
Identify the environments and boundaries to be separated.
Provide administrative PCE access.
Make infrastructure, network, and application owners available to validate cross-boundary traffic.
Confirm the business purpose of traffic that crosses environment boundaries.
Review and approve the mitigation plan.
Approve and apply label corrections.
Perform any infrastructure changes identified in the mitigation plan.
Track and remove temporary exceptions after remediation.
Review and approve separation policy before provisioning to production.
Perform customer-side change control, provisioning, validation, and enforcement.
Maintain separation policy after the engagement.
Out of Scope/Limitations: Scope Limitations
Limited to the two(2) labeled environments and boundaries agreed during boundary definition.
Separation policy is created in draft only.
Analysis reflects the traffic observed during the engagement.
Effectiveness depends on accurate environment labeling and on customer completion of mitigation actions.
Temporary exceptions remain in policy until the customer completes the related remediation.
Covers separation between environments only.
Out of Scope/Limitations: Excluded Scope
Intra-application host-to-host or role-to-role segmentation
Application Ringfencing
Tier-to-tier segmentation or microsegmentation
Core-services policy development, which is delivered through Basic Policy – Core Services + Ransomware Policy provisioning
Changing VEN enforcement modes, including moving workloads into Selective
Enforcement Enforcement cut-over and production validation
Customer change-management execution
Physical or logical infrastructure migration, including moving systems between data centers, networks, or VLANs
Network redesign or network device configuration
Label schema redesign or label remediation beyond the corrections identified in the mitigation plan
Tracking and removal of temporary exceptions after handoff
Consultancy or configuration of third-party equipment or software
Custom automation, scripting, or integration development
Threat hunting, incident response, or forensic analysis
Ongoing policy management or support after handoff
Expected Timeline
The delivery schedule is set at project initiation based on:
- Purchased add-on size
- Number of environments and boundaries in scope
- Volume of cross-boundary traffic
- Number of findings requiring mitigation
- Stakeholder availability and review cycles.
Delays in confirming cross-boundary traffic, approving the mitigation plan, or completing label corrections may affect the schedule.
Time and Location for Delivery of Services
Working hours are Monday to Friday from 9 am to 5 pm local time (where the Services are delivered).
Out-of-hours work is by arrangement but may require some evening or weekend time.
The Customer shall schedule all remote work in minimum blocks of two (2) hours. Remote work may be scheduled on non-consecutive days.
The Customer shall schedule onsite work in one (1) day minimum blocks of time on consecutive days.
Services may be delivered remotely and/or at the Customer’s designated office location. Any required travel to other locations may be subject to travel time and expenses, at cost.
Illumio may replace a resource delivering the services at its discretion. All efforts will be made to ensure that this does not impact delivery of the services.
The Customer may, with reasonable grounds, request that Illumio replace the resource delivering the Services if the Services are not being delivered to the required standard. In this instance, Illumio will offer a replacement Professional Services resource.
Service Terms
The Services described in this Service Description shall be incorporated by reference into and governed by either: (a) the master agreement between Illumio and the Customer; or (b) if there is no other master agreement between Illumio and the Customer the Illumio Master Subscription Agreement available online at www.illumio.com/eula, including the Supplemental Terms for Professional Services thereto (the “Master Agreement”). This document constitutes a “Service Description” under the Master Agreement, and shall be effective as of the effective date of the relevant Order Form are entered into by and between Illumio and Customer. In the event of any conflict or inconsistency between any terms in this Service Description, the Master Agreement, and the Order Form, the terms of the Order Form shall govern and control. Capitalized terms used but not defined in this Service Description will have the definitions ascribed thereto in the Master Agreement..
Acceptance does not apply to the Services provided by Illumio Professional Services under this Service Description. Illumio may update or modify the Services set forth in this Service Description at any time, provided however, Illumio shall notify Customer if it makes changes that materially reduces the scope of the Services..
The Services are standardized catalog offerings and are not customized statements of work. The Customer may not i) substitute, swap, or trade Services included herein for other services, (ii) increase package limits without purchasing additional services, and (iii) remove or reduce portions of the Service after delivery has begun. Requests for additional functionality or services outside the Services in this Service Description require a separate purchase. Illumio may use certain AI tools to deliver the Services, but Customer may opt out by notifying Illumio in writing. No Customer data or Customer confidential information will be used by Illumio to train large language models in any third-party AI models. All AI tools are fully contained in Illumio server networks and no public AI models interact with Customer data in any way.
Get Started
Talk to our Sales team to learn more about Services.
Explore our Professional Services at illumio.com/services/professional-services
