Segmentation Strategy & Roadmap

Bold black left arrow symbol.Service Description Library
/
Service Description

EINFÜHRUNG

This service description document (“Service Description”) outlines the Illumio Segmentation Strategy & Roadmap Services (“Services”). Illumio will provide Services on the Customer’s existing security infrastructure to Illumio’s software offerings (collectively "Products").

Overview

The Segmentation Strategy & Roadmap package establishes a customer-specific Zero Trust Segmentation strategy before technical deployment and policy activities begin.

The engagement aligns business objectives, security requirements, infrastructure realities, compliance obligations, and operational ownership into a documented segmentation roadmap that guides subsequent Illumio implementation activities. Illumio Professional Services collects information directly from customer stakeholders and from pre-sales intake materials, then develops a high-level view of the customer's environment, desired outcomes, deployment priorities, and recommended order of operations.

The engagement documents the customer's current network and security posture, identifies strategic considerations such as legacy operating systems or compliance requirements, establishes responsibility and governance models, and defines the value milestones expected throughout the customer's segmentation journey.

The engagement produces a single customer-specific High-Level Design and Roadmap Document that serves as the foundational reference throughout the customer's visibility, containment, and segmentation program.

Illumio Part Names covered by this Service Description are:

  • IL-SVCS-STRA-SEGSTRAT-S
  • IL-SVCS-STRA-SEGSTRAT-M
  • IL-SVCS-STRA-SEGSTRAT-L
  • IL-SVCS-STRA-SEGSTRAT-XL

Who should engage?

Recommended stakeholders include:

  • Security leadership
  • Security architects
  • Security engineers
  • Infrastructure architects
  • Enterprise architects
  • Cloud architects
  • Network architects
  • Platform owners
  • Application owners
  • Infrastructure operations teams
  • Compliance stakeholders
  • Program managers
  • Project managers
  • Customer Success representatives Executive sponsors

Participation from both business and technical stakeholders is strongly recommended to ensure security objectives, operational realities, and application priorities are accurately represented.

Prerequisites

Package Dependencies

  • None  

Technical Readiness

  • Existing infrastructure information available
  • Security architecture information available
  • Network architecture information available
  • Available application inventory if known
  • Existing security controls documented where possible  
  • Customer Readiness Executive sponsor identified
  • Project lead assigned Security stakeholders identified
  • Infrastructure stakeholders identified
  • Customer outcome objectives identified
  • Stakeholder availability for discovery sessions

Covered Services

Project Kickoff and Objective Alignment

  • Conduct project kickoff with customer stakeholders.
  • Review customer business objectives and desired security outcomes.
  • Confirm whether the customer's target outcome is visibility, containment, or segmentation.
  • Review the problem the customer intends to solve.
  • Confirm project stakeholders, project lead, and organizational structure.
  • Review the purchased package bundle and expected engagement sequence.

Customer Outcome

Customer and Illumio share a documented understanding of program objectives, stakeholders, and the intended engagement path.

Strategic Data Collection

  • Collect environment and program information directly from customer stakeholders.
  • Incorporate information gathered during pre-sales intake and outcome-alignment activities.
  • Review in-scope deployment environments and planned Illumio footprint.
  • Review total environment scale, including node counts, datacenter locations, cloud environments, office locations, and branch offices.
  • Review workload operating systems, including Windows, Linux, and legacy platforms.
  • Review container platforms in use.
  • Review environment breakdown, including DMZ, development, test, and production boundaries.
  • Review high-value application lists where available to support application-tiering discussions.
  • Review application-owner and business-unit ownership structures where available.
  • Review compliance requirements such as DORA, PCI, HIPAA, and SWIFT.
  • Review special data-security requirements such as Federal or restricted-support considerations.

Customer Outcome

Customer's environment, scale, operating platforms, compliance obligations, and business priorities are documented in a single consolidated view for strategic planning."

Current Security and Network Posture

  • Review Review existing firewall and security controls in place today.
  • Review Windows Firewall and iptables usage.
  • Review cloud-native security controls.
  • Review internal east-west firewall controls.
  • Review VLAN and network-based separation approaches.
  • Review network design information.
  • Review network mapping considerations such as NAT, MIP, load balancer, and accelerator configurations.
  • Identify special circumstances such as legacy operating systems or constrained platforms.

