> For the complete documentation index, see [llms.txt](https://legal.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legal.dispel.com/security-and-data-protection/shared-security-model/complementary-user-entity-controls.md).

# Complementary User Entity Controls

This page summarizes the customer security responsibilities for Dispel’s SaaS and on-prem deployments.

{% hint style="info" %}
This document speaks to the security controls customers operate. For specific technical shared responsibilities, please visit [Shared Responsibilities](https://legal.dispel.com/security-and-data-protection/shared-security-model/shared-responsibilities.md).
{% endhint %}

## Introduction

As part of Dispel’s commitment to security and transparency, we publish this Complementary User Entity Controls (CUECs) document to identify the security responsibilities that rest with our customers. These controls are **complementary** to those implemented by Dispel and are critical to ensuring that the combined security program for your environment—spanning Dispel’s Zero Trust Engine (ZTE), remote access workflows, micro-segmentation, and threat-detection features—operates effectively.

Because Dispel serves organizations operating in highly regulated sectors—including industrial manufacturing, critical infrastructure, utilities, defense contractors, and operators of OT/ICS environments—we align our CUECs with the frameworks **most commonly used by our customers**:

* **IEC 62443-3-3** (System Security Requirements and Security Levels), widely used for OT and industrial control systems;
* **NIST SP 800-53 Rev. 5 High Baseline**, used across U.S. federal and defense programs and often adopted by enterprises seeking strong cybersecurity controls; and
* **EU NIS2 Directive (Directive (EU) 2022/2555)**, for customers designated as essential or important entities. See the NIS2 Article 21(2) Mapping section at the end of this page.

Expressing customer responsibilities in these frameworks lets you map them directly into your existing compliance obligations and shortens audit cycles.

We encourage customers to view Dispel’s controls and their own controls as a shared-responsibility model. Dispel secures the cloud infrastructure, platform features, and connective workflows. Customers secure the assets, identities, networks, and processes they manage.

**The specific division of responsibilities depends heavily on how Dispel is deployed**, and our customers use Dispel in two distinct ways:

1. **Dispel-Hosted SaaS Deployment** — Dispel operates the entire platform infrastructure.
2. **On-Premises / Customer-Cloud Deployment** — The platform is deployed fully inside customer-controlled infrastructure, and the customer assumes operational hosting responsibilities.

This document will help you understand how to fulfill your part of both models.

### Understanding Complementary User Entity Controls

CUECs identify the **security controls the customer must operate** so that Dispel’s platform—whether hosted by us or by you—functions securely.

* In **SaaS deployments**, Dispel handles platform hosting, infrastructure security, and system availability.
* In **On-Prem / Customer-Cloud deployments**, customers assume many of those functions and must perform platform-level operations as well as site-level security.

Each section below highlights what customers must do in each deployment model.

## Customer Responsibilities by Security Domain

### Dispel Platform Configuration

{% hint style="info" %}
**Mapping:** IEC 62443 SR-1.1, SR-1.7, SR-1.11, SR-2.1, SR-2.6, SR-2.8, SR-7.6–7.8; NIST AC-2(3), AC-6, AC-7, AC-12, AU-6, AU-12, CM-6, CM-7, CM-8, IA-2, IA-2(1), IA-2(2), IA-5(1), PS-4; NIS2 Art. 21(2)(f), (i), (j)
{% endhint %}

#### **Why this matters**

Dispel is built around 45 [Universal Controls](https://docs.dispel.com/secure-and-govern/overview/universal-controls) that cover the remote access lifecycle, each based on a NIST SP 800-53 Rev. 5 control. Dispel can perform many of these controls for you, but how many depends on your configuration and subscription:

* **Platform** controls are part of how Dispel is built. You inherit them automatically.
* **Configurable** controls are capabilities Dispel provides that take effect only once you turn them on. Some also depend on add-ons, such as Session Forensics.
* **Shared** controls are split between Dispel and you. Dispel performs its part, and you perform yours.

Some controls require configuration in the Dispel platform in order to pass. The table below shows which ones and where to find them. To check your configuration, go to **Security → Compliance → Controls** in the Dispel app.

#### **Customer Responsibilities**

These responsibilities apply to both SaaS and On-Prem / Customer-Cloud deployments. Your Dispel account team can confirm which add-ons your subscription includes.

| Control                | Customer responsibility                                                                                                     | Where to configure                                  |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| IA-2, IA-2(1), IA-2(2) | Enforce two-factor authentication or SSO for the whole organization. If you use SSO, enforce MFA in your identity provider. | Settings → Security                                 |
| IA-5(1)                | If you do not enforce SSO, set password lifetime and password reuse policies.                                               | Settings → Security                                 |
| AC-12                  | Require access windows for roles whose access should be time-bound, such as third-party contractors.                        | Settings → Security                                 |
| AU-12                  | Allow Regions to record Browser Connect sessions.                                                                           | Settings → Browser Connect                          |
| AC-6                   | Limit the Organization Admin role to the people who administer Dispel, and give other members non-admin roles.              | Users                                               |
| AU-6                   | Review audit records and session recordings, either with the Session Forensics add-on or with your own tooling.             | Session Forensics: contact your Dispel account team |
| AC-7, AC-2(3)          | Optionally set stricter failed-login suspension and inactivity lockout limits than Dispel’s defaults.                       | Settings → Security                                 |
| CM-6                   | Select the compliance frameworks that apply to you, and rerun assessments after changing settings.                          | Security → Compliance                               |
| CM-7                   | Define ACL rules for each Region so users reach only the assets they need.                                                  | Region ACL rules                                    |
| CM-8                   | Register the devices reachable through Dispel, or connect an asset-discovery integration.                                   | Devices or asset-discovery integration              |
| PS-4                   | Deactivate members promptly when they leave or no longer need access.                                                       | Users                                               |

### **Identity & Access Management (IAM)**

{% hint style="info" %}
**Mapping:** IEC 62443 SR-1.1–1.5, SR-1.7, SR-2.1, SR-2.12; NIST AC-2, AC-3, AC-5, AC-6, IA-2, IA-5; NIS2 Art. 21(2)(i), (j)
{% endhint %}

#### **Why this matters**

Attackers commonly target identities. Dispel integrates with your IdP, but you control authentication upstream.

#### **Customer Responsibilities**

**SaaS Deployment**

* Maintain user lifecycle processes for your IdP (provision/de-provision).
* Enforce MFA and authenticator-strength policies on your enterprise IdP.
* Maintain least-privilege role assignments.
* Review users, roles, and Organization Admin assignments on a defined schedule, and remove access that is no longer needed.
* Assign each person an individual account and do not share credentials, so actions taken through Dispel can be attributed to a named individual.
* Sponsor each third-party user (contractor or vendor), limit their access in time, and remove it when the engagement ends.
* Ensure third-party users are bound by your own security and confidentiality requirements.
* Secure customer-managed credentials, API keys, and certificates.

**On-Prem / Customer-Cloud Deployment**

All SaaS responsibilities **plus**:

* You are responsible for securing, maintaining, and hardening the identity systems you integrate with Dispel.
* You must configure, secure, and monitor the authentication infrastructure used by the Dispel instance (e.g., SAML/SCIM endpoints hosted internally).
* You are responsible for access control on all platform servers, VMs, and support systems.

### Asset, Configuration & Change Management

{% hint style="info" %}
**Mapping:** IEC 62443 SR-7.6–7.8; NIST CM-2, CM-3, CM-6, CM-7, CM-8; NIS2 Art. 21(2)(a), (e), (i)
{% endhint %}

#### **Why this matters**

Dispel secures connectivity; you control the assets connected behind it (PLCs, firewalls, HMIs, servers).

#### **Customer Responsibilities**

**SaaS Deployment**

* Maintain inventory of assets behind Dispel micro-segments.
* Maintain secure configurations of OT/ICS/IT assets connected to Dispel.
* Disable unused ports, services, and protocols on assets reachable through Dispel.
* Validate that only authorized assets reside in Dispel segments.
* Follow change-control processes for systems integrated with Dispel.
* Apply Wicket ESI updates, and keep Wicket ESI on a version supported under the [Product Lifecycle Policy](https://legal.dispel.com/support/product-lifecycle-policy).

**On-Prem / Customer-Cloud Deployment**

All SaaS responsibilities **plus**:

* You operate and patch the virtual machines, servers, storage, networking, and OS layers that host the Dispel platform.
* You maintain configuration baselines and change control for Dispel platform nodes, load balancers, databases, and endpoint services.
* You must ensure secure installation, configuration, and dependency management for all platform components.
* You must keep the Dispel platform on a version supported under the Product Lifecycle Policy.

### Logging, Monitoring & Incident Response

{% hint style="info" %}
**Mapping:** IEC 62443 SR-2.8, SR-2.9, SR-6.1, SR-6.2; NIST AU-6, AU-11, IR-4, IR-6, IR-8; NIS2 Art. 21(2)(b), (f); Art. 23
{% endhint %}

#### **Why this matters**

Dispel logs platform activity. Customers log their internal environment.

#### **Customer Responsibilities**

**SaaS Deployment**

* Monitor logs for systems not hosted by Dispel (local OT/IT networks).
* Review Dispel audit logs and session recordings on a defined schedule, and export and retain them according to your retention requirements.
* Maintain and execute your internal IR plan.
* Meet any regulatory incident-reporting obligations that apply to you (for example, NIS2 Article 23).
* Notify Dispel promptly of any suspected compromise of accounts, credentials, or devices used to access Dispel.
* Maintain an SIEM/SOC if you so choose.
* Designate security contacts for coordination with Dispel, and keep them current.
* Perform local containment (e.g., isolating plant networks).

**On-Prem / Customer-Cloud Deployment**

All SaaS responsibilities **plus**:

* You must collect, store, protect, and monitor logs generated by the Dispel platform infrastructure itself.
* You are responsible for maintaining uptime for monitoring systems (SIEM, log collectors).
* You must integrate platform logs into your IR workflow and perform forensic preservation as needed.
* You own the patching and security lifecycle of monitoring agents on platform nodes.

### Physical & Environmental Security

{% hint style="info" %}
**Mapping:** IEC 62443-2-1 (physical and environmental security is outside the scope of IEC 62443-3-3 SRs); NIST PE-3, PE-4, PE-13, PE-18; NIS2 Art. 21(2) (all-hazards approach)
{% endhint %}

#### **Why this matters**

Physical access defeats digital controls.

#### **Customer Responsibilities**

**SaaS Deployment**

* Secure all local OT/ICS assets and workstations.
* Protect engineering laptops used to access Dispel.
* Maintain environmental protections on local systems.

**On-Prem / Customer-Cloud Deployment**

All SaaS responsibilities **plus**:

* You must secure the physical servers, racks, data centers, and cloud resources hosting the Dispel platform.
* You must ensure environmental controls (power, cooling, humidity) for all platform nodes.
* You must physically restrict access to administrative consoles and hardware used by the platform.

### Network Security & Communications Integrity

{% hint style="info" %}
**Mapping:** IEC 62443 SR-1.13, SR-5.1, SR-5.2, SR-7.6; NIST AC-17, SC-3, SC-5, SC-7, SC-13; NIS2 Art. 21(2)(d)
{% endhint %}

#### **Why this matters**

Dispel provides secure transport and micro-segmentation. Customers control surrounding networks.

#### **Customer Responsibilities**

**SaaS Deployment**

* Route all remote access to OT assets through Dispel, and remove or disable alternative remote access paths (for example, vendor modems or unmanaged remote desktop tools).
* Maintain segmentation and firewall rules at your network boundary.
* Patch and secure your local networking equipment (firewalls, routers, proxies).
* Harden ICS protocols behind your network.
* Validate contractor access before issuing credentials.

**On-Prem / Customer-Cloud Deployment**

All SaaS responsibilities **plus**:

* You secure and operate the network that hosts the Dispel platform, including VLANs, subnets, cloud VPCs, and routing controls.
* You must configure secure ingress/egress rules for platform components.
* You are responsible for securing local load balancers, API gateways, VPN bridges, and HA pairs used by the platform.
* You must protect and isolate platform management interfaces.

### Data Governance & Recovery

{% hint style="info" %}
**Mapping:** IEC 62443 SR-4.1, SR-4.3, SR-7.3, SR-7.4; NIST CP-2, CP-9, MP-2, SC-12, SC-13; NIS2 Art. 21(2)(c), (h)
{% endhint %}

#### **Why this matters**

Customers own their data and must maintain governance over how it is stored, transmitted, and backed up.

#### **Customer Responsibilities**

**SaaS Deployment**

* Maintain backups of any data stored outside Dispel’s cloud.
* Classify and handle data according to your internal policies.
* Manage customer-owned materials used in integrations.
* Select Dispel regions that meet your data residency requirements.
* Give notice to users whose sessions are recorded, and establish a lawful basis for recording them, as required by applicable privacy law (for example, GDPR).
* Maintain business continuity plans for operating if remote access through Dispel is unavailable.

**On-Prem / Customer-Cloud Deployment**

All SaaS responsibilities **plus**:

* You must back up and restore the Dispel platform infrastructure (databases, configs, platform nodes, etc.).
* You must ensure secure storage, rotation, and protection of any encryption keys used by the platform.
* You are responsible for backup media protection and disaster recovery processes for the entire deployment.

### Endpoint Security

{% hint style="info" %}
**Mapping:** IEC 62443 SR-2.3, SR-3.2, SR-3.4; NIST AT-2, SI-2, SI-3, SI-7, SC-3; NIS2 Art. 21(2)(g)
{% endhint %}

#### **Why this matters**

Compromised endpoints undermine remote access security regardless of platform protections.

#### **Customer Responsibilities**

**SaaS Deployment**

* Harden and monitor endpoints accessing Dispel (antivirus/EDR, secure configuration, patching).
* Secure target jump hosts or HMIs connected to through Dispel.
* Train users and administrators on secure use of Dispel, including recognizing phishing and protecting their credentials.

**On-Prem / Customer-Cloud Deployment**

All SaaS responsibilities **plus**:

* You must secure the endpoints hosting Dispel platform services:
  * Admin consoles
  * Deployment servers
  * Orchestration servers
  * Any underlying OSes
* You must maintain patching, vulnerability scanning, and malware protection for all platform nodes.

## NIS2 Article 21(2) Mapping

{% hint style="info" %}
Under the NIS2 Directive, cybersecurity risk-management obligations rest with the essential or important entity and cannot be transferred to a supplier. The table below shows how the customer responsibilities on this page relate to each measure in Article 21(2). It is not legal advice; consult your legal advisor for questions about your obligations.
{% endhint %}

| Article 21(2) measure                                                                                      | Responsibility                                     | Customer responsibilities                                                                                                                                                                        | Related section                                                                                       |
| ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |
| (a) Risk analysis and information system security policies                                                 | Customer                                           | Include Dispel in your risk assessment, and define which assets and zones may be reached through it.                                                                                             | Asset, Configuration & Change Management                                                              |
| (b) Incident handling                                                                                      | Shared                                             | Maintain and execute your incident response plan, coordinate with Dispel through designated security contacts, and meet your Article 23 reporting obligations.                                   | Logging, Monitoring & Incident Response                                                               |
| (c) Business continuity, backup management, disaster recovery, and crisis management                       | Shared (SaaS); Customer (On-Prem / Customer-Cloud) | Plan for continued operations if remote access is unavailable. For on-prem and customer-cloud deployments, back up and restore the Dispel platform.                                              | Data Governance & Recovery                                                                            |
| (d) Supply chain security                                                                                  | Customer                                           | Assess Dispel as a supplier using the attestation reports available in the Dispel Trust Portal, and validate contractor and vendor access before issuing credentials.                            | Network Security & Communications Integrity                                                           |
| (e) Security in acquisition, development, and maintenance, including vulnerability handling and disclosure | Shared                                             | Apply Dispel updates in on-prem and customer-cloud deployments and on Wicket ESI, and patch the systems that host them. Dispel provides updates and operates a Vulnerability Disclosure Program. | Asset, Configuration & Change Management                                                              |
| (f) Assessing the effectiveness of cybersecurity risk-management measures                                  | Customer                                           | Periodically review Dispel roles, configurations, audit logs, and session recordings, run Dispel compliance assessments, and test the controls you operate around Dispel.                        | Dispel Platform Configuration; Logging, Monitoring & Incident Response                                |
| (g) Basic cyber hygiene and cybersecurity training                                                         | Customer                                           | Train users and administrators, and keep endpoints that access Dispel hardened and patched.                                                                                                      | Endpoint Security                                                                                     |
| (h) Cryptography and encryption                                                                            | Shared                                             | Define your cryptography policy. For on-prem and customer-cloud deployments, store, rotate, and protect platform encryption keys. Dispel implements tunnel encryption.                           | Data Governance & Recovery                                                                            |
| (i) Human resources security, access control, and asset management                                         | Customer                                           | Run joiner, mover, and leaver processes in your IdP, review access on a defined schedule, keep role assignments least-privilege, and maintain an inventory of assets behind Dispel.              | Dispel Platform Configuration; Identity & Access Management; Asset, Configuration & Change Management |
| (j) Multi-factor or continuous authentication, secured communications, and emergency communication systems | Shared                                             | Enforce two-factor authentication or SSO in Dispel and MFA on your enterprise IdP, and keep emergency communication channels that do not depend on Dispel.                                       | Dispel Platform Configuration; Identity & Access Management                                           |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://legal.dispel.com/security-and-data-protection/shared-security-model/complementary-user-entity-controls.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
