INTRODUCCIÓN
This service description document (“Service Description”) outlines the Illumio Labeling Services (“Services”). Illumio will provide Services on the Customer’s existing security infrastructure to Illumio’s software offerings (collectively "Products").
Overview
The Labeling package establishes the customer’s metadata and workload-classification strategy that will be used to organize assets, support visibility, enable reporting, and prepare the environment for future segmentation policy. Effective labels provide the business and technical context required to understand application communications and build scalable segmentation policy over time.
Illumio Professional Services works with customer stakeholders to design a customer-specific labeling model, identify available metadata sources, define naming and governance standards, and establish a repeatable approach for assigning and maintaining labels. The engagement focuses on creating a sustainable label architecture rather than attempting to permanently classify every workload in the environment.
The resulting label schema becomes the foundation for Discovery, Basic Policy, Ringfencing, Environmental Separation, and future segmentation activities. As network visibility improves and policy development progresses, label definitions and assignments may continue to evolve and mature beyond the initial engagement.
The intended outcome is a documented label strategy, an implemented foundational label structure, and customer enablement to continue label administration independently after Professional Services disengagement.
Illumio Part Names covered by this Service Description are:
- IL-SVCS-DEPF-LABEL-S
- IL-SVCS-DEPF-LABEL-M
- IL-SVCS-DEPF-LABEL-L
- IL-SVCS-DEPF-LABEL-XL
Who should engage?
Recommended stakeholders include:
- Security architects
- Security engineers
- Illumio platform administrators
- Infrastructure administrators
- CMDB or asset-management owners
- Enterprise architecture teams
- Cloud operations teams
- Application owners Service owners
- Platform engineering teams
Labeling is most successful when both technical administrators and business/application stakeholders participate, as technical metadata alone is often insufficient to determine application ownership and business context.
Prerequisites
Package Dependencies
- Platform Foundation Deployment
Strongly Recommended Packages
- Segmentation Strategy & Roadmap
Optional Supporting Packages
- None
Technical Readiness
- Operational Illumio platform
- Workloads visible within the platform
- Access to available metadata sources
- Available asset inventory or CMDB data
- Existing naming standards, where available
Customer Readiness
- Project sponsor assigned
- Technical point of contact assigned
- Application-owner participation available
- Infrastructure stakeholders available
- Access to inventory, metadata, and workload information approved
Covered Services
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.
Assumptions
Customer metadata is reasonably accurate.
Application owners are available when required.
Customer stakeholders can validate business context and ownership information.
Workloads are visible within the Illumio platform.
Customer responds to information requests within agreed project timelines.
Environment remains materially stable during delivery.
Customer will maintain and evolve labels after handoff.
Future policy-development activities may require adjustments to the label schema.
Customer Requirements
The customer will:
Assign a project manager or primary point of contact.
Provide workload inventory information.
Provide available CMDB or metadata sources.
Provide access to appropriate stakeholders.
Participate in label-validation activities.
Review and approve naming standards.
Review and approve label hierarchy design.
Review documentation deliverables.
Maintain labels after engagement completion.
Own future label-governance activities.
Out of Scope/Limitations: Scope Limitations
Includes one customer-specific label schema design.
Includes foundational label creation and configuration.
Includes guidance for ongoing administration and expansion.
Results depend on the quality and completeness of customer metadata.
Label effectiveness depends on stakeholder participation and validation.
Future Discovery and policy-development activities may require refinement of label assignments.
The package establishes a framework for label management rather than complete classification of every workload.
Label strategy and operational guidance are based on information available during the engagement.
Out of Scope/Limitations: Excluded Scope
Complete manual labeling of every workload.
Classification of every application and role within the environment.
Ongoing label administration.
Comprehensive CMDB remediation.
Asset-inventory cleanup projects.
Custom integration development.
Third-party system configuration.
Policy creation. Policy provisioning.
Policy enforcement.
Discovery analysis.
Application Ringfencing.
Environmental Separation.
Continuous operational services.
Long-term governance ownership after project completion.
Expected Timeline
The delivery schedule will be established at project initiation based on:
- Metadata quality
- Number of applications
- Number of workloads
- Labeling complexity
- Stakeholder availability
- Customer review cycles.
Delays in metadata availability, stakeholder participation, ownership validation, or customer approvals 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
