INTRODUÇÃO
This service description document (“Service Description”) outlines the Illumio On-Premises PCE Build 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 Build add-on installs the on-premise Policy Compute Engine (PCE) and brings it online, following the design produced in the On-Premise PCE Design and Architecture add-on.
The design phase identifies the required server configuration. The PCE build package carries out that design. Illumio Professional Services prepares the customer-provisioned servers for PCE installation, installs the PCE software, completes the required configuration, and brings the cluster up.
A PCE installation depends on correct capacity sizing, storage partitions, load balancing, DNS, TLS certificates, email, and a set of operating system dependencies and settings. Errors in any of these can stop the PCE from starting or cause it to run unreliably. PS works through each prerequisite, installs the PCE, and verifies that the cluster is working.
The engagement is complete once the PCE databases are online and administrators can log in to the PCE web console. At that point the platform is ready for Platform Foundation Deployment activities such as SSO, logging integration, and VEN onboarding.
Illumio Part Names covered by this Service Description are:
- IL-SVCS-OP-PCE-BLD-ADDON-S
- IL-SVCS-OP-PCE-BLD-ADDON-M
- IL-SVCS-OP-PCE-BLD-ADDON-L
- IL-SVCS-OP-PCE-BLD-ADDON-XL
Who should engage?
This add-on is for customers who will run the PCE on-premise and have an approved PCE design.
Recommended stakeholders include:
- Illumio platform owners and administrators
- Server and virtualization administrators
- Linux system administrators
- Network engineers and firewall administrators
- Load balancer administrators DNS, certificate, and email (SMTP) administrators
- Storage administrators
- Change-management stakeholders
- Project managers
Server and network administrators need to be available during the build. Many installation steps rely on root access, firewall changes, load balancer configuration, and DNS updates that the customer controls.
Prerequisites
Package Dependencies
On-Premise PCE Design and Architecture, or an equivalent approved PCE design
Technical Readiness
- Servers or VMs provisioned to the approved design, with the specified CPU, RAM, storage, and IOPS
- Storage device partitions configured as specified
- Supported operating system installed on each node
- Root or equivalent administrative access for Illumio Professional Services
- IP addresses assigned for the PCE
- DNS domain names configured
- Load balancer in place for multi-node clusters
- TLS/SSL certificates obtained to the required types and settings
- Mail (SMTP) service available
- Required PCE ports open, including reserved port ranges for multi-node clusters
- PCE software packages available
- SAML identity provider details, where applicable
Customer Readiness
- Project manager or primary point of contact assigned
- Readiness checklist from the design phase completed
- Server, network, load balancer, DNS, and certificate administrators available during the build window
- Change approvals in place for the build window
- Full organization name confirmed for PCE configuration
Covered Services
Pre-Installation Validation
- Confirm that the provisioned servers or VMs match the approved design.
- Confirm capacity, storage partitions, IP addressing, DNS, load balancing, certificates, and mail readiness.
- Confirm that required ports and network paths are open.
- Confirm administrative access and permissions on each node.
- Identify any remaining gaps and the customer actions needed to close them.
Customer Outcome
The customer knows its environment meets PCE installation requirements before installation starts, which reduces the risk of rework or a failed build.
Server Preparation
- Install the required operating system package dependencies and libraries on each node.
- Configure operating system settings required by the PCE, including NTP, iptables, UTF-8 locale, trusted CA, syslog, process and file limits, and kernel parameters.
- Check file and directory permissions required by the PCE.
Customer Outcome
Each node is prepared to Illumio's installation requirements and ready for the PCE software.
PCE Installation and Configuration
- Install the PCE and UI software packages on each node.
- Configure the PCE runtime environment according to the approved design, including node roles, cluster configuration, and FQDN.
- Install and configure TLS certificates.
- Configure mail settings.
- Complete initial cluster configuration and create the initial administrative account.
- Troubleshoot installation issues within the Illumio software.
Customer Outcome
The PCE software is installed and configured on every node according to the approved design.
Build Validation and Handoff
- Bring up the PCE cluster.
- Confirm that the PCE databases are online.
- Confirm cluster health and node status.
- Confirm that administrators can log in to the PCE web console.
- Document the as-built configuration, including nodes, roles, certificates, and key configuration settings.
- Review the build and documentation with customer stakeholders.
Customer Outcome
The customer has a running on-premise PCE, with databases online and web console access confirmed, and is ready to begin Platform Foundation Deployment.
Assumptions
The customer has an approved PCE design and has provisioned servers or VMs to match it.
The customer has completed the design-phase readiness checklist before the build begins.
The customer provides root or equivalent administrative access to each node.
The customer supplies valid TLS certificates, DNS records, IP addresses, and mail configuration.
For multi-node clusters, the customer configures the load balancer.
The customer makes firewall and network changes needed to open required ports and paths.
Security scanners and similar tools that probe the PCE or its environment are not run against the PCE.
Illumio does not support their use because they can interfere with PCE operation.
Customer server, network, and certificate administrators are available during the build window.
A standard build normally takes about one full day of effort when all prerequisites are complete.
The customer is responsible for backup, patching, monitoring, and ongoing administration of the PCE after handoff.
Customer Requirements
The customer will:
Assign a project manager or primary point of contact.
Provision servers or VMs to the approved design, including CPU, RAM, storage, IOPS, and partitions.
Install a supported operating system on each node.
Provide root or equivalent administrative access.
Assign IP addresses and configure DNS records.
Obtain and provide TLS certificates.
Configure the load balancer for multi-node clusters.
Provide mail (SMTP) service details.
Open required ports and network paths.
Complete the design-phase readiness checklist before the build.
Make server, network, load balancer, DNS, and certificate administrators available during the build window.
Obtain change approvals for the build window.
Take ownership of backup, patching, monitoring, and ongoing administration after handoff.
Out of Scope/Limitations: Scope Limitations
Covers one PCE cluster built to the approved design.
Completion is defined as PCE databases online and successful login to the PCE web console.
Depends on the customer completing all installation prerequisites before the build window.
Installation issues caused by incomplete or incorrect customer prerequisites may extend the effort and require change control.
Covers installation of the PCE version agreed at project initiation.
Out of Scope/Limitations: Excluded Scope
PCE design and capacity planning, delivered through the On-Premise PCE Design and Architecture add-on
Hardware procurement, server or VM provisioning, and operating system installation
Operating system hardening, patching, or ongoing maintenance
Load balancer, DNS, firewall, network, or storage configuration
Certificate procurement or generation
Mail server configuration
Backup, high availability, or disaster recovery implementation or testing
PCE upgrades or ongoing PCE administration
SSO, SIEM, or logging integration, delivered through Platform Foundation Deployment
VEN installation on PCE nodes or other workloads
Labeling, discovery, or policy work
Consultancy or configuration of third-party equipment or software
Custom automation, scripting, or integration development
Ongoing support after handoff, other than through standard Illumio support channels
Expected Timeline
A standard PCE build normally takes about one full day of effort once all prerequisites are complete. The delivery schedule is set at project initiation based on:
- Purchased package size
- PCE deployment type and number of nodes
- Number of data centers or sites
- Readiness of customer prerequisites
- Availability of customer administrators and the approved build window
Incomplete prerequisites, access delays, certificate problems, or network changes made during the build window may extend 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
