RBAC Configuration

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

EINFÜHRUNG

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

Overview

The RBAC add-on sets up role-based access control in the Illumio platform so each user has the access their job requires and nothing more.

Illumio RBAC is built on users and permissions. Each permission combines a role, an optional scope, and the user or group it is granted to. Roles define what a user can do, such as creating labels or provisioning policy changes. Scopes limit those actions to workloads that carry specific Application, Environment, and Location labels. Because scopes are made of labels, RBAC design depends on the customer's label schema. For that reason this add-on is delivered alongside the Labeling engagement.

Illumio Professional Services works with the customer to define its access goals, including separation of duties and whether application owners need access. It then maps those goals to Illumio roles, scopes, and identity-provider groups and configures RBAC in the PCE.

At the end of the engagement, the customer has a working RBAC configuration for its current needs, a document describing the design, and a template and instructions for adding roles, scopes, and groups on its own.

Illumio Part Names covered by this Service Description are:

  • IL-SVCS-DEPF-RBAC-ADDON-S
  • IL-SVCS-DEPF-RBAC-ADDON-M
  • IL-SVCS-DEPF-RBAC-ADDON-L
  • IL-SVCS-DEPF-RBAC-ADDON-XL

Who should engage?

Recommended stakeholders include:

Illumio platform administrators Security architects and security engineers Identity and access management teams Identity provider administrators Security operations teams Application owners, where scoped application-owner access is planned Governance, risk, and audit stakeholders, where separation of duties is required Project managers

Identity team participation is essential when access is managed through an external identity provider, because group names and user mappings come from that system.

Prerequisites

Package Dependencies

  • Platform Foundation Deployment
  • Labeling  

This add-on can be attached to the Visibility, Containment, or Segmentation Bundle, since all three include both prerequisite packages.  

Technical Readiness

  • Operational PCE
  • Label schema defined through the Labeling engagement, including Application, Environment, and Location labels used for scopes
  • If an identity provider is used: SSO configured, and external users and groups added to the PCE before permissions are assigned
  • Administrative access to the PCE for Illumio Professional Services  

Customer Readiness

  • Project manager or primary point of contact assigned
  • High-level access goals identified, including separation-of-duties needs and application-owner access requirements
  • Customer-provided role definitions for the users and teams in scope
  • Identity provider group names identified, where applicable Identity and access management stakeholders available

Covered Services

RBAC Requirements and Design

  • Explain Illumio RBAC concepts: users, permissions, roles, scopes, and how access is bound to users and groups.
  • Review the customer's access goals, separation-of-duties needs, and application-owner access requirements.
  • Map customer-provided role definitions to Illumio global and scoped roles.
  • Design scopes using the customer's Application, Environment, and Location labels.
  • Map roles and scopes to identity provider groups or local users.
  • Agree the RBAC design with customer stakeholders.

Customer Outcome

The customer has an agreed RBAC design that connects its organizational roles to Illumio permissions and label-based scopes.

RBAC Configuration and Validation

  • Configure the agreed RBAC roles and associated groups, up to the limit of the purchased size.
  • Configure label-based scopes for scoped roles.
  • Bind roles and scopes to identity provider groups or local users.
  • Validate that users receive the intended access and that scoped users are limited to workloads within their scope.
  • Resolve configuration issues within the Illumio platform.

Customer Outcome

The customer has a working RBAC configuration in the PCE that gives each user group the intended level of access.

Documentation and Handoff

  • Provide a document describing the RBAC design and configuration.
  • Provide a template for future RBAC additions and changes.
  • Provide instructions for adding roles, scopes, and group mappings after the engagement.
  • Explain how label changes affect scoped access. Review the configuration and documentation with customer stakeholders.

Customer Outcome

The customer can maintain its RBAC configuration and extend it to new teams, applications, and scopes without further Professional Services involvement.

Assumptions

Platform Foundation Deployment and Labeling are delivered before or alongside this add-on.

The label schema is stable enough to define scopes; later label changes may require customer updates to scopes.

If an identity provider is used, SSO is already configured and external users and groups are present in the PCE.

The customer provides role definitions and access goals; Illumio does not define the customer's organizational roles.

The customer's identity provider is a supported platform.

Identity and platform stakeholders are available within agreed project timelines.

Documents are produced using Illumio templates.

The customer maintains RBAC configuration after handoff.

Customer Requirements

The customer will:  

Assign a project manager or primary point of contact.

Provide high-level access goals, including separation-of-duties and application-owner access requirements.

Provide role definitions for the users and teams in scope.

Provide identity provider group names, where applicable.

Configure SSO and make sure external users and groups are present in the PCE before permissions are assigned.

Create or maintain identity provider groups and user membership.

Provide administrative PCE access.

Review and approve the RBAC design.

Validate user access during testing.

Maintain and extend RBAC configuration after the engagement.

Out of Scope/Limitations: Scope Limitations

Each purchased block includes up to five (5) RBAC roles and associated groups, mapped to customer-provided role definitions.

Scopes use the label schema delivered through the Labeling engagement.

Configuration covers the organization's current access needs at the time of delivery.

Supported identity provider platforms only.

RBAC effectiveness depends on accurate labels and accurate identity provider group membership.

Out of Scope/Limitations: Excluded Scope

Defining new organizational roles or access policies for the customer

Integration with unsupported identity provider platforms

SSO configuration, which is delivered through Platform Foundation Deployment

Creating, modifying, or managing identity provider groups or user membership

Label schema design or label remediation

RBAC roles and groups beyond the purchased block

Custom scripts or API automation for user or permission management

Identity governance, access certification, or access review programs

Configuration of third-party identity, directory, or privileged access tools

Policy development, provisioning, or enforcement

Ongoing user administration or access management after handoff

Expected Timeline

This add-on is delivered alongside the Labeling engagement, since scopes depend on the label schema. The schedule is set at project initiation based on:

  • Purchased block size
  • Number of roles, scopes, and groups
  • Identity provider readiness
  • Label schema readiness
  • Stakeholder availability and review cycles.

Delays in SSO readiness, identity provider group setup, label schema decisions, or customer approvals may affect the 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