Containment Bundle

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

소개

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

Overview

The Containment Bundle delivers a complete path from program strategy through operational containment controls in a single engagement with a single SKU. It combines strategic planning, platform deployment, workload classification, network traffic analysis, and the customer's first operational segmentation policies.

The bundle begins with a documented segmentation strategy and roadmap that aligns business objectives, environment realities, and compliance requirements into a recommended order of operations. It then establishes the Illumio platform, a scalable labeling framework, and a documented understanding of network communications. The engagement concludes by implementing a core-services policy framework covering shared infrastructure and administrative services, followed by containment controls that restrict high-risk protocols commonly used for lateral movement.

Because containment rules can interact with core-service communications, the final stage is delivered iteratively — core-services policy is revisited as risky protocols are restricted, ensuring required administrative and infrastructure traffic is preserved.

The intended outcome is an operational Illumio deployment with a documented labeling strategy, a documented understanding of network communications, an implemented core-services policy framework, and implemented ransomware containment controls that reduce lateral-movement risk.

Illumio Part Names covered by this Service Description are:

  • IL-SVCS-BUN-CONT-S
  • IL-SVCS-BUN-CONT-M
  • IL-SVCS-BUN-CONT-L
  • IL-SVCS-BUN-CONT-XL

Who should engage?

Recommended stakeholders across the bundle include:

  • Executive sponsors and security leadership
  • Security architects and security engineers
  • Illumio platform administrators Infrastructure and systems administrators
  • Active Directory administrators
  • Network architects and network engineers
  • Cloud architects and cloud operations teams
  • Identity and access management teams
  • SIEM and logging teams
  • Software distribution and endpoint management teams
  • Vulnerability-management teams
  • Security operations teams
  • CMDB and asset-management owners
  • Application owners and service owners
  • Compliance stakeholders
  • Enterprise architecture teams
  • Change-management stakeholders
  • Program and project managers
  • Customer Success representatives

Participation from both business and technical stakeholders is required throughout. Strategic planning depends on business objectives and compliance context, while labeling, discovery, and policy development depend on application ownership and validation of required communications.

Prerequisites

Illumio Package Prerequisites  

Package Dependencies

  • None — this bundle includes all prerequisite packages.  

Delivery Sequence

  • Segmentation Strategy & Roadmap → Platform Foundation Deployment → Labeling → Discovery → Basic Policy – Core Services + Ransomware  

Technical Readiness

  • Illumio licensing available
  • Available infrastructure, network, and security architecture information
  • Workload and asset inventory available
  • Available application inventory where known
  • Supported operating systems identified
  • Deployment tooling identified
  • Identity provider available for SSO integration
  • SIEM destination identified
  • Available metadata sources, including CMDB, cloud tags, and existing naming standards  

Customer Readiness

  • Executive sponsor identified
  • Project lead and technical point of contact assigned
  • Deployment owners and operating-system owners identified
  • Core-service owners identified
  • Application owners identified Network, security, and compliance stakeholders available
  • Change-management process documented Required administrative access approved

Covered Services

Segmentation Strategy & Roadmap

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.

Platform Foundation Deployment

Platform Operational Configuration

  • Configure customer access to the Illumio platform.
  • Configure and validate Single Sign-On (SSO).
  • Configure logging integration for supported log forwarding methods.
  • Validate logging delivery into the customer SIEM.
  • Review platform administrative access requirements.

Deployment Planning

  • Review workload inventory.
  • Categorize workloads by operating system.
  • Review customer deployment methodology.
  • Identify deployment ownership and responsibilities.
  • Review automation and software-distribution approaches.
  • Review onboarding expectations and support responsibilities. API enablement

VEN Installation and Validation

  • Facilitate installation of up to ten (10) sample VENs per supported operating system type.
  • Validate successful workload pairing.
  • Validate deployment methodology.
  • Review installation outcomes and onboarding process.

Customer Outcome:

Customer administrators can access and operate the platform, logging is integrated into the customer's monitoring ecosystem, deployment methods are validated, and compatibility findings have been documented for future onboarding activities.

Compatibility Assessment

  • Execute VEN compatibility reporting.
  • Review existing host firewall configurations.
  • Identify operating-system conflicts or compatibility issues.
  • Identify workload-specific remediation requirements.
  • Review findings with customer stakeholders.
  • Document workloads requiring corrective actions before transitioning to Visibility Mode.

End of Engagement Summary and Handoff

  • Review customer change-management process.
  • Identify risks associated with future workload onboarding and Visibility Mode transitions.
  • Develop onboarding documentation.
  • Document deployment methodology.
  • Document operational recommendations.
  • Document next-step guidance for future onboarding activities.

