Basic Policy - Core Services + Ransomware

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

INTRODUÇÃO

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

Overview

The Basic Policy – Core Services + Ransomware package establishes the customer's first operational segmentation policies by defining shared infrastructure communications and implementing controls that reduce ransomware propagation risk.

The engagement begins by identifying business-critical shared services and administrative platforms used throughout the environment. These services are organized into a documented Core Services policy framework designed to support future segmentation efforts. Core services are broadly defined as global or administrative services consumed across the environment, such as Active Directory, DNS, DHCP, endpoint management platforms, vulnerability scanners, monitoring systems, and similar support infrastructure.

Once the core-services foundation is established, Illumio Professional Services implements ransomware-containment controls focused on restricting high-risk protocols commonly leveraged for lateral movement. Because containment rules can interact with core-service communications, the engagement includes an iterative review that revisits core-services policy as risky protocols are restricted.

The resulting policy framework serves as the customer's baseline segmentation architecture and creates the policy foundation required for Ringfencing, Environmental Separation, and future policy development.

Illumio Part Names covered by this Service Description are:

  • IL-SVCS-PEOPT-BASIC-POL-S
  • IL-SVCS-PEOPT-BASIC-POL-M
  • IL-SVCS-PEOPT-BASIC-POL-L
  • IL-SVCS-PEOPT-BASIC-POL-XL

Who should engage?

Recommended participants include:

  • Security architects
  • Security engineers Infrastructure administrators
  • Active Directory administrators
  • Platform administrators
  • Vulnerability-management teams
  • Security operations teams
  • Application owners
  • Enterprise architects
  • Network security teams

Broad stakeholder participation is recommended because shared services frequently span multiple operational teams.

Prerequisites

Package Dependencies

  • Platform Foundation Deployment
  • Labeling
  • Descoberta  

Strongly Recommended Packages

  • Segmentation Strategy & Roadmap  

Technical Readiness

  • Operational PCE
  • Visibility data available for the agreed scope
  • Discovery findings available
  • Required IP Lists and Unmanaged Workloads created
  • Labels established for the agreed in-scope workload population
  • Customer-approved application inventory available  

Customer Readiness

  • Project sponsor assigned
  • Technical point of contact assigned
  • Core-service owners identified
  • Application stakeholders available
  • Security stakeholders available
  • Change-management process defined

Covered Services

Core Services Analysis and Design

  • Review Discovery findings and available traffic data.
  • Identify shared infrastructure and administrative services in scope.
  • Validate core-service communication requirements with stakeholders.
  • Review operational dependencies and consumption patterns.
  • Define reusable policy structures and policy hierarchy.
  • Define the customized architectural configuration structure for core-services policy.
  • Identify required exceptions and document their rationale.

Customer Outcome

Customer receives a validated architectural model for shared-services policy that can be reused and extended as additional services are onboarded.

Core Services Policy Implementation and Handoff

  • Implement core-services policy for up to ten (10) approved core-service applications.
  • Create and organize required policy objects and rule structures.
  • Validate policy against observed and approved communications.
  • Document implemented policy structure and associated objects.
  • Provide a reference guide describing core-services policy structure, construction methodology, and maintenance practices.
  • Document exception-management guidance and future core-services onboarding guidance.
  • Review implemented policy and documentation with customer stakeholders.

Customer Outcome

Customer has an implemented and documented core-services policy framework and the reference material required to continue expanding and maintaining it independently.

Ransomware Containment Design and Implementation

  • Review the standard high-risk protocol list and customize where requested.
  • Design the deny-rule framework used to restrict high-risk protocols.
  • Implement containment controls for up to ten (10) approved risky protocols, commonly beginning with RDP and SSH and typically including protocols such as Telnet, FTP, and SMB.
  • Validate the impact of containment rules on core-service communications.
  • Iteratively revisit and adjust core-services policy where containment rules interrupt required communications.
  • Create and document approved exceptions and their rationale.

Customer Outcome

Customer receives implemented containment controls that reduce lateral-movement risk while preserving required core-service communications.

Ransomware Containment Documentation and Handoff

  • Document blocked protocols, approved exceptions, and exception rationale.
  • Add ransomware-containment content to the customer policy reference documentation.
  • Provide an as-built record of implemented policy, rule organization, and associated objects.
  • Document ransomware-policy administration and future protocol-evaluation guidance.
  • Document recommended containment-expansion approach and operational ownership.
  • Review implemented controls and documentation with customer stakeholders.

Customer Outcome

Customer has a documented containment framework, a record of blocked protocols and exceptions, and the operational guidance required to maintain and expand ransomware controls after Professional Services disengagement.

Assumptions

Discovery findings are available for the agreed in-scope environment.

Required policy objects have been created.

Labels exist for the agreed in-scope workload population.

Core-service owners and application stakeholders are available when required.

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

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

Customer will maintain and expand policy following handoff.

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 in-scope core-service applications.

Provide access to Illumio administrators and required platform access.

Make core-service owners, application owners, and security stakeholders available.

Validate required core-service communications.

Review and approve the high-risk protocol list.

Review and approve required exceptions.

Participate in policy-validation activities.

Perform customer-side change-management and approval activities.

Review provided documentation and reference material.

Assume ongoing ownership of policy administration and expansion after delivery.

Out of Scope/Limitations: Scope Limitations

Limited to ten (10) core-service applications.

Limited to ten (10) approved risky protocols.

Limited to ten (10) exception rules to bypass risky protocol deny rules.

Policy reflects the environment state and available data during delivery.

Policy effectiveness depends on the completeness of Discovery findings and labeling.

Customer is expected to expand policy coverage after engagement completion.

Exception handling is limited to exceptions identified and approved during the engagement.

Enforcement of all workloads is not included.

Out of Scope/Limitations: Excluded Scope

Full-environment segmentation

Enforcement of all workloads

Application Ringfencing

Separação ambiental

Tier-to-tier segmentation

Microsegmentation Policy development beyond the approved core-service and protocol limits

Unlimited exception creation

Customer change-management execution

Remediation of customer metadata or workload labels

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

Custom automation, scripting, or integration development

Threat hunting

Resposta a incidentes

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:

  • Package size
  • Number of core-service applications
  • Number of risky protocols selected
  • Discovery readiness
  • Label quality
  • Stakeholder availability
  • Customer review and approval cycles.

Delays in dependency validation, exception decisions, or change 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