Descubrimiento

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

INTRODUCCIÓN

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

Overview

The Discovery package analyzes observed network communications to determine what policy objects, network representations, and environmental context must exist within Illumio before policy can be safely and effectively developed.

The engagement focuses on reviewing inbound and outbound communications observed within the Illumio platform, identifying communication patterns that are relevant to future segmentation efforts, and documenting infrastructure elements that are not yet represented within the PCE. Discovery provides customers with a structured understanding of application communications, external dependencies, network complexity, cloud connectivity, branch-office communications, partner communications, internet exposure, and other traffic patterns that influence future policy design.

As part of the engagement, Illumio Professional Services teaches the customer the methodologies used to analyze traffic, identify trends, validate communication patterns, and determine required policy objects. The service includes creation of policy objects required to support future policy engineering activities and provides standards, governance recommendations, and operational guidance for ongoing object creation after the engagement concludes.

Discovery is intended to establish policy readiness. It does not attempt to analyze every communication path or completely model the customer environment. Instead, it provides a bounded analysis, creates priority policy objects, and delivers a documented path forward into Basic Policy, Ringfencing, Environmental Separation, and future segmentation services.

Illumio Part Names covered by this Service Description are:

  • IL-SVCS-PEOPT-DISC-S
  • IL-SVCS-PEOPT-DISC-M
  • IL-SVCS-PEOPT-DISC-L
  • IL-SVCS-PEOPT-DISC-XL

Who should engage?

Discovery is designed for customers that have completed foundational deployment and labeling activities and need to prepare their environment for policy development.

Recommended participants include:

  • Illumio administrators
  • Security architects
  • Security engineers
  • Network architects
  • Network engineers
  • Infrastructure administrators
  • Cloud operations teams
  • Application owners
  • CMDB and asset-management owners
  • Security operations personnel
  • Enterprise architecture teams
  • Customer project managers

Customers should identify stakeholders capable of validating network communications, application ownership, infrastructure dependencies, and business purpose where required.

Prerequisites

Package Dependencies

  • Platform Foundation Deployment
  • Labeling  

Strongly Recommended Packages

  • Segmentation Strategy & Roadmap  

Technical Readiness

  • Operational Illumio platform
  • VEN-installed workloads paired and reporting
  • Visibility data available
  • Initial labeling completed
  • Asset inventory available
  • Network inventory available where applicable
  • Access to traffic data and exports
  • Access to object-management methods within Illumio  

Customer Readiness

  • Designated project sponsor
  • Primary technical contact
  • Network stakeholders available
  • Security stakeholders available
  • Application stakeholders available
  • Agreed Discovery scope
  • Agreed workload population

Covered Services

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.

Assumptions

Visibility data is available for the agreed in-scope population.

VEN-installed workloads are paired and reporting traffic.

Labels exist for the agreed in-scope workload population.

Customer metadata and inventory information are reasonably accurate.

Network, security, and application stakeholders are available when required.

Customer responds to information 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.

Customer will maintain created policy objects after handoff.

Customer will continue Discovery activities after package completion.

Customer Requirements

The customer will:  

Assign a project manager or primary technical contact.

Approve the Discovery scope and in-scope population.

Provide timely PCE access and any approved data-export access required for the engagement.

Provide workload inventory, network inventory, and available application context.

Make network, infrastructure, cloud, security, and application stakeholders available for validation.

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

Review candidate IP Lists and Unmanaged Workloads.

Approve object names, values, ranges, descriptions, and labels prior to creation.

Validate whether observed communications are expected, authorized, or required.

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

Perform customer-side change-control activities required for object creation.

Continue Discovery analysis and object creation beyond the package limits.

Own ongoing maintenance of policy objects, metadata, and related classifications after handoff.

Out of Scope/Limitations: Scope Limitations

Limited to creation of up to sixty (60) policy objects.

Objects may include IP Lists and Unmanaged Workloads based on Discovery findings.

Analysis is limited to the purchased package size and agreed in-scope environment.

Discovery reflects traffic, telemetry, labels, metadata, and inventories available during the engagement.

Analysis prioritizes policy-readiness outcomes rather than exhaustive flow review.

Object creation depends on customer validation and available information.

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

Limited application-owner or network-team participation may reduce the ability to classify systems and dependencies.

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

Findings represent a point-in-time view and may change as the environment and traffic patterns change.

Additional Discovery activities remain customer-owned after engagement completion.

Out of Scope/Limitations: Excluded Scope

Analysis of every observed communication flow

Identification of every application dependency

Full-environment network mapping

Classification of every source and destination

Creation of policy objects beyond the package limits

Resolution of all unknown or unowned assets

Remediation of customer metadata, CMDB, or asset inventories

Completion or correction of workload labels

Continuous monitoring or Discovery services after the analysis period

Segmentation rule or ruleset creation

Policy provisioning

Policy testing

Policy enforcement

Changes to VEN enforcement modes

Application Ringfencing

nvironmental Separation

Vulnerability assessment

Penetration testing

Threat hunting

Incident-response investigation

Forensic analysis

Formal network-security audit

Confirmation or attribution of malicious activity

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

Custom scripts, integrations, data pipelines, or analytics development

Ongoing operational support after package completion

Expected Timeline

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

  • Package size
  • Environment complexity
  • Traffic volume
  • Number of applications
  • Number of observed dependencies
  • Stakeholder availability
  • Customer review cycles

Delays in data availability, stakeholder participation, scope validation, or object approval may impact delivery timelines.

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