Labeling

Labeling Strategy Development

  • Review customer segmentation goals and desired outcomes.
  • Review available workload metadata.
  • Assess existing naming conventions and classification methods.
  • Define a scalable label hierarchy.
  • Define customer-specific classification requirements.
  • Define naming standards and label conventions.
  • Review Illumio labeling best practices.
  • Establish standards for capitalization, abbreviations, prefixes, naming consistency, and searchability.

Label Schema Design and Governance

  • Define Role, Application, Environment, and Location strategy.
  • Define approved customer-specific label dimensions where appropriate.
  • Document label definitions and ownership.
  • Establish governance standards for label creation, maintenance, modification, and retirement.
  • Define future label-expansion guidance.
  • Establish recommendations for long-term administration and operational ownership.

Customer Outcome

Customer receives a documented label schema and governance model aligned to operational, reporting, and future segmentation requirements.

Metadata Analysis and Classification

  • Analyze available workload information.
  • Review hostname patterns.
  • Review available application metadata.
  • Review infrastructure metadata.
  • Review cloud metadata and tagging information.
  • Identify customer-specific identifiers that should be incorporated into the labeling strategy.
  • Identify metadata gaps that may impact future policy development.

Customer Outcome

Customer gains a structured understanding of the metadata required to support ongoing workload classification and future segmentation activities.

Label Operationalization

  • Create agreed foundational label structures.
  • Configure initial labels required to support the agreed scope.
  • Review bulk-label assignment methods.
  • Demonstrate API-enabled label-management capabilities.
  • Demonstrate Workloader usage when permitted and applicable.
  • Review techniques for maintaining labels at scale.
  • Document recommended operational processes for future label management.

End-of-Engagement Summary and Handoff

  • Provide a customer-specific label schema reference.
  • Provide governance recommendations.
  • Provide operational administration guidance.
  • Document recommended future enhancements.
  • Document ongoing ownership expectations.
  • Provide best-effort guidance for future label refinement as Discovery and policy development progress.

Customer Outcome

Customer has implemented foundational labels and possesses the documented processes, governance standards, and operational knowledge necessary to continue label administration and evolution after Professional Services disengagement.

발견

Discovery Planning

  • Review customer segmentation objectives.
  • Confirm Discovery scope, priorities, and in-scope population.
  • Review available metadata, inventory, and network information.
  • Establish traffic-analysis priorities and review methodology.
  • Confirm the approach for handling unidentified or disputed systems.

Customer Outcome

Customer and Illumio share an agreed Discovery scope, analysis method, and set of priorities aligned to the customer's segmentation objectives.

Traffic Analysis

  • Analyze inbound and outbound communications to/from in-scope workloads.
  • Review communication patterns between applications.
  • Identify branch-office communications.
  • Identify cloud infrastructure communications.
  • Identify partner connectivity.
  • Identify internet-facing communications.
  • Review multicast and broadcast activity.
  • Identify scanning, management, and network-discovery traffic patterns.
  • Document legacy protocols, shared-services dependencies, and other network-complexity observations.
  • Document communications requiring additional customer validation.

Customer Outcome

Customer gains a documented understanding of inbound and outbound communication patterns, external dependencies, and network complexity that will influence future segmentation policy design.

Policy Readiness Analysis

  • Identify systems and networks requiring representation within the PCE.
  • Identify candidate IP Lists. Identify candidate Unmanaged Workloads.
  • Review application-boundary observations. Identify labeling, metadata, and ownership gaps affecting policy readiness.
  • Document policy-design considerations for future segmentation activities.

Customer Outcome

Customer understands what must exist within the PCE, and what remains unresolved, before segmentation policy can be developed.

Policy Object Creation and Operationalization

  • Define object naming standards, description standards, and documentation conventions.
  • Create approved IP Lists.
  • Create approved Unmanaged Workloads.
  • Apply agreed naming, description, and documentation standards to created objects.
  • Provide data templates for future object creation.
  • Demonstrate manual and API-enabled object-management methods.
  • Demonstrate supported bulk object-management techniques where applicable.
  • Document object-governance recommendations.
  • Document candidate objects not created due to missing information, customer decisions, or package limits.

Customer Outcome

Customer receives the policy objects required to support future policy development, the standards and templates used to create them, and the operational knowledge to continue object creation independently.

Discovery Findings and Handoff

  • Demonstrate the traffic-analysis and data-extraction methods used during the engagement.
  • Provide a documented summary of Discovery findings, including traffic observations, network-complexity findings, and policy-readiness findings.
  • Provide a summary of created policy objects and applicable standards.
  • Document unresolved items, ownership questions, and recommended customer follow-up.
  • Document recommended next-step activities and readiness considerations for Basic Policy, Ringfencing, and future segmentation work.
  • Review findings and recommendations with customer stakeholders.