Customer Outcome

Customer receives a documented view of current network and security posture, including architectural factors that will influence segmentation design and deployment sequencing.

Segmentation Strategy and Roadmap Development

  • Develop the recommended order of operations for visibility, containment, and segmentation.
  • Develop high-level segmentation architecture recommendations.
  • Develop application-tiering recommendations based on available high-value application information.
  • Define value milestones expected throughout the project.
  • Define the recommended package sequence and ongoing high-level plan.
  • Identify recommendations to avoid engagement slowdowns.
  • Identify potential future roadblocks and recommended mitigations.

Customer Outcome

Customer receives a prioritized segmentation roadmap that sequences Illumio adoption according to business objectives, environment complexity, and security priorities."

Operational Readiness and Governance Planning

  • Document the customer responsibility matrix.
  • Document Customer Success RACI information.
  • Document project lead and organizational structure.
  • Review asset-list requirements for future deployment activities.
  • Review VEN package preparation requirements.
  • Document required documentation and reference materials.
  • Provide relevant knowledge base references.
  • Document training links and expected training requirements.
  • Document support model and account team engagement information.
  • Provide deployment-focused best-practice guidance.

Customer Outcome

Customer understands operational responsibilities, required preparation, training expectations, and support engagement model before technical deployment begins.

High-Level Design and Roadmap Documentation and Handoff

  • Produce a network posture diagram representing the customer's environment.
  • Produce the customer-specific High-Level Design and Roadmap Document, consolidating environment profile, security posture, segmentation strategy, roadmap, governance model, readiness requirements, and value milestones.
  • Review the document and recommendations with customer stakeholders.
  • Confirm alignment to future service packages and next-step activities.

Customer Outcome

Customer receives a single documented strategy and roadmap that guides the segmentation program and serves as the reference point for subsequent Illumio engagements.

Assumptions

Customer provides accurate environment, network, and application information.

Customer provides available architecture documentation.

Customer stakeholders participate in data-collection and review sessions.

Customer goals, priorities, and compliance requirements are communicated accurately.

Information provided by customer stakeholders reflects the planned deployment scope.

Pre-sales intake information is available where applicable.

Customer responds to information requests within agreed project timelines.

Environment information provided is sufficiently detailed to support high-level strategic planning.

Customer Requirements

The customer will:  

Assign a project lead and identify executive sponsorship.

Participate in kickoff and data-collection sessions.

Provide available environment, infrastructure, and network information.

Provide available application and business-unit ownership information.

Provide compliance and data-security requirements where applicable.

Provide information regarding existing firewall and security controls.

Identify operational stakeholders and support responsibilities.

Participate in roadmap review sessions.

Review provided documentation and strategic recommendations.

Provide feedback required to finalize the roadmap.

Out of Scope/Limitations: Scope Limitations

Provides one customer-specific High-Level Design and Roadmap Document.

The document is a high-level roadmap intended to guide the program and does not constitute a detailed design.

Recommendations are based on information available and provided during the engagement.

Application-tiering recommendations depend on high-value application information provided by the customer.

Architecture guidance is intended for strategic planning purposes.

This engagement is advisory and planning focused.

Out of Scope/Limitations: Excluded Scope

Platform deployment VEN installation or onboarding

SSO configuration

Logging or SIEM integration

Custom label-schema design

Label creation

Discovery analysis

Detailed network analysis

Traffic-flow analysis

Detailed application dependency mapping IP List creation

Unmanaged Workload creation

Core-services policy creation

Ransomware policy creation

Ringfencing policy creation

Umwelttrennung

Custom policy design

Policy implementation

Policy provisioning

Policy enforcement

Detailed or low-level design services

Compliance audits, certification, or attestation

Custom development, scripting, or integration work

Third-party system configuration

Ongoing operational support

Third-party system configuration

Expected Timeline

The delivery schedule will be established at project initiation based on:

  • Package size
  • Infrastructure complexity
  • Number of environments
  • Application portfolio complexity
  • Compliance requirements
  • Stakeholder availability
  • Customer review cycles

Delays in stakeholder participation, environment data availability, or review cycles may affect the delivery 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