INTRODUCTION
This service description document (“Service Description”) outlines the Illumio On-Premises PCE Design and Architecture Services (“Services”). Illumio will provide Services on the Customer’s existing security infrastructure to Illumio’s software offerings (collectively "Products").
Overview
The On-Premise PCE Design and Architecture add-on gives customers a right-sized design for an on-premise Policy Compute Engine before any infrastructure is built.
An on-premise PCE runs on one or more nodes. The deployment type depends on scale and resilience requirements. A 2x2 multi-node cluster runs two core nodes and two data nodes for redundancy. A 4x2 cluster runs four core nodes and two data nodes for larger deployments. A supercluster joins two or more replicating clusters into one administrative domain. If the wrong type or size is chosen, the PCE can be under-provisioned, lack resilience, or be expensive to rebuild later.
Illumio Professional Services works with the customer to determine the right PCE type and scale for the current deployment and planned growth. PS then specifies the resources each server needs, defines where the nodes should be placed, and gives the customer setup instructions so the environment is prepared correctly. If the customer plans to split the PCE across data centers, PS helps define the latency and connectivity requirements between sites.
This add-on covers preparation and design only. The PCE itself is built in the separate On-Premise PCE Build add-on.
At the end of the engagement, the customer knows what needs to be built, how large it must be, where it should be built, and what infrastructure must be ready before installation starts.
Illumio Part Names covered by this Service Description are:
- IL-SVCS-OP-PCE-DSGN-ADDON
Who should engage?
This add-on is for customers who need to run the PCE on-premise instead of using the Illumio SaaS platform.
Recommended stakeholders:
- Security architects and Illumio platform owners
- Infrastructure and data center architects
- Server and virtualization administrators
- Network architects and network engineers
- Load balancer administrators DNS, certificate, and email (SMTP) administrators
- Backup and disaster recovery owners
- Change-management stakeholders Project managers
The customer's infrastructure and network teams need to be involved. They own the servers, networks, and supporting services the design depends on, and they will prepare the environment before the build.
Prerequisites
Package Dependencies
- Segmentation Strategy & Roadmap
- This add-on is normally followed by the On-Premise PCE Build add-on.
Technical Readiness
- Decision to deploy the PCE on-premise
- Estimated current and planned workload count
- Candidate data center locations identified Information on available server, virtualization, network, and storage infrastructure
Customer Readiness
- Project manager or primary point of contact assigned
- Infrastructure, network, and data center stakeholders available
- High availability, disaster recovery, and growth requirements identified
- Existing infrastructure standards documented, including server builds, load balancing, certificates, DNS, and email
Covered Services
Requirements and Capacity Review
- Review the current workload count, planned growth, and expected scale of the deployment.
- Review high availability, disaster recovery, and resilience requirements.
- Review candidate data center locations and the customer's infrastructure standards.
- Review integration requirements that affect the design, including load balancing, certificates, DNS, and email.
- Apply Illumio capacity planning guidance to the customer's requirements.
Customer Outcome
The customer's scale, growth, and resilience requirements are documented and ready to be turned into a PCE design.
PCE Architecture Design
- Recommend the PCE deployment type: single-node cluster, 2x2 multi-node cluster, 4x2 multi-node cluster, or supercluster.
- Specify the resources required for each node.
- Define node roles and placement.
- Where the PCE will be split across data centers, define node placement, the latency requirements between sites, and the connectivity requirements.
- Define the load balancing approach for multi-node clusters.
- Define requirements for certificates, DNS, email (SMTP), and network and firewall access.
- Define backup, high availability, and disaster recovery considerations for the recommended design.
- For a single-node cluster, this includes the additional backup and recovery precautions Illumio recommends because an SNC is a single point of failure.
Customer Outcome
The customer receives a right-sized PCE architecture that sets out what will be built, where it will be built, and how it will scale and recover.
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.
Environment Preparation Guidance and Handoff
- Provide PCE design documentation covering the deployment type, node specifications, placement, and supporting requirements.
- Provide setup instructions the customer can use to prepare servers, networks, and supporting services before the build.
- Provide a readiness checklist to confirm the environment is prepared for installation.
- Document design assumptions, dependencies, and decisions still open with the customer.
- Review the design and setup instructions with customer stakeholders.
Customer Outcome
The customer has the documentation and instructions it needs to prepare its environment correctly, so the On-Premise PCE Build add-on can start without redesign or rework.
Assumptions
The customer has decided to deploy the PCE on-premise.
The customer provides accurate current and planned workload counts.
The customer provides accurate information about its infrastructure, data centers, and network.
Recommendations follow Illumio capacity planning guidance for the PCE version being deployed.
The customer's infrastructure and network teams are available within agreed project timelines.
The customer prepares servers, networks, and supporting services according to the provided instructions.
The design reflects the requirements known at the time of the engagement.
A significant change in scale or resilience requirements may require the design to be revisited.
Documents are produced using Illumio templates.
Customer Requirements
The customer will:
Assign a project manager or primary point of contact.
Provide current and planned workload counts and growth expectations.
Provide high availability, disaster recovery, and resilience requirements.
Provide information on available data centers, servers, virtualization, networks, and storage.
Provide existing infrastructure standards, including load balancing, certificates, DNS, and email.
Make infrastructure, network, and data center stakeholders available.
Review and approve the recommended design.
Prepare servers, networks, and supporting services according to the setup instructions.
Complete the readiness checklist before the PCE build begins.
Out of Scope/Limitations: Scope Limitations
Covers preparation and design only.
Covers one PCE design for one deployment.
Recommendations depend on the accuracy of the workload counts, growth estimates, and infrastructure information the customer provides.
Latency and connectivity requirements for split data centers are defined at the design level only.
Network performance is not tested or validated.
The design applies to the PCE version being deployed and to Illumio capacity planning guidance current at the time of the engagement.
Out of Scope/Limitations: Excluded Scope
PCE installation, configuration, or build, which is delivered through the On-Premise PCE Build add-on
Provisioning, building, or patching servers, or maintaining their operating systems
Configuring load balancers, DNS, certificates, email, or network and firewall devices
Procuring or generating certificates
Network latency testing or performance validation
Backup, high availability, or disaster recovery implementation or testing
PCE upgrades, maintenance, or ongoing administration
Migration from on-premise to
SaaS SaaS PCE design or configuration
VEN deployment, labeling, discovery, or policy work
Consultancy or configuration of third-party equipment or software
Custom automation, scripting, or integration development
Ongoing architecture advisory after handoff
Expected Timeline
The delivery schedule is set at project initiation based on:
- Deployment scale and planned growth
- Recommended PCE deployment type
- Whether the PCE is split across data centers
- Availability of infrastructure information
- Stakeholder availability and review cycles.
Delays in providing infrastructure information, making design decisions, or getting approvals 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