Customer Outcome

Customer receives a documented Discovery record, governance standards, and a recommended path into future policy-development activities that can be executed independently.

Basic Policy - Core Services + Ransomware containment

Core Services Analysis and Design

  • Review Discovery findings and available traffic data.
  • Identify shared infrastructure and administrative services in scope.
  • Validate core-service communication requirements with stakeholders.
  • Review operational dependencies and consumption patterns.
  • Define reusable policy structures and policy hierarchy.
  • Define the customized architectural configuration structure for core-services policy.
  • Identify required exceptions and document their rationale.

Customer Outcome

Customer receives a validated architectural model for shared-services policy that can be reused and extended as additional services are onboarded.

Core Services Policy Implementation and Handoff

  • Implement core-services policy for up to ten (10) approved core-service applications.
  • Create and organize required policy objects and rule structures.
  • Validate policy against observed and approved communications.
  • Document implemented policy structure and associated objects.
  • Provide a reference guide describing core-services policy structure, construction methodology, and maintenance practices.
  • Document exception-management guidance and future core-services onboarding guidance.
  • Review implemented policy and documentation with customer stakeholders.

Customer Outcome

Customer has an implemented and documented core-services policy framework and the reference material required to continue expanding and maintaining it independently.

Ransomware Containment Design and Implementation

  • Review the standard high-risk protocol list and customize where requested.
  • Design the deny-rule framework used to restrict high-risk protocols.
  • Implement containment controls for up to ten (10) approved risky protocols, commonly beginning with RDP and SSH and typically including protocols such as Telnet, FTP, and SMB.
  • Validate the impact of containment rules on core-service communications.
  • Iteratively revisit and adjust core-services policy where containment rules interrupt required communications.
  • Create and document approved exceptions and their rationale.

Customer Outcome

Customer receives implemented containment controls that reduce lateral-movement risk while preserving required core-service communications.

Ransomware Containment Documentation and Handoff

  • Document blocked protocols, approved exceptions, and exception rationale.
  • Add ransomware-containment content to the customer policy reference documentation.
  • Provide an as-built record of implemented policy, rule organization, and associated objects.
  • Document ransomware-policy administration and future protocol-evaluation guidance.
  • Document recommended containment-expansion approach and operational ownership.
  • Review implemented controls and documentation with customer stakeholders.

Customer Outcome

Customer has a documented containment framework, a record of blocked protocols and exceptions, and the operational guidance required to maintain and expand ransomware controls after Professional Services disengagement.

Bundle Customer Outcome

At the conclusion of the Containment Bundle, the customer has a documented segmentation strategy and roadmap, an operational Illumio platform integrated with its identity and monitoring systems, a validated and repeatable workload onboarding method, a documented and implemented labeling framework, a documented analysis of network communications and complexity, an implemented core-services policy framework, and implemented ransomware containment controls — together with the operational knowledge required to maintain and expand those frameworks and progress into application segmentation.

Assumptions

Customer provides accurate environment, network, application, and architecture information.

Customer provides required administrative access and platform access throughout the engagement.

Customer provides accurate workload inventory, asset inventory, and metadata information.

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

Pre-sales intake information is available where applicable.

Customer identifies deployment ownership and operating-system ownership responsibilities.

Supported operating systems and deployment architectures are used.

Identity-provider integration requirements are known and the SIEM destination is available.

Core-service owners, application owners, and technical stakeholders are available when required.

Customer stakeholders can validate ownership, application alignment, business context, and required communications.

Customer responds to information, review, and approval requests within agreed project timelines.

The in-scope environment remains materially stable during delivery.

Observed traffic represents a point-in-time view of the environment; absence of observed traffic does not establish that a dependency does not exist.

Infrequent, seasonal, failover, or event-driven communications may not appear in the reviewed data.

Labels and policy objects will continue to evolve as discovery and policy development progress.

Customer performs provisioning and enforcement activities through its own change-management process.

Policy reflects communications and business requirements known at the time of delivery.

Customer will assume responsibility for continued onboarding, label administration, object maintenance, and policy expansion after handoff.

Customer Requirements

The customer will:  

Assign a project lead, executive sponsor, and primary technical point of contact for the bundle engagement.

Participate in kickoff, data-collection, and roadmap review sessions.

Provide available environment, infrastructure, network, and security architecture information.

Provide compliance and data-security requirements where applicable.

Provide administrative access required for platform configuration, onboarding, analysis, and policy work.

Provide workload inventory, asset inventory, network inventory, and available metadata sources.

