Application Ringfencing

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

INTRODUCCIÓN

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

Overview

Application Ringfencing implements application-focused segmentation policy that restricts communications to only those dependencies required for an application to operate. The package represents the customer's entry into the Segmentation phase of the Illumio journey, following the visibility and containment outcomes established by earlier packages.

For each in-scope application, Illumio Professional Services analyzes observed inbound and outbound communications, validates required dependencies with application owners through an attestation process, and develops segmentation policy reflecting the approved communication requirements. By reducing unnecessary communication paths, customers improve security posture, limit lateral movement opportunities, and establish a repeatable methodology for securing additional applications.

The engagement is delivered as a repeatable motion performed for up to five applications, concluding with a segmentation reference guide and as-built policy record that document the methodology, governance model, and change-management path the customer can follow to continue ringfencing additional applications independently.

The intended outcome is implemented draft ringfencing policy for the approved applications and a documented, repeatable segmentation methodology the customer can apply across the remaining application portfolio.

Illumio Part Names covered by this Service Description are:

  • IL-SVCS-PEOPT-RING-FENC-S
  • IL-SVCS-PEOPT-RING-FENC-M
  • IL-SVCS-PEOPT-RING-FENC-L
  • IL-SVCS-PEOPT-RING-FENC-XL

Who should engage?

This service is intended for customers that have completed foundational visibility, labeling, discovery, and core-services policy work and are ready to implement application-specific segmentation controls.

Recommended participants include:

  • Security architects
  • Security engineers
  • Illumio administrators
  • Application owners
  • Application support teams
  • Infrastructure teams
  • Cloud operations teams
  • Platform administrators
  • Enterprise architecture teams
  • Change-control stakeholders

Application-owner participation is especially important because flow analysis identifies observed communications but application stakeholders must validate which communications are business-required before policy implementation occurs.

Prerequisites

Package Dependencies  

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

Technical and Data Readiness

  • Operational Illumio platform
  • Visibility data available for the in-scope applications
  • Application labels established for the approved in-scope applications
  • Required IP Lists and Unmanaged Workloads created
  • Core-services policy framework established
  • Defined application boundaries
  • Appropriate application-owner participation  

Customer Readiness  

  • Designated project sponsor
  • Technical point of contact
  • Application owners identified for in-scope applications
  • Available application-support teams
  • Approval authority for policy implementation
  • Defined change-management process for future provisioning and enforcement

Covered Services

Application Analysis (up to 5 applications)

  • Review observed inbound communications for each in-scope application.
  • Review observed outbound communications for each in-scope application.
  • Identify application dependencies and supporting infrastructure relationships.
  • Validate application boundaries and workload membership.
  • Identify communications requiring additional customer classification.
  • Document segmentation considerations specific to each application.

Customer Outcome

Customer receives a documented view of each in-scope application's communication profile and the dependencies that will shape its segmentation policy.

Application Attestation (up to 5 applications)

  • Prepare application communication findings for application-owner review.
  • Conduct attestation with application owners to validate required communications.
  • Validate business requirements and expected dependencies.
  • Review and document proposed exceptions.
  • Record approved communication requirements used to guide policy development.

Customer Outcome

Customer application owners formally validate required communications, providing an approved basis for segmentation policy and reducing the risk of operational impact.

Ringfencing Policy Development and Implementation (up to 5 applications)

  • Develop ringfencing policy architecture for each approved application.
  • Define permitted and restricted communications based on attested requirements.
  • Create ringfencing policy in draft mode within the PCE.
  • Organize policy hierarchy, rule structure, and associated policy objects.
  • Document policy-design decisions and approved exceptions.
  • Produce application-specific policy documentation for each in-scope application.

Customer Outcome

Customer receives implemented draft segmentation policy for up to five applications, aligned to attested communication requirements and ready for customer-led review and provisioning.

Segmentation Methodology and Operationalization Handoff

  • Document the ringfencing methodology used during the engagement, including analysis, attestation, policy development, and policy implementation.
  • Provide a segmentation reference guide describing application onboarding, dependency validation, and policy-development practices.
  • Document the recommended draft-to-provision workflow, including validation steps and change-management considerations.
  • Document enforcement-planning considerations and exception-management guidance.
  • Provide an as-built policy record covering implemented applications, policy hierarchy, rule organization, associated objects, and approved exceptions.
  • Document future application-onboarding guidance, operational ownership recommendations, and policy-maintenance practices.
  • Review the methodology, reference guide, and as-built record with customer stakeholders.

Customer Outcome

Customer receives a documented, repeatable segmentation methodology, change-management guidance, and an as-built policy record enabling continued ringfencing of additional applications after Professional Services disengagement.

Assumptions

Discovery findings accurately reflect application communications for the in-scope applications.

Required application labels exist for the approved in-scope applications.

Application owners are available to participate in attestation activities.

Core-services policy has been established prior to engagement start.

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

Application architecture remains materially stable during delivery.

Required application dependencies can be identified from available traffic data and stakeholder input.

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

Customer will continue expanding application segmentation after project completion.

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

Customer Requirements

The customer will:  

Assign a project manager or primary point of contact.

Identify up to five in-scope applications.

Provide primary application-owner contacts for each in-scope application.

Validate application communication requirements during attestation activities.

Review and approve proposed segmentation controls and exceptions.

Provide access to Illumio administrators and required platform access.

Participate in dependency-validation and policy-review activities.

Perform customer-side change approvals required for policy work.

Review provided documentation and reference material.

Perform provisioning, validation, and enforcement activities through the customer's change-management process.

Maintain and expand application policies after engagement completion.

Out of Scope/Limitations: Scope Limitations

Limited to five (5) applications per package purchase.

Requires application labels and Discovery findings for the approved in-scope applications.

Policy is created in draft mode only.

Results depend on available traffic visibility and application-owner participation.

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

Additional applications require additional package purchases or separately scoped engagements.

The package establishes a repeatable segmentation methodology rather than environment-wide segmentation.

Future application onboarding remains a customer responsibility after delivery.

Out of Scope/Limitations: Excluded Scope

Policy provisioning

Enforcement-mode transitions

Enforcement validation

Production cutover activities

Customer change-management execution

Ringfencing of applications beyond the package limit

Enterprise-wide microsegmentation

Separación de ambientes

Intra-application role-to-role or host-to-host segmentation

Core-services policy development

Discovery of applications outside the approved package scope

Remediation of customer metadata or workload labels

Elimination of all policy exceptions

Unlimited exception-management cycles

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

Custom automation, scripting, or integration development

Threat hunting Incident response

Forensic analysis

Continuous policy management or tuning

Ongoing operational support after package completion

Expected Timeline

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

  • Purchased package quantity
  • Number of in-scope applications
  • Application complexity
  • Dependency volume
  • Stakeholder availability
  • Customer review cycles
  • Policy-validation requirements.

Delays in application-owner validation, change approvals, or dependency confirmation may impact 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