Flowlink and NEN Deployment

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

INTRODUCTION

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

Overview

The Flowlink and NEN Deployment add-on sets up Illumio Flowlink, the Illumio Network Enforcement Node (NEN), or both, so that network traffic from systems without a VEN is ingested into the Policy Compute Engine for analysis.

Visibility across all communications is critical for segmentation, and the preferred way to get it is a VEN on each workload. In some cases a VEN can't be installed, or the customer chooses not to install one. Examples include mainframes, storage filers, legacy Windows systems, appliances, systems where an agent would void vendor support, and latency-sensitive high-transaction servers. Flowlink and the NEN fill that gap by bringing network-sourced flow data into the PCE.

Flowlink collects flow records from network devices and uploads them to the PCE. Current releases can also stream flows to Azure Event Hub for higher-throughput ingestion. The NEN is installed as part of the Illumio deployment and paired with the PCE. For switch devices, it can receive traffic flow information from managed network devices and supply that data to the PCE.

These are separate products. They are combined in one service add-on because both do the same job at this stage of the program: getting traffic into the PCE. The add-on is normally delivered during Platform Foundation Deployment, and delivery can continue into the Labeling or Discovery phases. When it is complete, network-sourced traffic is flowing into the PCE and is available for analysis in Discovery before any policy is configured.

Illumio Part Names covered by this Service Description are:

  • IL-SVCS-DEPF-FLOW-NEN-ADDON-S
  • IL-SVCS-DEPF-FLOW-NEN-ADDON-M
  • IL-SVCS-DEPF-FLOW-NEN-ADDON-L
  • IL-SVCS-DEPF-FLOW-NEN-ADDON-XL

Who should engage?

This add-on is for customers that have purchased Illumio Flowlink or NEN and need visibility into systems or network segments that can't be covered by VENs.

Recommended stakeholders include:

  • Illumio platform administrators
  • Network architects and network engineers
  • Network device and load balancer administrators
  • Server and infrastructure administrators responsible for the Flowlink or NEN host servers
  • Security architects and security engineers
  • Cloud and messaging platform owners, where flows are streamed through Azure Event Hub
  • Change-management stakeholders Project managers

Network team participation is essential. The customer must configure their own network devices to send traffic information to Flowlink or the NEN.

Prerequisites

Package Dependencies

  • Platform Foundation Deployment  

Product Readiness

  • Illumio Flowlink and/or NEN licensing purchased
  • Operational PCE instance

Technical Readiness

  • Customer-managed servers with a supported operating system for each Flowlink or NEN instance, including two servers or Load Balancer where the NEN is deployed as a high-availability pair
  • Access privileges to install software on those servers
  • Web server certificate for each server
  • Network connectivity between the Flowlink or NEN servers, the network devices supplying flow data, and the PCE
  • Azure Event Hub available and accessible, where Flowlink will stream flows through it  

Customer Readiness

  • Project manager or primary point of contact assigned
  • Network device owners identified and available
  • Inventory of the network devices and segments that will supply flow data
  • Change approvals in place for network device and server changes

Covered Services

Deployment Planning

  • Confirm which products are in scope: Flowlink, NEN, or both.
  • Identify the systems, network segments, and devices that need network-sourced visibility.
  • Review server readiness, including operating system, access, certificates, and high-availability requirements.
  • Confirm the ingestion approach for each product, including direct upload to the PCE or streaming through Azure Event Hub where applicable.
  • Confirm the network-device configuration the customer must perform to send flow data.

Customer Outcome

The customer has an agreed ingestion design that identifies which traffic will come into the PCE, through which product, and what the customer must prepare before installation.

Flowlink Deployment and Flow Ingestion

  • Applies where Flowlink is purchased.
  • Install Flowlink on customer-managed servers.
  • Configure Flowlink to run as a Linux service where the installed version supports it, so it restarts automatically after a reboot.
  • Configure flow ingestion from the customer's network devices.
  • Configure flow upload to the PCE, or flow streaming through Azure Event Hub where applicable.
  • Record each installation's instance identifier for traceability and troubleshooting.

Customer Outcome

Flow records from the customer's network devices are collected by Flowlink and delivered to the PCE.