Identify deployment owners, operating-system owners, core-service owners, and application owners.

Provide access to identity, logging, network, security, compliance, and application stakeholders.

Approve the in-scope workload, application, and Discovery population.

Identify in-scope core-service applications.

Review and approve the high-risk protocol list.

Participate in deployment validation, label validation, findings review, and policy-validation activities.

Review compatibility findings and perform any required remediation.

Review and approve label hierarchy design and naming standards.

Review candidate policy objects and approve names, values, ranges, and descriptions prior to creation.

Identify the business owner and purpose of communications that cannot be determined from technical data.

Review and approve required policy exceptions.

Investigate potential scanning or anomalous traffic through the customer's established security processes.

Perform customer-side change-control, approval, provisioning, and enforcement activities.

Own ongoing onboarding, label administration, policy-object maintenance, policy administration, and expansion after project completion.

Out of Scope/Limitations: Scope Limitations

The bundle provides one customer-specific High-Level Design and Roadmap Document; it is a high-level roadmap intended to guide the program and does not constitute a detailed or low-level design.

Strategic recommendations are based on information available and provided during the engagement.

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

Sample VEN installation is limited to ten (10) workloads per supported operating-system type; the engagement validates onboarding methodology rather than onboarding the entire workload estate.

Compatibility assessment reflects the workloads reviewed during the engagement.

Logging integration is limited to supported integration methods.

The bundle includes one customer-specific label schema design.

Labeling establishes a framework and foundational label structure rather than complete classification of every workload.

Label effectiveness depends on the quality and completeness of customer metadata and stakeholder participation.

Discovery includes creation of up to sixty (60) policy objects, comprising IP Lists and Unmanaged Workloads, with a recommended planning assumption of approximately thirty (30) of each type.

Discovery analysis prioritizes policy-readiness outcomes rather than exhaustive review of every observed flow.

Discovery reflects traffic, telemetry, labels, metadata, and inventories available during the engagement and represents a point-in-time view.

Observed traffic does not independently establish the business purpose or legitimacy of a connection.

Potential scanning or anomalous patterns are documented as observations and are not a confirmed threat determination.  

Core-services policy is limited to ten (10) approved core-service applications.

Ransomware containment is limited to ten (10) approved risky protocols.

Policy reflects the environment state and available data during delivery, and policy effectiveness depends on the completeness of Discovery findings and labeling.

Exception handling is limited to exceptions identified and approved during the engagement.

Limited application-owner, core-service-owner, or network-team participation may reduce the ability to classify systems, dependencies, and required communications.

Out of Scope/Limitations: Excluded Scope

Detailed or low-level design services

Compliance audits, certification, or attestation

Movement of workloads into Visibility Mode

Deployment of the entire workload estate or future onboarding waves

Remediation of customer operating-system issues or existing host firewall conflicts

Complete manual labeling of every workload, application, or role

Comprehensive CMDB remediation or asset-inventory cleanup

Analysis of every observed communication flow or identification of every application dependency

Full-environment network mapping

Creation of policy objects beyond the bundle limits

Resolution of all unknown or unowned assets

Policy development beyond the approved core-service and protocol limits

Unlimited exception creation

Full-environment segmentation or enforcement of all workloads

Policy provisioning, testing, or enforcement

Changes to VEN enforcement modes

Customer change-management execution

Application Ringfencing

환경 분리  

Tier-to-tier segmentation or microsegmentation

Custom policy design beyond the approved bundle scope

Vulnerability assessment, penetration testing, threat hunting, incident response, or forensic analysis

Formal network-security audit or confirmation of malicious activity

Third-party system, network device, security tool, or cloud platform configuration

Custom automation, scripting, integration, or analytics development

Continuous monitoring or Discovery services after the analysis period

Continuous policy management or tuning

Ongoing operational support, administration, or governance after package completion

Expected Timeline

The Containment Bundle is delivered as a sequenced program rather than a set of independent engagements. The delivery schedule will be established at project initiation based on:

  • Purchased bundle size
  • Infrastructure complexity, number of environments, and application portfolio complexity
  • Compliance requirements
  • Number of operating systems and deployment complexity
  • Identity-provider and logging integration complexity
  • Metadata quality and number of applications
  • Traffic volume and number of observed dependencies
  • Number of core-service applications and risky protocols selected
  • Stakeholder availability and customer review and approval cycles.

Packages are delivered in sequence, with Discovery activities potentially beginning before final label refinement is complete, and core-services policy revisited iteratively as containment controls are implemented. Delays in stakeholder participation, access provisioning, integration configuration, metadata availability, dependency validation, exception decisions, or change approvals may affect the overall program 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