소개
This service description document (“Service Description”) outlines the Illumio Visibility Bundle Services (“Services”). Illumio will provide Services on the Customer’s existing security infrastructure to Illumio’s software offerings (collectively "Products").
Overview
The Visibility Bundle delivers the foundational Illumio capabilities required to analyze and understand communications across the customer environment. It combines platform deployment, workload classification, and network traffic analysis into a single engagement with a single SKU.
The bundle establishes operational access to the Illumio platform, integrates platform events into the customer's monitoring ecosystem, validates workload onboarding methodology, creates a scalable labeling framework, and analyzes inbound and outbound communications to determine what must exist within the platform before segmentation policy can be developed.
The intended outcome is an operational Illumio deployment, a documented labeling strategy, a documented understanding of network communications, and the policy objects and operational knowledge required to progress into containment and segmentation activities.
Illumio Part Names covered by this Service Description are:
- IL-SVCS-BUN-VIS-S
- IL-SVCS-BUN-VIS-M
- IL-SVCS-BUN-VIS-L
- IL-SVCS-BUN-VIS-XL
Who should engage?
Recommended stakeholders across the bundle include:
- Security architects and security engineers
- Illumio platform administrators Infrastructure and systems administrators
- Network architects and network engineers
- Cloud operations teams Identity and access management teams
- SIEM and logging teams Software distribution and endpoint management teams
- CMDB and asset-management owners
- Application owners and service owners
- Enterprise architecture teams
- Change-management stakeholders
- Customer project managers
Application-owner and business-stakeholder participation is important throughout. Technical metadata and traffic data identify what exists and what communicates, but business stakeholders are required to validate ownership, application alignment, and business purpose.
Prerequisites
Illumio Package Prerequisites
Package Dependencies
- None — this bundle includes all prerequisite packages.
Delivery Sequence
- Platform Foundation Deployment → Labeling → Discovery
Technical Readiness
- Illumio licensing available
- Supported operating systems identified
- Deployment tooling identified
- Connectivity requirements identified
- Identity provider available for SSO integration
- SIEM destination identified Workload and asset inventory available
- Available metadata sources, including CMDB, cloud tags, and existing naming standards
- Available network inventory where applicable
Customer Readiness
- Project sponsor assigned
- Technical point of contact assigned
- Deployment owners and operating-system owners identified
- Application owners identified
- Network and security stakeholders available
- Change-management process documented
- Required administrative access approved
Covered Services
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.
Bundle Customer Outcome
At the conclusion of the Visibility Bundle, the customer has 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, and the policy objects and operational knowledge required to begin containment and segmentation policy development.
Assumptions
Customer provides required administrative access and platform access throughout the engagement.
Customer provides accurate workload inventory, asset inventory, and metadata information.
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.
Application owners and technical stakeholders are available when required.
Customer stakeholders can validate ownership, application alignment, and business context.
Customer responds to information requests within agreed project timelines.
Customer substantially completes VEN installation before proceeding to Labeling and Discovery phases 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 will assume responsibility for continued onboarding, label administration, and object maintenance after handoff.
Customer Requirements
The customer will:
Assign a project manager or primary point of contact for the bundle engagement.
Provide administrative access required for platform configuration, onboarding, and analysis.
Provide workload inventory, asset inventory, network inventory, and available metadata sources.
Identify deployment owners, operating-system owners, and application owners.
Provide access to identity, logging, network, security, and application stakeholders.
Approve the in-scope workload, application, and Discovery population.
Participate in deployment validation, label validation, and findings review 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.
Investigate potential scanning or anomalous traffic through the customer's established security processes.
Perform customer-side change-control and approval activities.
Own ongoing onboarding, label administration, policy-object maintenance, and operational activities after project completion.
Out of Scope/Limitations: Scope Limitations
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.
Limited application-owner or network-team participation may reduce the ability to classify systems and dependencies.
Out of Scope/Limitations: Excluded Scope
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
Core-services policy creation
Ransomware containment policy creation
Segmentation rule or ruleset creation
Policy provisioning, testing, or enforcement
Changes to VEN enforcement modes
Application Ringfencing
환경 분리
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
Ongoing operational support, administration, or governance after package completion
Expected Timeline
The Visibility 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
- Number of operating systems and deployment complexity
- Identity-provider and logging integration complexity
- Metadata quality and number of applications
- Environment complexity and traffic volume
- Number of observed dependencies
- Stakeholder availability and customer review cycles.
Packages are delivered in sequence, with Discovery activities potentially beginning before final label refinement is complete. Delays in access provisioning, integration configuration, metadata availability, stakeholder participation, validation, or 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
