Labeling

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.

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

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.

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.

Talk to our Sales team to learn more about Services.

Explore our Professional Services at illumio.com/services/professional-services