INTRODUCTION
This service description document (“Service Description”) outlines the Illumio Active Incident Segmentation Support Services (“Services”). Illumio will provide Services on the Customer’s existing security infrastructure to Illumio’s software offerings (collectively "Products").
Overview
Active Incident Segmentation Support helps organizations stop lateral movement during an active breach. It protects servers that have been confirmed healthy so compromised systems can't reinfect them.
During a breach, a critical task is keeping compromised systems from reaching systems that have been investigated and cleared. Traditional network controls are usually too slow or too coarse to change in the middle of an incident. Illumio segmentation can put workload-level boundaries in place quickly, without redesigning the network.
Illumio Professional Services is not an incident response firm. PS works alongside the IR firm the customer has contracted. The IR firm leads the investigation, forensics, and remediation, and Illumio PS provides segmentation controls to support that work.
PS helps the customer set up an environmental separation rule based on workload state. As the customer and its IR firm sort servers into impacted, cleared, or unknown, PS helps deploy VENs and apply enforcement so that cleared servers refuse traffic from compromised or unverified systems. Protection is enforced on the healthy side of the boundary, so it doesn't depend on getting an agent onto a system that may already be compromised.
PS also gives the customer a blueprint for repeating the method. The customer can then keep classifying, clearing, and protecting workloads as recovery continues, and use the same approach to protect the environment going forward.
This method is temporary by design. It is built for speed during an incident, not for long-term operation. Once the incident is resolved, it can transition into a full Illumio deployment.
This package is usually used by organizations that are new to Illumio or haven't created policy yet.
Illumio Part Names covered by this Service Description are:
- IL-SVCS-IR-INCD-SGMT-SUPP-S
- IL-SVCS-IR-INCD-SGMT-SUPP-M
- IL-SVCS-IR-INCD-SGMT-SUPP-L
- IL-SVCS-IR-INCD-SGMT-SUPP-XL
Who should engage?
This package is for organizations managing an active security incident, including organizations that don't use Illumio yet.
Recommended stakeholders include:
- Incident commander or incident response lead
- The customer's contracted incident response firm
- CISO and security leadership Security operations teams
- Infrastructure and systems administrators
- Network engineers
- Endpoint and software distribution teams
- Identity and directory service administrators
- Application owners for critical systems
- Executive and crisis management stakeholders
The customer must have an incident response firm or internal IR team engaged. That team owns the investigation and decides which workloads are impacted, cleared, or unknown.
Prerequisites
Package Dependencies
- None
Incident Readiness
- An incident response firm or internal IR team is engaged and leading the investigation
- An incident commander or single decision-maker is identified
- The customer has authority to make emergency changes to production systems
Technical Readiness
- Illumio licensing is available, including licensing issued for the incident where applicable
- Access to an Illumio PCE, or the ability to provision one quickly
- Administrative access to in-scope workloads, or a software distribution method, for VEN deployment
- Network connectivity from in-scope workloads to the PCE
- An initial list of in-scope workloads and critical systems
Customer Readiness
- A primary point of contact available throughout the engagement
- Infrastructure and security staff available to deploy VENs and approve changes
- An emergency change-approval process in place for the incident
Covered Services
Incident Engagement and Coordination
- Establish a working cadence with the customer's incident commander and IR firm.
- Confirm the in-scope environment, critical systems, and containment priorities.
- Confirm how workload state decisions will be made and communicated.
- Confirm emergency change-approval and authorization procedures.
Customer Outcome
The customer, its IR firm, and Illumio PS agree on how segmentation will be used to support the incident response.
Rapid Platform Enablement
- Set up or confirm access to the Illumio PCE.
- Set up the minimum configuration the incident requires, including a label structure for workload state.
- Define the workload state labels: impacted, cleared, and unknown.
- Identify core infrastructure services that must stay reachable, such as identity and name resolution, and the IR tooling access that must be kept.
Customer Outcome
The customer has an Illumio environment ready to support incident segmentation in the shortest practical time.
Incident Separation Rule
- Design an environmental separation rule that prevents cleared workloads from accepting traffic from impacted and unknown workloads.
- Build in approved exceptions for IR tooling, investigation access, and required core services.
- Adjust the rule and its exceptions as the IR firm's findings change.
- Document the rule, the exceptions, and the reason for each change.
Customer Outcome
The customer has a defined boundary that shields healthy servers from compromised or unverified systems and keeps the access the investigation needs.
VEN Deployment and State-Based Enforcement
- Help deploy VENs to in-scope workloads using the customer's available deployment methods, with cleared and critical systems first.
- Apply state labels to workloads as the customer and IR firm classify them.
- With customer authorization, help apply enforcement so cleared workloads refuse traffic from impacted and unknown systems.
- Update workload labels as systems move between states, such as from unknown to cleared.
- Use Illumio visibility to confirm the separation rule is working as intended.
Customer Outcome
Healthy servers are protected from reinfection as they are cleared, so the customer can return them to service with less risk.
Recovery Blueprint and Transition
- Give the customer a blueprint for repeating the classify, clear, and protect method as recovery continues.
- The blueprint covers VEN deployment, state labeling, updating the separation rule, and enforcement.
- Document the configuration at transition, including labels, the separation rule, exceptions, workload states, and enforcement state.
- Document recommendations for removing or refining incident-specific policy once the incident is resolved.
- Recommend a path from temporary incident segmentation to a full Illumio deployment, and identify the packages that support it.
- Review the blueprint and transition documentation with customer stakeholders.
Customer Outcome
The customer can keep recovering and protecting its environment independently, and has a clear path from temporary incident containment to a sustainable Illumio deployment.
Assumptions
The customer has engaged an incident response firm or internal IR team, and that team leads the investigation.
The customer and its IR firm decide which workloads are impacted, cleared, or unknown.
Illumio PS applies segmentation based on those decisions.
The customer authorizes every provisioning and enforcement change made during the incident.
The customer accepts that emergency segmentation changes during an active incident may affect application availability.
Speed takes priority over completeness.
The incident configuration is intentionally minimal and temporary.
Enforcement is applied on cleared workloads.
Protection doesn't depend on installing agents on compromised systems.
The customer provides timely access to workloads, deployment tools, and staff.
Workloads that can't run a VEN or can't reach the PCE can't be directly protected.
The applicable order defines service activation, response times, and hours of coverage.
The customer owns incident communications, regulatory notifications, and recovery decisions.
Customer Requirements
The customer will:
Engage an incident response firm or internal IR team to lead the investigation.
Identify an incident commander or single decision-maker.
Work with its IR firm to classify workloads as impacted, cleared, or unknown.
Authorize all provisioning and enforcement changes.
Provide administrative access to workloads, or to software distribution tools, for VEN deployment.
Make infrastructure, security, and network staff available throughout the engagement.
Identify critical systems and core services that must stay reachable.
Identify the access IR tooling requires.
Accept responsibility for business impact caused by emergency changes.
Use the recovery blueprint to continue recovery after the engagement.
Own incident communications, notifications, and recovery decisions.
Out of Scope/Limitations: Scope Limitations
Covers one incident.
Segmentation is limited to workloads with an installed VEN and connectivity to the PCE.
The incident configuration is temporary and intended for emergency containment, not long-term operation.
Enforcement is applied only with customer authorization and follows workload state decisions made by the customer and its IR firm.
Out of Scope/Limitations: Excluded Scope
Incident response leadership or incident command
Forensic investigation, malware analysis, or root-cause analysis
Deciding which workloads are compromised or cleared
Threat hunting or indicator-of-compromise analysis
Attribution of attacker activity
Malware removal, system rebuild, restoration, or recovery
Ransom negotiation or payment support
Legal, regulatory, insurance, or breach notification advice
Crisis communications
Configuration of network devices, firewalls, EDR, or other third-party security tools
Full Platform Foundation Deployment, Labeling, or Discovery
Long-term segmentation policy beyond incident separation
Transition to a full deployment, which is delivered through separate packages
Guaranteed prevention of further compromise
On-call or standby coverage outside defined service hours
Ongoing support after transition
Expected Timeline
This engagement follows the incident. The applicable order defines activation, response times, and hours of coverage.
Effort depends on:
- Purchased package size
- Number of in-scope workloads
- Whether Illumio is already deployed
- How quickly VENs can be deployed
- How quickly workloads are classified
- Availability of the customer and its IR firm.
The engagement ends at the earliest of the following: the customer or IR firm confirms containment is no longer needed, the purchased effort is used up, or the customer transitions to standard Illumio services.
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