NEN Deployment and Pairing

  • Applies where NEN is purchased.
  • Install the NEN application on customer-managed servers, including a high-availability pair where required. Pair the NEN with the PCE. Register the in-scope network switches or Load-Balancers with the NEN so they can report traffic flow information. Configure the NEN to receive traffic flow information from managed switches and supply that data to the PCE.

Customer Outcome

The NEN is installed, paired with the PCE, and supplying network-sourced traffic data for the in-scope switches.

Ingestion Validation and Handoff

  • Confirm that network-sourced traffic is arriving in the PCE.
  • Troubleshoot ingestion issues within the Illumio components.
  • Document the deployed configuration, including servers, instances, ingestion paths, and connected devices.
  • Document operating guidance for maintaining Flowlink and NEN, and for adding more network devices later.
  • Document traffic sources that were identified but not connected, along with the customer actions needed to connect them.
  • Review the deployment and documentation with customer stakeholders.

Customer Outcome

Network-sourced traffic is ingested into the PCE and ready for analysis in Discovery, and the customer has the documentation it needs to maintain and extend ingestion on its own.

Assumptions

The customer has purchased the Flowlink and/or NEN licensing that corresponds to this add-on.

The PCE is operational before installation begins.

The customer provides servers with a supported operating system, required access privileges, and web server certificates before installation.

The customer configures its own network devices to send traffic information to Flowlink or the NEN.

Illumio does not configure network devices.

Network devices supplying flow data are supported and able to export flow information.

Required network paths between network devices, Flowlink or NEN servers, and the PCE are open.

Where Azure Event Hub is used, the customer provisions and manages the Event Hub resources.

The customer's network and server teams are available within agreed project timelines.

Delivery normally takes place during Platform Foundation Deployment and may continue into Labeling or Discovery.

The customer maintains Flowlink, NEN, and network-device configuration after handoff.

Customer Requirements

The customer will:  

Assign a project manager or primary point of contact.

Provide customer-managed servers with a supported operating system for each Flowlink or NEN instance.

Grant the access privileges needed to install software on those servers.

Provide a web server certificate for each server.

Provide the PCE pairing key for NEN deployment.

Configure network devices to send traffic information to Flowlink or the NEN.

Open the required network paths between network devices, Flowlink or NEN servers, and the PCE.

Provision and manage Azure Event Hub resources where applicable.

Identify the network devices and segments in scope.

Obtain customer-side change approvals for server and network-device changes.

Review the deployment and documentation.

Maintain Flowlink, NEN, and network-device configuration after handoff.

Out of Scope/Limitations: Scope Limitations

The add-on covers deployment and configuration for traffic ingestion only.

Ingestion is limited to the network devices and segments agreed during deployment planning.

The completeness of ingested traffic depends on how the customer configures its network devices and on each device's ability to export flow data.

Network-sourced flow data may not carry the same context as VEN-reported data.

Delivery may continue into the Labeling or Discovery Phase of the deployment.

Out of Scope/Limitations: Excluded Scope

NEN policy enforcement on switches or load balancers

Generating, applying, or managing switch ACLs or load balancer firewall policy

Load balancer integration, including F5 AFM or LTM configuration

Creating and labeling Unmanaged Workloads mapped to switch interfaces

Configuring customer network devices, switches, routers, or load balancers

Provisioning, building, or patching servers, or maintaining their operating systems

Procuring or managing certificates

Provisioning or administering Azure Event Hub, Kafka, or other messaging infrastructure

Analyzing ingested traffic, which is performed in Discovery

Creating labels, IP Lists, or other policy objects

Developing, provisioning, or enforcing policy Custom scripts, automation, or integration development

Consultancy or configuration of third-party equipment or software

Ongoing monitoring, administration, or support after handoff

Expected Timeline

This add-on is normally delivered during Platform Foundation Deployment and may continue into Labeling or Discovery. The delivery schedule is set at project initiation based on:

  • Purchased add-on size
  • Products in scope: Flowlink, NEN, or both
  • Number of instances and connected network devices
  • Whether a high-availability NEN pair is required
  • Readiness of customer servers, certificates, and network devices
  • Network team availability and change-approval cycles.

Delays in server readiness, certificates, network-device configuration, or change 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