Only this pageAll pages
Powered by GitBook
Couldn't generate the PDF for 145 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

🇺🇸 English

Loading...

Get started

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Connect to your systems

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Build your environment

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Manage users & access

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Secure & govern

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Monitor & investigate

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Welcome

Secure remote access that gets your team and vendors to the right devices in minutes.

Dispel's layered access model across facility levels, from corporate management down to process and control

Get started

New to Dispel? Start here.

Getting Started with Dispel

Set up your organization and make your first connection.

User Quick Start Guide

Sign in, request access, and connect to a device.

Key Terminology

The core concepts: facilities, access windows, and Wickets.

Connect to facilities

Access Windows

Request, approve, and manage timed access to a facility.

Browser Connect

Reach a device from your browser, with nothing to install.

Virtual Desktops

Reserve a desktop inside the facility's network.

Manage your organization

Users

Invite people, set their roles, and manage access.

Groups

Assign permissions and access to many people at once.

Roles & Permissions

What each role can do across the organization, regions, and facilities.

Settings

Branding, points of contact, and organization-wide options.

Secure and monitor

Policy Builder

Decide who is challenged for MFA when signing in, and how.

Session Forensics

See per-session risk and what happened during a connection.

Reports

Export access and activity for audits.

Compliance

Map Dispel controls to IEC 62443, NIST, and more.

Getting Started with Dispel

Welcome to Dispel. These guides will help you start working with Dispels' dashboard, a tool designed to provide you a safe and secure connection down to your site and OT assets.

User Quick Start Guide

User Quick Start Guide

As a user within Dispel, your main responsibility is connecting down to the necessary devices and performing your work. Follow the steps below to request access and connect to devices:

Step 1: Create a Dispel Account

Create a Dispel Account

Step 2: Request Access

Request an access window

Step 3: Connect to Site

Reserve a Virtual Desktop (User)Connect to a Browser Connect Session (User)

Access Windows

Access windows grant time-boxed access to a facility for the users and groups you choose. This section covers creating, requesting, approving, and managing them, plus the risk score that helps you wei

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Create an approved access window

Create an approved access window from the single-panel create flow, granting the members you pick access to a facility on the schedule you set.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Request an access window

Request access to a facility when you can't yet connect, then track your pending request until an approver responds.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Approve or deny a request

Review a pending access request inside an Access Window — check the risk tier and the reason, add approver notes, and approve or deny.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Manage an access window

Open a window from the Access Windows list to rename it, change its schedule, manage who and what it reaches, review its activity, and revoke access.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Access window risk scores

How Dispel scores each access window for risk, what the tiers mean, and how to read the user and device breakdown behind the pill.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Connection Methods

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Reserve a Virtual Desktop (Admin)

Reserve a Virtual Desktop from a stack as an admin, connect over RDP or in the browser, and delete it when you're done.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Reserve a Virtual Desktop (User)

Reserve a Virtual Desktop from a stack you can reach, connect to it over RDP or in the browser, and release it when you're done.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Stacks

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

VDI Users

The VDI-User role is scoped to reserving and connecting to Virtual Desktops. Assign it to people who need desktop access to your network but shouldn't manage users, devices, or stacks.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Connect with an RDP client

Use the host, username, and password Dispel shows for a reserved Virtual Desktop to connect from a desktop RDP client on Windows or macOS.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Browser Connect

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Set up Browser Connect on a device

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Connect to a Browser Connect Session (Admin)

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Connect to a Browser Connect Session (User)

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Use a Browser Connect session

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Join a shared Browser Connect session

Open a Browser Connect session-share invite link, sign in as the invited person, and join a session someone else is already running.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Install the Dispel VPN Client (macOS)

Follow this guide to install and connect with the Dispel VPN Client Application for macOS.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Install the Dispel VPN Client (Windows)

Follow this guide to install and connect with the Dispel VPN Client Application for Windows machines.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Infrastructure

How a Dispel deployment fits together, from organizations and regions down to the facilities, Wickets, and devices you reach through them.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Deployment Infrastructure

The components that make up a Dispel deployment and how they stack: organizations contain regions, regions contain facilities, and facilities contain the Wickets and devices you connect to.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Facilities

A facility is one site inside a region, with its own members, devices, and Wickets. Create facilities to control who can reach which systems at each site.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Create a Facility

Create a facility to group the users and devices at a site within a region. A facility is where you later add members, device ACLs, and access windows.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Wickets

A Wicket is the on-premise hardware or software appliance that connects your OT network to a Dispel region over an outbound encrypted tunnel.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Subnet Management

Push a subnet to a Wicket interface so the devices on that range can be reached through Dispel, then confirm the appliance actually applied it.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Device Management

Manage every device in your organization from one searchable table, then open a device to view its details, security findings, remote-access rules, and file transfer settings.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Dispel Identity

Dispel Identity verifies who a person is and links them to the accounts they use.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Getting Started

Turn on verification for the people you choose, then manage their access by person.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Use Cases

Organizations use Dispel Identity to verify who is behind the accounts that reach their systems. What changes between setups is who you verify and why.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Identity Registers

A reference to the Settings → Identity tabs: what each register and settings tab lists, and what you use it for.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Key Terminology

Access Window

A scheduled time frame during which authorized users are permitted to remotely access authorized end devices at a specified facility. Outside of this window, access is automatically denied.


Browser Connect Session

Clientless Browser Connect Sessions allow for direct access to devices within facilities. Browser Connect Sessions allow for rapid access downstream.


ACL (Access Control List) Rules

Granular access policies that specify which users can access which end devices, and through which ports and protocols.


Dashboard

Dispel’s administrative web portal found at app.dispel.com, where administrators can manage user access and permissions. Users can also reserve and launch Virtual Desktops or Browser Connect sessions to securely connect to remote end devices.


Facility

A physical or virtual location—such as a factory, plant, or network site—that is accessed and managed through Dispel’s platform. Facilities are remotely accessed through Dispel via a Wicket.


Golden Image

A pre-configured Windows image used to create Virtual Desktops. It can include specific applications, security settings, and system configurations.


Region

An individual remote access network hosted by Dispel. Each Region contains the infrastructure needed to support secure connections to end devices and is where Facilities connect via a Wicket. Regions are geographically distributed to improve performance and support compliance requirements.


Stack

A collection of Virtual Desktops built from a golden Windows image.


Virtual Desktop (VDI)

A temporary, cloud-hosted Windows machine provisioned through the Dispel Dashboard. Virtual Desktops provide users with secure, isolated environments to remotely access authorized end devices. Each VDI is non-persistent—it is created for a specific session duration and automatically destroyed afterward, ensuring a clean and secure workspace for every use.


Virtual Desktop Reservation

A temporary assignment of a Virtual Desktop to a specific user. When a reservation is made, the user’s unique access profile is applied, and the desktop is locked for use by that user only. The Virtual Desktop remains available for the duration of the reservation, after which it is deleted. A new desktop is then automatically rebuilt and added back to the Stack.


Wicket

A virtual or hardware appliance that links a Facility to a Dispel Region. It acts as a bridge between on-site networks and Dispel’s remote access infrastructure, allowing users to reach end authorized devices via Dispel.

Facility Admin Quick Start Guide

The core tasks for a Facility Admin: manage members, set device ACLs, grant and manage access windows, apply changes in bulk with groups, and connect to devices.

A Facility Admin manages everything inside a single facility: its members, the devices those members can reach, and the access windows that let them connect.

This guide covers those tasks in the order you'll usually do them, from adding your first member to connecting to a device yourself. Each step links to a full how-to.

Add and manage facility members

Everyone who needs a device ACL or an access window has to be a member of the facility first. From Facilities, open the facility and go to its Groups and Members tab to add a member, change a member's facility role, or remove someone from the facility.

To add a member, select Add members, enter the person's email, and select Add this user. If the email matches someone who already has an account in your organization, they're added to the facility right away. If it doesn't, the person receives an email invitation, creates their Dispel account from it, and is added to the facility once that account exists.

Add a User to a Facility

Grant device access with ACLs

A device ACL gives a user access to specific protocol-and-port combinations on a device. Assign ACLs from a device's Remote Access tab when you're granting many users access to one device, or from a user's Devices tab when you're granting one user access to many devices.

Each combination shows as a pill, for example TCP (443), that turns green once it's granted. A user appears in a device's access list after they join the facility that contains the device, and the device's protocols and ports have to be configured before you can grant access to them.

Device access (ACLs)

Create and manage access windows

Depending on your organization's settings, users may need an active access window before they can connect. From Access Windows, select Create Access Window, then choose a facility, a schedule, the members or groups it covers, and the devices, protocols, and ports they can reach. Because you're creating the window rather than requesting it, it opens in Approved status right away instead of waiting for approval, and its members get access for the scheduled period.

Open a window later to rename it, change its schedule, add or remove the users and groups it reaches, or revoke it to end access.

Create an approved access windowManage an access window

Apply changes in bulk with facility groups

When several people need the same facility role, the same device ACLs, or the same access window, a facility group lets you set it once and apply it to everyone in the group. From Member Groups, select Add Group, then Add Facility Group. Add members by selecting organization members or pulling in an organization group, then assign the group's facility role, device ACLs, and access windows from its Permissions, Access, and Access Windows tabs.

Facility Groups

Connect to a device yourself

You can reach devices the same way your users do. Reserve a virtual desktop from a stack and connect with the RDP file or in the browser, or start a Browser Connect session from a device. Depending on your organization's settings, reserving a desktop or opening a session can require an active access window.

Reserve a Virtual Desktop (Admin)Connect to a Browser Connect Session (Admin)

Dispel Application

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Quick Connect

Choose the default connect experience non-admin users see in a region and control which connection links are offered.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Dashboard

One powerful overview into your global operations

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Add a User to a Facility

Add a member to a facility, change the facility role they hold, or remove them. A user must belong to the facility before you can grant them device ACLs or access windows there.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Add devices

Add devices to Dispel so you can grant users remote access to them — one at a time from a form, or many at once from a CSV file.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Manage access request approvers

Set who reviews and approves access requests for a facility, choose who gets an email when a request comes in, and understand what happens when a facility has no approvers.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Enable Browser Connect for a region

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Virtual Desktops

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Org Admin Quick Start Guide

The first-run path for an Organization Admin: set up your account and MFA, push a subnet, build a facility and a device, grant access, and verify a first connection.

As an Organization Admin, you set up the deployment everyone else connects through. This guide follows the path from your first sign-in to a working connection, in the order each piece depends on the one before it. After you sign in, you land on the dashboard, which summarizes your users, regions, facilities, Wickets, and devices alongside facility health and active sessions.

The Dispel dashboard for Acme Corp showing user, region, facility, Wicket, and device counts alongside facility health, an activity heatmap, and active sessions

Step 1: Set up your account and MFA

Start from the invitation Dispel sends to your email. Create your account, set a password, and register a multi-factor method to reach the dashboard.

Create a Dispel Account

Step 2: Understand your regions and Wickets

A region is the remote-access network your facilities live in, and a Wicket is the appliance that connects a facility to that region. As an Organization Admin you set up both yourself. Your role can create regions and Wickets, so you provision them rather than arranging each one with Dispel. Review how they fit together before you build on top of them.

Deployment Infrastructure

Step 3: Push a subnet to a Wicket

Assign the subnet to its Wicket in CIDR notation. Push the subnet before you add devices in it, so those devices are reachable through the Wicket.

Subnet Management

Step 4: Create a facility

A facility organizes the users and devices within a region. Open Facilities, click Create New Facility, then choose a region and enter a facility name.

Facilities

Step 5: Create a device

Add the device under its facility, and set the ports and protocols people will reach it on. Those ports and protocols are what you grant in a device ACL.

Add devices

Step 6: Enable a connection method

Choose how people reach the device. Build a Virtual Desktop stack for the region, or enable Browser Connect for the region and then turn it on per device.

StacksEnable Browser Connect for a region

Step 7: Invite a user

Add the person who will connect by inviting them to the organization. Their role sets the organization permissions they start with.

Invite a User

Step 8: Add the user to a facility

Add the user to the facility their device lives in. Adding them to the facility first lets you grant device ACLs and include them in an access window there.

Add a User to a Facility

Step 9: Set device ACLs

Grant the user access to the device on a per-port, per-protocol basis, so they reach only what you intend.

Device access (ACLs)

Step 10: Create an access window

If your organization requires an access window to connect, create one for the facility. As an administrator you create the window directly, and the members you add get access for the period you schedule.

Create an approved access window

Step 11: Verify a first connection

Confirm the path end to end by connecting yourself. Reserve a Virtual Desktop, or launch a Browser Connect session, and reach the device.

Reserve a Virtual Desktop (Admin)Connect to a Browser Connect Session (Admin)

Where to go next

To manage many people at once, assign devices and access windows through organization and facility groups. To govern how people sign in, set up the Policy Builder.

About Dispel

What the Dispel Zero Trust Engine is, why access works the way it does, and how a connection reaches a device inside an OT network.

Dispel delivers security that makes industrial operations run faster.

The Dispel Zero Trust Engine securely connects people, systems, and operational data across complex OT environments. It replaces the static VPNs, jump servers, and unmanaged vendor pathways industrial sites have relied on: operators, OEMs, contractors, and engineers reach the systems they need through a brokered connection that is scoped to a time window and recorded, with no standing path left open into the OT network.

This page covers what the platform is made of and how a connection reaches a device. For the vocabulary used throughout this documentation, see Key Terminology.

Why access works this way

Every OT security program serves three groups that want different things. Security wants the tightest controls. Operations needs production to keep moving. Compliance needs to prove the controls work.

When the tooling doesn't serve all three, people work around it. A vendor asks a plant operator for shared credentials because signing in is too hard. An engineer is locked out because corporate SSO doesn't reach the local directory. A contractor routes around the approved path because onboarding takes four days. The program looks sound on paper while a dozen private tunnels run underneath it.

Dispel is built so the secure path is also the fastest one. Much of what the rest of this documentation describes follows from that goal — why access is granted for a window instead of standing open, why vendors can onboard themselves, why the network pathway is rebuilt between sessions.

The platform

The Dispel platform between users and an OT network: the Tiered Connection Suite on the left, a Region running Moving Target Defense with Virtual Desktop stacks and Browser Connect intermediates in the middle, and a Wicket bridging into the Purdue model levels on the right, with Dispel Intelligence, Compliance, and the security ecosystem alongside

Users connect through a Region, which brokers the session and hands it to a Wicket at the site. The Wicket sits at the OT DMZ boundary and reaches down into the cells where the equipment lives, so a connection arrives at the device without the user's machine ever joining the OT network.

Part of the platform
What it does
Where it's documented

Tiered Connection Suite

Matches the access method to the work: clientless Browser Connect for quick vendor sessions, an isolated Virtual Desktop for engineering work, and the Dispel Application for legacy and proprietary tooling.

Access windows

Grant access to a facility for a set period and a chosen set of users or groups, by approval or by request.

Dispel Intelligence

Scores and records what happens inside a session — identity, device, and behavior — from sign-in through disconnect.

,

The platform is interoperable with existing OT systems across all 65,000+ TCP/IP protocols, including SSH, RDP, and VNC. Proprietary environments such as Rockwell FactoryTalk, Siemens TIA Portal, and Mitsubishi GX Works require a translator. Session and asset risk signals exchange with the OT security tools you already run — Nozomi Networks, Dragos, Armis, Forescout, and TXOne Networks among them. See Integrations.

How your environment is organized

Your organization nests into layers, and the same layering scopes roles and permissions.

Layer
What it is

Region

A Dispel-hosted remote-access network for a geographic area, kept separate from every other Region.

Facility

One site inside a Region — a plant, substation, or network segment — along with the devices you reach there.

Wicket

The hardware or software appliance at the site that links a facility to its Region.

End device

The OT asset you work on, reached from inside its facility.

For how a deployment is built and what each component does, see Deployment Infrastructure.

How a connection reaches a device

  1. Sign in at app.dispel.com. This is where you request access, launch connections, and — if you administer the organization — manage it.

  2. Hold an access window. An access window covers a facility, a period of time, and a set of users or groups. Without one for the facility, no connection method reaches a device there.

  3. Launch a connection method. Reserve a Virtual Desktop, open a Browser Connect session, or connect through the Dispel Application. Each routes you through the Region.

  4. Reach the device. Traffic relays from the Region across the Wicket to the device. Which devices you reach, over which ports and protocols, comes from .

  5. Access ends with the window. When the access window closes it stops granting access to that facility, whichever connection method you used. A Virtual Desktop is additionally destroyed once you're finished with it.

What Dispel provisions and what you register

The network a Region runs on is built by Dispel's infrastructure as part of your deployment. An organization administrator can add a Region later from the app by naming it and choosing a hosting location; it shows a building state until the network is ready. Everything inside a Region — facilities, Wickets, devices, and users — your team registers and manages.

Next steps

  • Getting Started with Dispel — set up your organization and make a first connection.

  • Key Terminology — definitions for the terms on this page.

  • Access Windows — grant and request time-boxed access.

  • Connection Methods — choose between Virtual Desktops, Browser Connect, and the Dispel Application.

Dispel Compliance

Evaluates the platform's live configuration against framework baselines and builds the evidence as you operate.

Dispel Identity

Establishes who is connecting before access begins, rather than trusting the credential alone.

Topology

One live view of every region, facility, Wicket, and device, with pathway health.

access rules (ACLs)
Connection Methods
Access Windows
Session Forensics
UEBA
Compliance
Dispel Identity
Topology

Password vault

Store a device's login credentials in a dedicated vault so members open pre-authenticated sessions through desktop shortcuts without ever seeing the password.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Invite a User

Invite people to your organization one at a time, and resend or revoke a pending invitation.

Roles & Permissions

File shares

Set up a file share on a device so it can back uploads, downloads, and automated file transfers.

Periodic Authentication Challenge

Confirming your password before you change how you sign in.

Sign in to continue →

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Device findings

Read a device's risk score, asset intelligence, and security findings on the Findings tab, and refresh them from your connected security integrations.

Upload & download files

Set which protocols a device accepts for file uploads and downloads, then send and retrieve files with a live progress and safety-scan view.

Sign in to Dispel

Sign back in to Dispel with email and password, single sign-on, or Active Directory, and finish any multi-factor step your organization requires.

Policy Builder

Define who gets challenged for MFA when signing in to Dispel, which factors they must use, and whether certain users are blocked or allowed through.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Sign in to continue →
Sign in to continue →
Sign in to continue →
Sign in to continue →

Supported Frameworks

Dispel Compliance supports a wide range of frameworks.

Dispel ships with the following framework catalogs and profiles. New frameworks are added in subsequent releases.

Framework
Profile / Baseline
Notes

NIST SP 800-53 Rev 5

Low, Moderate, High, Privacy

Full control catalog including control enhancements

NERC CIP

Versions currently in effect

Organization Groups

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Device access (ACLs)

Grant users per-user, per-protocol access to a device from the Remote Access tab's Access Rules list, and save the changes back to your infrastructure.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Prepare Windows for SMB

Prepare a Windows device so operators can upload files to it and download files from it over SMB.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Reset your password

Reset a forgotten Dispel password, change it while signed in, and get through the password prompts your organization's policies can trigger at sign-in.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Groups

Authenticators

How Dispel aligns its authentication architecture with NIST SP 800-63B and provides verifiable evidence of compliance across AAL1–AAL3.

Users

Manage everyone in your organization from one roster — members, pending invitees, and shared accounts — and set what each person can do.

UEBA Baselines Dashboard

Mapped to NIST 800-53 for cross-framework reconciliation

NIS2

Implementing Regulation (EU) 2024/2690

Dispel-authored OSCAL catalog cross-walked to NIST 800-53

NIST Cybersecurity Framework (CSF) 2.0

Core

Subcategory-level coverage

SANS 5 Critical Controls

Core

High-priority control set for rapid posture assessment

IEC 62443-3-3

SL1 - 4, Baseline

Dispel-authored OSCAL catalog cross-walked to IEC 62443-3-3

A note on the NIS2 catalog

The EU NIS2 Directive does not have an OSCAL catalog published by ENISA or any other authoritative body. Because NIS2 is the regulatory regime several Dispel customers are now reporting against, Dispel publishes a first-party OSCAL catalog derived directly from the legal text — Implementing Regulation (EU) 2024/2690 — which contains the operational cybersecurity risk-management measures that competent authorities check against during a NIS2 audit.

Always consult your own regulatory and compliance team to ensure you are complying with NIS2. Our catalog is an interpretation and does not constitute legal or regulatory advice. You are solely responsible for ensuring your compliance with all applicable laws and regulations.

The Dispel NIS2 catalog is cross-walked to NIST SP 800-53 using the mapping table published by ENISA in its Technical Implementation Guidance on Cybersecurity Risk Management Measures. This means evidence collected for any 800-53 control automatically contributes to the corresponding NIS2 measure, and vice versa — there is no separate evidence pipeline to maintain. Auditors and competent authorities receive a NIS2-shaped OSCAL Component Definition that traces every measure back to the Implementing Regulation article it implements.

If ENISA publishes an official NIS2 OSCAL catalog in the future, Dispel will adopt it and migrate existing assessments without loss of history.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Sign in to continue →
Sign in to continue →
Sign in to continue →
Sign in to continue →

Session Forensics - Risk Factor Analysis

Understand how Dispel calculates user event risk factors.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Data Backup & Recovery

Dispel's approach to data storage, retention, and recovery is engineered to provide robust security and operational resilience. Utilizing a combination of encrypted storage solutions, automated backup mechanisms, and geographically distributed redundancy, we aim to protect your data against unauthorized access and data loss. This documentation outlines the technical details of how these systems work, the policies that govern them, and the procedures to follow in case of data recovery needs.

Data Locations

Dispel clients can choose from one of two data residency locations:

Dashboard Type
Location
Plans

Dispel - US

United States

SaaS

Dispel performs automatic backups of all customer and system data to protect against catastrophic loss due to unforeseen events that impact the entire system. An automated process will back up all data to storage that is resilient against events that impact an entire availability zone. By default, data will be backed up at least once every 24 hours. The backups are stored in an encrypted data storage archive. Backups are monitored and alerted.

All databases managed by Dispel provide continuous protection by persisting snapshots, base backups and WAL files to object store. Also, fork and follower databases are implemented by fetching snapshots or persistent base backups and WAL files and replaying them on a fresh Postgres installation. Storing these physical backups in a highly available object store also enables us to recover entire databases in the event of hardware failure, data corruption or a large scale service interruption. By default, Dispel sub-processor object stores provides durable infrastructure to store important data and is designed for durability of 99.999999999% of objects.

Dispel makes complete database backups. Transactions committed to the database are recorded as WAL files, which are able to be replayed on top of the snapshots or base backups, providing a method of completely reconstructing the state of a database. Snapshots are stored directly in object store. Base backups and WAL files are pushed to the object store through an application called WAL-E as soon as they are made available by Postgres.

Databases can be restored from backups from a cold state or synced with an existing database. These are known, respectively, as fork and following processes. Dispel can also rollback to an earlier database backup.

In all cases, a new database instance (N2) is created, brought in parallel to the existing database (N1), and then promoted to the primary database for the API. This is demonstrated in the following process diagram showing a database fork data restoration:

Our platform automatically restores Postgres databases in the case of an outage. The Dispel platform is designed to dynamically deploy applications within the cloud, monitor for failures, and recover failed platform components including customer applications and databases.

Production databases run on Amazon Aurora (RDS) with automated backups configured for a rolling 30-day retention window, providing continuous point-in-time recovery (PITR) to any second within the most recent 30 days. Automated backups include daily snapshots and transaction logs stored in Amazon S3, all KMS-encrypted with access restricted to authorized operators. Logs may be retained up to one year or longer to support compliance, auditing, and forensic investigation requirements.

Clients may request a copy of their data for export and archival. Dispel uses the native pg_dump PostgreSQL tool to create its backup files, making it easy to export to other PostgreSQL installations. The resulting backup file uses the custom format option in pg_dump. As compared to the plain-text format, the custom format options result in backup files that can be much smaller.

Client data belongs to clients; Dispel data belongs to Dispel. For more information on how Dispel handles client data please review our .

Reading a Session Forensics Export

The Export as JSON button on a Session Forensics event downloads the whole event record as a json file. This page is a field reference for that file.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Logs

Investigate activity across your organization with the activity log, monitor live Browser Connect utilization, and play back recorded sessions.

Audiences

Define named groups of users for your sign-in policy. Use existing Dispel groups, facility groups, or build custom audiences with your own membership rules.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Sign in to continue →

Dispel - EU

Europe

SaaS, Private Cloud

Data Backup

Backup Types

Data Restoration

Disaster Recovery / Business Continuity

Backup Retention Limits

Data Export / Archival

Data Ownership

Privacy Policy

PingIdentity

Use PingIdentity as your identity provider for federated single sign-on, so users access Dispel with their existing enterprise credentials over OAuth (OIDC) or SAML.

Overview

Connect PingIdentity — Ping's federated identity platform — as your organization's identity provider. Once connected, your users sign in to Dispel with their existing enterprise credentials through single sign-on. You can connect Ping over OAuth (OIDC) or SAML.

This page covers the Ping-specific setup. For the shared behavior that applies to every provider — how users sign in, group mapping, MFA, and disconnecting — see Identity Providers.

Where to find it. Sign in as an organization administrator and open Settings → Integrations (or the dedicated Settings → Authentication page). PingIdentity appears in the Identity & Authentication (IdP / SSO) section. Click Connect on its card to begin.

Before you begin

  • You'll configure the IdP side in your Ping environment — PingOne or PingFederate — so you'll need administrative access there.

  • Decide on a protocol — OAuth (OIDC) or SAML. See Choosing a protocol.

  • Make sure the users who will sign in via Ping are already invited to your organization in Dispel. SSO authenticates users but doesn't create access on its own.

  1. In your Ping environment, create a new OIDC / Web application for Dispel.

  2. Set the redirect URI to your Dispel address followed by /oauth/login-callback — for example https://app.dispel.com/oauth/login-callback. Confirm the exact address for your environment with your Dispel representative if you're unsure.

  3. Generate a client secret for the application.

  1. Click Connect on the PingIdentity card and Select Authentication Protocol → OAuth.

  2. Fill in the fields:

Field
Value from PingIdentity
  1. Click Save settings.

  1. In your Ping environment, create a new SAML application for Dispel.

  2. In the SAML configuration, paste the values Dispel shows at the top of its SAML form:

    • ACS URL / Assertion Consumer Service URL ← Dispel's Assertion Consumer Service URL.

    • Entity ID / Audience ← Dispel's Service Provider (SP) Entity ID.

  1. Click Connect on the PingIdentity card and Select Authentication Protocol → SAML.

  2. Copy the Service Provider (SP) Entity ID and Assertion Consumer Service URL shown at the top of the form (use Copy ID / Copy URL) into Ping, as above.

  3. Fill in the fields:

Field
Value from PingIdentity
  1. Click Save settings.

  2. Click Test connection. Dispel redirects you to Ping to sign in, then shows the email and name it received. If the test fails, confirm the values match your Ping application and that the test user is invited to your organization.

  • Users sign in by entering your Organization Identifier on the Dispel sign-in screen and authenticating with Ping. See .

  • MFA enforced in Ping applies during sign-in; Dispel's email one-time codes don't apply to SSO users. See .

  • To switch protocols or providers, disconnect first. See .

Scheduled file transfers

Set up an automated, scheduled file transfer that moves or copies files from a source facility to a destination facility over Dispel's network, then accept or deny it at the destination.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Reading a UEBA Baselines Export

The Export as JSON button on the UEBA Baselines page downloads the org's baseline state as a json file. This page is a field reference for that file.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Manage a User

Open a person's detail page to change their role, reset MFA, block or restore sign-in, review permissions, and archive or remove them.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Account Recovery & MFA Reset

Reset a member's multi-factor authentication and restore access to locked-out accounts, including an Organization Admin who cannot sign in.

Sign-in Policy Builder

Build sign-in rules for your organization — connect audiences to MFA rulesets, add conditions, configure a default, and publish.

Roles & Capabilities

What each Dispel role can do across your organization, its regions, and its facilities.

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

This page requires authentication

This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

Sign in to continue →

Note the application's Client ID, client secret, and your Ping OAuth/OIDC issuer endpoint.

From the Ping application's SAML / connection details, collect:

  • The Single Sign-On Service URL → Dispel's SSO URL.

  • The IdP Entity ID / Issuer → Dispel's Identity Provider Entity ID.

  • The signing certificate → Dispel's Base64 Signing Certificate.

  • Grant the application to the users or groups who should have access.

  • Client URL

    Your Ping OAuth/OIDC issuer endpoint (where tokens are issued).

    Client ID

    The application's Client ID.

    Client Secret

    The application's client secret.

    Organization Identifier

    A unique identifier you choose; users type it on the sign-in screen.

    SSO URL

    The Single Sign-On Service URL.

    Identity Provider Entity ID

    The IdP Entity ID / Issuer.

    Base64 Signing Certificate

    The Ping signing certificate. Paste it or use Upload Certificate.

    Organization Identifier

    A unique identifier you choose; users type it on the sign-in screen.

    One provider at a time. If your organization is already connected to another identity provider, disconnect it before connecting PingIdentity.

    Connect with OAuth (OIDC)

    In PingIdentity

    In Dispel

    Connect with SAML

    In PingIdentity

    In Dispel

    After connecting

    Frequently asked questions

    Does this work with both PingOne and PingFederate?

    Yes. Create an OIDC or SAML application in whichever Ping product you use, then enter its values in Dispel. The Dispel-side fields are the same either way.

    Which protocol should I use with Ping?

    Either works. Use whichever matches the application you create in Ping — an OIDC application for OAuth, or a SAML application for SAML.

    My SAML test connection failed. What should I check?

    Confirm the SSO URL, IdP Entity ID, and certificate match your Ping application, that you pasted Dispel's SP Entity ID and ACS URL into Ping's SAML configuration, and that the test user is granted access to the Ping application and invited to your Dispel organization.

    How users sign in
    SSO and multi-factor authentication
    Switching or disconnecting a provider
    Sign in to continue →
    Sign in to continue →
    Sign in to continue →

    Microsoft Entra ID

    Use Microsoft Entra ID (formerly Azure AD) as your identity provider so users sign in to Dispel with their Microsoft credentials over OAuth (OIDC) or SAML.

    Overview

    Connect Microsoft Entra ID — Microsoft's cloud identity platform, formerly known as Azure AD — as your organization's identity provider. Once connected, your users sign in to Dispel with their Microsoft credentials through single sign-on. You can connect Entra over OAuth (OIDC) or SAML.

    This page covers the Entra-specific setup. For the shared behavior that applies to every provider — how users sign in, group mapping, MFA, and disconnecting — see Identity Providers.

    Where to find it. Sign in as an organization administrator and open Settings → Integrations (or the dedicated Settings → Authentication page). Microsoft Entra ID appears in the Identity & Authentication (IdP / SSO) section. Click Connect on its card to begin.

    Before you begin

    • You'll configure the IdP side in the Microsoft Entra admin center (or Azure portal), so you'll need administrative access there.

    • Decide on a protocol — OAuth (OIDC) or SAML. See Choosing a protocol.

    • Make sure the users who will sign in via Entra are already invited to your organization in Dispel. SSO authenticates users but doesn't create access on its own.

    1. In the Microsoft Entra admin center, go to App registrations → New registration and create an app for Dispel.

    2. Add a the following 2 Web redirect URIs for your Dispel environment

      • /oauth/login-callback — (e.g.https://app.dispel.com/oauth/login-callback).

    1. Click Connect on the Microsoft Entra ID card and Select Authentication Protocol → OAuth.

    2. Fill in the fields:

    Field
    Value from Entra
    1. Click Save settings.

    1. In the Microsoft Entra admin center, go to Enterprise applications → New application → Create your own application, then open Single sign-on → SAML.

    2. In Basic SAML Configuration, paste the values Dispel shows at the top of its SAML form:

      • Identifier (Entity ID) ← Dispel's Service Provider (SP) Entity ID.

    1. Click Connect on the Microsoft Entra ID card and Select Authentication Protocol → SAML.

    2. Copy the Service Provider (SP) Entity ID and Assertion Consumer Service URL shown at the top of the form (use Copy ID / Copy URL) into Entra, as above.

    3. Fill in the fields:

    Field
    Value from Entra
    1. Click Save settings.

    2. Click Test connection. Dispel redirects you to Entra to sign in, then shows the email and name it received. If the test fails, confirm the values match your Entra app and that the test user is invited to your organization.

    • Users sign in by entering your Organization Identifier on the Dispel sign-in screen and authenticating with Microsoft. See .

    • Map Entra groups to Dispel groups so membership stays in sync — see .

    • MFA enforced in Entra applies during sign-in; Dispel's email one-time codes don't apply to SSO users. See .

    • To switch protocols or providers, disconnect first. See .

    Protocols & ports

    View and manage the protocols and ports a device accepts connections on — the list that device Access Rules (ACLs) draw from.

    This page requires authentication

    This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

    /client-app-launcher/oktaauth.dispel.io — (e.g. https://app.dispel.com/client-app-launcher/oktaauth.dispel.io).

  • Confirm the exact address for your environment with your Dispel representative if you're unsure.

  • Under Certificates & secrets, create a client secret and copy its value.

  • Note your Application (client) ID and your tenant's OAuth/OIDC endpoint.

  • Reply URL (Assertion Consumer Service URL)
    ← Dispel's
    Assertion Consumer Service URL
    .
  • From the Entra SAML setup, collect:

    • Login URL → Dispel's SSO URL.

    • Microsoft Entra Identifier → Dispel's Identity Provider Entity ID.

    • Download the Certificate (Base64) → Dispel's Base64 Signing Certificate.

  • Client URL

    Your tenant's OAuth/OIDC endpoint (where tokens are issued).

    Client ID

    The Application (client) ID from your app registration.

    Client Secret

    The client secret value you created.

    Organization Identifier

    A unique identifier you choose; users type it on the sign-in screen.

    SSO URL

    The Entra Login URL.

    Identity Provider Entity ID

    The Microsoft Entra Identifier.

    Base64 Signing Certificate

    The downloaded Base64 certificate. Paste it or use Upload Certificate.

    Organization Identifier

    A unique identifier you choose; users type it on the sign-in screen.

    One provider at a time. If your organization is already connected to another identity provider, disconnect it before connecting Entra.

    Connect with OAuth (OIDC)

    In Microsoft Entra ID

    In Dispel

    Connect with SAML

    In Microsoft Entra ID

    In Dispel

    After connecting

    Frequently asked questions

    Is this the same as "Azure AD"?

    Yes. Microsoft renamed Azure Active Directory to Microsoft Entra ID. If your Entra console still shows "Azure AD" labels in places, the setup is the same.

    Which protocol should I use with Entra?

    Either works. Use whichever matches how your Entra app is configured — an OIDC app registration for OAuth, or an enterprise application with SAML single sign-on for SAML.

    My SAML test connection failed. What should I check?

    Confirm the SSO URL, Entity ID, and certificate match your Entra SAML app exactly, that you pasted Dispel's SP Entity ID and ACS URL into Entra's Basic SAML Configuration, and that the test user exists in Entra and is invited to your Dispel organization.

    How users sign in
    Group Mapping
    SSO and multi-factor authentication
    Switching or disconnecting a provider
    Sign in to continue →

    Session Recordings

    Find a recorded Browser Connect or virtual desktop session, play it back, jump to the moments that matter, and share a link to an exact point in it.

    Manage a device

    Open the device panel to review and edit a device's attributes, reach its Remote Access, Findings, and File Transfer settings, or delete it.

    This page requires authentication

    This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

    This page requires authentication

    This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

    Invite Links

    Create a link that lets people sign themselves up to your organization by matching email domain, and choose the group new members join.

    Sign in to continue →
    Sign in to continue →

    This page requires authentication

    This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

    MFA Rulesets

    Create reusable definitions of which authentication factors satisfy an MFA challenge, then reference them from your sign-in policy rules.

    Sign in to continue →

    This page requires authentication

    This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

    Sign in to continue →

    Compliance

    Automated audit readiness with Dispel for NERC CIP, NIST 800-53, and NIS2 controls.

    Compliance & Audit Readiness Overview

    The Compliance module turns Dispel into a continuous, evidence-backed control assessment of how Dispel implements security controls on your behalf. Instead of preparing for an audit by collecting screenshots and spreadsheets in the weeks beforehand, your GRC team can pull a current, timestamped view of where your organization stands against the frameworks that matter — at any time, in formats your auditors already accept.

    Compliance is built on the Open Security Controls Assessment Language (OSCAL) specification published by NIST. Every catalog, profile, control implementation statement, and assessment record produced by Dispel is structured according to OSCAL 1.1.2 — so the artifacts you export are machine-readable, framework-neutral, and portable into whatever GRC platform your organization uses to assemble its full System Security Plan (SSP).

    Key benefits

    • Inherited controls, proven continuously — Dispel evaluates its own implementation of each in-scope control against your tenant’s live configuration, so the evidence supporting your inheritance claim is always current and timestamped.

    • One vocabulary per audit — Choose the framework your organization reports against and Dispel re-expresses its coverage in that framework’s terms. The same underlying evidence supports NIST 800-53, NERC CIP, NIS2, and NIST CSF simultaneously.

    • Auditor-ready Component Definition — Export an OSCAL Component Definition: the standard artifact for documenting a single component’s contribution to a customer’s SSP. Auditors and GRC platforms accept it as the authoritative inheritance package for Dispel.

    • Executive PDF report — A concise narrative summary showing which controls you can claim from Dispel today, which are partial, and what configuration changes would close the remaining gaps in Dispel coverage.

    • Configuration impact simulation — Before changing a Dispel setting, see exactly which inherited controls would move from partial to fully implemented (or the reverse). Use this to prioritize internal configuration changes that strengthen your inheritance posture.

    • Permanent evidence trail — Every assessment captures a timestamped snapshot. During an audit window you can demonstrate that Dispel’s coverage was in place continuously, not just on the day of the audit.

    The Compliance module is designed for the people inside your organization who answer the question “what does Dispel cover for us?” during your own audits:

    • GRC analysts assembling SSPs and audit responses for NERC CIP, NIST 800-53, NIST CSF, NIS2, SANS, or internal control frameworks, who need to know what they can inherit from Dispel.

    • CISOs and security directors reporting compliance posture to executive leadership, boards, and regulators, and accounting for vendor inheritance in that posture.

    • Internal auditors verifying that the controls your organization claims to inherit from Dispel are actually implemented in your Dispel tenant.

    • Operations leadership at organizations subject to multiple, overlapping regulatory regimes who want a single source of truth for the Dispel portion of every audit.

    Create a Dispel Account

    Dispel account creation is the first step in connecting to your site through Dispel. In order to create a Dispel account, you must have received an invitation via email or have been provided an invite link from an admin within your Dispel deployment.

    1

    To create a Dispel account, you must first be invited to an organization. You will receive an invitation via email, as seen below, or be provided an invite link by an admin. Click Verify Email or open the invite link you have been sent.

    2

    Select your desired language.

    3

    Who Compliance is for

    Tap Continue to set your name.

    4

    Input your name.

    5

    Tap Continue to set your password.

    6

    Input the desired password for Dispel twice.

    7

    Check to acknowledge Dispel's Privacy Policy and Data Subject Consent Form.

    8

    Tap Set new password.

    9

    If your organization requires multi-factor authentication (MFA), you will now be prompted to set up MFA you are able to either Set up MFA device or Set Up Security Key. If your organization does not require MFA, your account is now fully set up, and you will be brought to the Dispel dashboard.

    10

    Set up MFA device

    Tap Set up MFA device.

    11

    Save the recovery codes by tapping Download as .txt or Copy to clipboard, then save the recovery codes somewhere safe.

    Recovery codes will allow you to temporarily bypass MFA to sign into your account in the future.

    12

    Once you have saved the recovery codes, tap I saved them, show me the next step.

    13

    In your MFA application device of choice, either scan the QR code or input the text secret.

    Some standard two-factor authentication apps include , Microsoft Authenticator, or .

    14

    Input the 6-digit code displayed on MFA device.

    15

    Tap Set up MFA device.

    You must tap Set Up MFA device before the code inputted from your MFA device expires.

    16

    Tap Continue. Your account is now fully set up, and you will be brought to the Dispel dashboard.

    17

    Set Up Security Key

    Tap Set up Security Key.

    18

    Save the recovery codes by tapping Download as .txt or Copy to clipboard, then save the recovery codes somewhere safe.

    Recovery codes will allow you to temporarily bypass MFA to sign into your account in the future.

    19

    Once you have saved the recovery codes, tap I saved them, show me the next step.

    20

    Input a name for the device you will be using as a security key.

    21

    Tap Add new key.

    22

    Plug in and activate your key. Follow the steps to register your security key.

    23

    Tap Continue. Your account is now fully set up, and you will be brought to the Dispel dashboard.

    Overview

    Create a Dispel Account

    Next Steps

    Request an access window
    Connection Methods

    Getting Started

    Automated audit readiness with Dispel for NERC CIP, NIST 800-53, and NIS2 controls.

    Getting started

    Producing a Dispel Compliance package is a four-stage workflow:

    1. Select the framework(s) your organization reports against.

    2. Assess Dispel’s coverage against your tenant’s current configuration.

    3. Review which controls Dispel covers, identify any gaps in coverage, and use the simulator to plan configuration changes that close them.

    4. the OSCAL Component Definition and PDF report and hand them to your GRC team or auditor.


    Selecting a framework tells Dispel which control vocabulary to express its coverage in. Most organizations select the framework their auditor or competent authority works from. You can have multiple frameworks active at once — useful when the same Dispel deployment is audited against more than one regulatory regime.

    1. In the left sidebar, navigate to Settings.

    2. Open the Compliance tab.

    3. Click Add Framework.

    4. Select a catalog (e.g., NIST SP 800-53 Rev 5).

    The framework appears in your active frameworks list immediately. Dispel begins evaluating its coverage in the background and the dashboard populates as evaluators complete.

    Removing a framework

    To remove an active framework, click the trash icon next to it in the active frameworks list. Removing a framework deletes its scorecard but does not affect any other active framework or the underlying evidence record. You can easily re-add removed frameworks without losing any of your history.


    Automated assessment

    Dispel ships with a library of control evaluators that check whether Dispel — given your tenant’s current configuration — implements each in-scope control. For example: is MFA enforced on this tenant, is session recording enabled, does the password policy meet the framework threshold, and are vendor attestations on file. Each evaluator maps to one or more controls in each active framework.

    To run an assessment:

    1. Navigate to Settings > Compliance.

    2. Open the framework you want to assess.

    3. Click Run Assessment.

    Assessment results are stored with a timestamp. Each control receives one of the following statuses, which describes Dispel’s implementation of that control on your tenant:

    Status
    Meaning

    The Compliance dashboard is your day-to-day workspace for understanding what Dispel covers on your tenant and where coverage can be improved.

    Scorecard

    Each active framework has a scorecard showing the percentage of in-scope controls Dispel currently implements on your tenant. Partial credit is given when only some sub-controls or enhancements are implemented. Hover any number for the underlying breakdown.

    Sunburst chart

    The hierarchical sunburst visualization shows Dispel’s coverage at a glance: framework → control family → individual control. Implemented (inheritable) controls render in green; failed (not currently inheritable) in red; unassessed in grey. Click any segment to drill into the control detail page.

    Control detail page

    Selecting a control surfaces:

    • Status — Dispel’s current and historical implementation of the control on this tenant

    • Evidence — the specific evaluators that contributed to the status, with timestamps and the underlying values they observed

    • Narrative — Dispel’s implementation statement for the control

    • Lineage — every other framework whose controls map to this same evidence (so a single inheritance claim can be expressed in multiple framework languages)

    Configuration impact simulation

    Before changing a Dispel setting on your tenant, use the simulator to predict how coverage shifts:

    1. From the dashboard, view Est. Impact under Recommendations.

    2. Locate one or more Dispel settings in the overlay panel (e.g., Enable MFA for all users).

    3. Compare the projected scorecard to your current scorecard.

    The simulator does not modify any real settings. It is purely a planning tool for sequencing changes that strengthen Dispel inheritance.


    OSCAL Component Definition

    The OSCAL Component Definition is the standardized artifact for documenting a single component’s contribution to a customer’s System Security Plan. For Dispel, that component is your Dispel deployment, and the Component Definition is the authoritative record of what your auditor can credit you for inheriting.

    1. Open the framework’s detail page.

    2. Click Export > OSCAL Component Definition.

    3. A JSON file is downloaded conforming to OSCAL 1.1.2.

    The export includes:

    • The catalog and profile the inheritance claim is expressed in

    • Each in-scope control’s implementation status from Dispel’s side (implemented, partial, not-implemented, not-applicable)

    • Dispel’s implementation narrative for each control

    This file can be imported into eMASS, Xacta, RegScale, FedRAMP and GovRAMP submissions, or any tool that accepts OSCAL — where it sits alongside Component Definitions from your other vendors and your internal SSP content.

    Executive PDF report

    For internal stakeholders and audit cover letters:

    1. Open the framework’s detail page.

    2. Click Export > PDF Report.

    The report contains:

    • An executive summary stating what percentage of in-scope controls you can inherit from Dispel today

    • A framework scorecard

    • Every control Dispel does not currently implement on your tenant, with the configuration change that would restore inheritance

    • The list of evidence sources contributing to the assessment


    Each evaluator run produces an evidence snapshot that is stored with a timestamp. The snapshot records what Dispel observed about its own coverage at that moment.

    Auditors who need to verify a specific moment in time can:

    1. Locate the assessment record for the date in question.

    2. Drill into the evidence snapshot for any individual control.

    3. See the exact values the evaluator observed and the timestamp of observation.


    Dispel covers the security controls that are implemented inside the Dispel platform itself — primarily the remote access, identity, session monitoring, network segmentation, and OT connectivity layers. Controls that depend on Dispel’s own corporate posture (vendor management, supply chain, SDLC, personnel screening) are also covered through Dispel’s published implementation narratives.

    Dispel does not cover controls outside its footprint: physical security at your facilities, endpoint hardening on equipment Dispel does not manage, application development inside your business systems, HR practices at your organization, and so on. Those controls remain entirely with your enterprise GRC tooling.

    The following table summarizes the categories of evidence Dispel produces and the framework control families they typically support. This is illustrative; the authoritative mapping for your active framework is shown on each control’s detail page.

    Evidence category
    Representative NIST 800-53 families
    Representative NERC CIP requirements
    Representative NIS2 measures (Implementing Regulation 2024/2690)

    Universal Controls

    The 45 controls Dispel checks on your tenant, and the settings that decide whether the configurable ones pass.

    Dispel checks your tenant against 45 Universal Controls. Each is based on a NIST SP 800-53 Rev 5 control and mapped to the requirements of every framework you select, so one result counts toward NIST 800-53, NERC CIP, NIS2, and the rest of the . You'll find them in the app under .

    Each control is marked Platform, Configurable, or Shared.

    Platform controls are part of how Dispel is built, such as encrypted tunnels and deny-by-default network access. You inherit them without doing anything.

    Configurable controls depend on your organization's settings. Dispel has the capability, but the control passes only once you've turned it on. The next section lists what each one needs.

    Shared controls are split between Dispel and you. Dispel checks its part, but an auditor will also expect your part: for example, PS-4 Personnel Termination assumes you deactivate people promptly when they leave.

    Control
    Passes when
    Google Duo
    1Password

    Select a profile or baseline (e.g., Moderate). Profiles narrow a catalog down to the subset of controls required at a given impact level.

  • Click Add.

  • Remediation guidance — for failed controls, a description of the Dispel setting or configuration change that would restore inheritance

    Links to the underlying evidence records

    Generation timestamp and the assessor identity

    Session recording and forensics

    AU

    CIP-007, CIP-008

    Incident handling; logging & monitoring

    Configuration and change records

    CM

    CIP-010

    Asset management; change management

    Vendor and supply-chain attestations

    SR, PS

    CIP-013

    Supply-chain security

    Platform attestation and integrity

    SI, SC

    CIP-007, CIP-010

    Vulnerability handling & disclosure; cryptography

    Implemented

    Dispel fully implements this control on your tenant. You may inherit it.

    Failed

    Dispel does not currently implement this control on your tenant — typically because a Dispel setting needs to change. You cannot inherit it as configured.

    Not Assessed

    No automated evaluator runs for this control, or evaluators have not yet completed.

    Not Applicable

    The control falls outside Dispel’s scope (e.g., physical security at your facility) and inheritance from Dispel does not apply.

    Identity, MFA, session lifecycle

    AC, IA

    CIP-004, CIP-005, CIP-007

    Identity & access control; authentication

    Remote access and segmentation

    AC, SC

    CIP-005, CIP-007

    Step 1: Select a framework

    Adding multiple frameworks does not duplicate work. Dispel produces a single set of evidence about its own implementation and re-expresses it through each active framework. Adding NIST CSF on top of NIST 800-53 reuses the same underlying evidence.

    Step 2: Assess Dispel’s coverage

    Assessments are non-destructive and read-only. They observe Dispel’s configuration; they never modify your tenant.

    Step 3: Review coverage and close gaps

    Use the simulator to sequence configuration changes in the order that restores the most inheritable controls first.

    Step 4: Export the inheritance package

    Continuous evidence and audit trail

    What Dispel covers (and what it does not)

    Frequently asked questions

    Does running an assessment change anything on my tenant?

    No. Assessments are read-only. They observe the current state of your Dispel configuration and produce evidence snapshots about Dispel’s coverage. They never modify settings, users, devices, or policies.

    How often should I run an assessment?

    For most organizations, running an assessment after any significant configuration change is sufficient. Some auditors require evidence of periodic assessment (e.g., monthly or quarterly) — schedule assessments to match the cadence your audit program requires. The OSCAL export and PDF report capture the assessment timestamp.

    Can I use Dispel as my full GRC system?

    No. Dispel is the system of record only for the controls Dispel itself implements — the inheritance layer beneath your audit. For controls outside Dispel’s footprint (physical security, HR processes, software development practices, endpoints Dispel does not manage, etc.), the evidence lives in your enterprise GRC platform. The Dispel OSCAL Component Definition is designed to be ingested into that platform as one component among many.

    What does "Not Assessed" mean on a control?

    A control shows Not Assessed when no automated evaluator runs against it yet, or when evaluators have not yet completed. This is distinct from Not Applicable, which means the control falls outside Dispel’s scope and is not part of what you can inherit from Dispel.

    Can I demonstrate NIS2 compliance with Dispel?

    For the portion of NIS2 that Dispel covers, we believe yes. Select NIS2 as an active framework and Dispel produces a Component Definition expressed against the measures in the EU NIS2 Implementing Regulation (2024/2690), cross-walked to NIST 800-53 per ENISA’s Technical Implementation Guidance. Hand it to your competent authority alongside the rest of your NIS2 documentation as the inheritance layer for your remote access, identity, session monitoring, and OT connectivity controls.

    ENISA has not published an official NIS2 OSCAL catalog. The Dispel catalog is authored directly from the legal text of the Implementing Regulation. If ENISA publishes an official catalog in the future, Dispel will adopt it.

    Why do some controls show "Not Applicable"?

    A control is marked Not Applicable when it falls outside Dispel’s footprint and is therefore not something you can inherit from Dispel — for example, controls governing physical access to your facility, hiring practices at your organization, or software development on your internal applications. The N/A determination is recorded in the OSCAL export so your auditor can see exactly which controls were excluded from the Dispel inheritance claim and verify them through other channels.

    What happens to my data if I remove a framework?

    Nothing, it is entirely safe. Removing a framework deletes its scorecard and removes it from the dashboard. Underlying evidence snapshots and control narratives are preserved and become available again if you re-add the framework. No assessment history is destroyed.

    Does the OSCAL export include sensitive tenant configuration?

    No. The Component Definition contains Dispel’s implementation status, narratives, and pointers to evidence — not raw configuration values, credentials, IP addresses, or user data from your tenant. It is safe to share with auditors and to upload to OSCAL-aware GRC platforms.

    Can the same Dispel evidence support more than one framework?

    Yes. This is the core benefit of the OSCAL-based architecture. A single piece of Dispel evidence (e.g., “MFA is enforced on this tenant”) contributes simultaneously to NIST 800-53 IA-2(1), NIST CSF PR.AA-03, NERC CIP-005-7 R2, and any other control that maps to the same evaluator. The same inheritance claim can be expressed in whichever framework language each of your audits requires.

    How do I prove continuous Dispel coverage during an audit window?

    Run an assessment at the start of your audit period and one at the end, and rely on the underlying evidence snapshots between the two. Each snapshot is timestamped, so you can show that your inheritance claim from Dispel was valid for every day of the audit period — not just the day the assessment was generated.

    Can I add my own internal control framework?

    Custom catalog ingestion is on the roadmap. Today, internal frameworks are typically represented by selecting the closest published baseline (e.g., NIST 800-53 Moderate) — Dispel will produce its inheritance evidence in that vocabulary, which your GRC team can then re-map onto the internal framework inside your enterprise GRC platform.

    Export

    Network security; access control policies

    Setting

    IA-2, IA-2(1), IA-2(2)

    Two-factor authentication or SSO is enforced for the whole organization. If you rely on SSO, enforce MFA in your identity provider.

    Require two-factor authentication or Force Organization members to use SSO to authenticate in

    IA-5(1)

    Passwords expire after a maximum lifetime of 1 day or more, or SSO is enforced.

    Enforce password min/max lifetime policy in

    IA-5(1).e

    A set number of previous passwords (1 or more) is remembered, or SSO is enforced.

    Enforce password reuse policy in

    AC-12 (access windows)

    At least one role has to request access windows.

    Any of the Require access windows for Organization … options in

    AU-12

    Regions are allowed to record Browser Connect sessions.

    Allow Regions to record Browser Connect sessions in

    AC-6

    At least one member isn't an Organization Admin.

    After changing a setting, open the control, click the failing assessment objective, and click Run Assessment to update the result.

    AC-7, AC-2(3), and SI-3 are also marked Configurable, but they pass on Dispel's defaults. Dispel rate-limits sign-in attempts and expires idle sessions on its own. Suspend user temporarily if repeated login attempts fail and Enforce inactivity lockout policy in Settings → Security add stricter limits of your own. SI-3 is met by the disposable virtual desktops users connect through.

    • CM-6: at least one compliance framework is selected.

    • CM-7: your Regions have ACL rules. An organization with no Regions passes, since nothing can be reached.

    • CM-8: at least one device is registered, or an asset-discovery integration has synced.

    • AC-2: your organization has members.

    • IA-4: your organization has no . Each account has to belong to one person, so IA-4 fails while any shared account exists. Remediate on its recommendation, Remove Shared Accounts, opens , where each one is tagged Shared Account. Turning off shared accounts in Settings isn't enough: IA-4 counts the shared accounts that still exist.

    • PS-4, IA-8(2), AC-12 (session timeout), and CM-3 pass on what Dispel provides: account disabling and identity-provider deprovisioning; sign-in through SAML, OAuth, OIDC, or Microsoft; session expiry; and a log of every settings change.

    Most Platform controls are checked against how Dispel itself is built. SA-4, SI-2, and IR-8 are checked against Dispel's published support policy, maintenance windows, and technical and organizational measures.

    A control that has never been checked shows Not Yet Assessed until you click Perform Baseline Assessment. After that it shows Passing or Failed. Failed also covers controls that are only partly in place. Controls that don't apply to your selected frameworks show N/A. Checking a control only reads your configuration; it doesn't change it.

    Click any control to see which assessment objectives passed or failed, the evidence behind each one, and the framework requirements it maps to.

    AC-12 and AU-6 each appear twice because Dispel checks two separate things against them.

    Code
    Control
    Type

    AC-2

    Account Management

    Shared

    AC-2(3)

    Disable Accounts

    Configurable

    Who owns each control

    Turn on the Configurable controls

    supported frameworks
    Security → Compliance → Controls

    What the Shared controls check

    How Dispel checks Platform controls

    Statuses

    The full list

    Member roles in Users

    AU-6 (both)

    Your organization has the Session Forensics add-on.

    Ask your Dispel account team

    AC-3

    Access Enforcement

    Platform

    AC-4

    Information Flow Enforcement

    Platform

    AC-6

    Least Privilege

    Configurable

    AC-7

    Unsuccessful Logon Attempts

    Configurable

    AC-11

    Device Lock

    Platform

    AC-12

    Session Termination (session timeout)

    Shared

    AC-12

    Session Termination (access windows)

    Configurable

    AC-17(1)

    Monitoring and Control

    Platform

    AC-17(2)

    Protection of Confidentiality and Integrity Using Encryption

    Platform

    AC-17(3)

    Managed Access Control Points

    Platform

    AC-17(4)

    Privileged Commands and Access

    Platform

    AU-2

    Event Logging

    Platform

    AU-3

    Content of Audit Records

    Platform

    AU-6

    Audit Record Review, Analysis, and Reporting (session forensics)

    Configurable

    AU-6

    Audit Record Review, Analysis, and Reporting (SOC monitoring)

    Configurable

    AU-9

    Protection of Audit Information

    Platform

    AU-12

    Audit Record Generation

    Configurable

    CM-3

    Configuration Change Control

    Shared

    CM-6

    Configuration Settings

    Shared

    CM-7

    Least Functionality

    Shared

    CM-8

    System Component Inventory

    Shared

    IA-2

    Identification and Authentication (Organizational Users)

    Configurable

    IA-2(1)

    Multi-factor Authentication to Privileged Accounts

    Configurable

    IA-2(2)

    Multi-factor Authentication to Non-privileged Accounts

    Configurable

    IA-4

    Identifier Management

    Shared

    IA-5(1)

    Password-based Authentication

    Configurable

    IA-5(1).e

    Password History

    Configurable

    IA-8

    Identification and Authentication (Non-organizational Users)

    Platform

    IA-8(2)

    Acceptance of External Authenticators

    Shared

    IA-11

    Re-authentication

    Platform

    IR-5

    Incident Monitoring

    Platform

    IR-8

    Incident Response Plan

    Platform

    MA-4

    Nonlocal Maintenance

    Platform

    PS-4

    Personnel Termination

    Shared

    SA-4

    Acquisition Process

    Platform

    SC-7

    Boundary Protection

    Platform

    SC-8

    Transmission Confidentiality and Integrity

    Platform

    SC-10

    Network Disconnect

    Platform

    SC-12

    Cryptographic Key Establishment and Management

    Platform

    SC-13

    Cryptographic Protection

    Platform

    SC-23

    Session Authenticity

    Platform

    SI-2

    Flaw Remediation

    Platform

    SI-3

    Malicious Code Protection

    Configurable

    shared accounts
    Users
    Settings → Security
    Settings → Security
    Settings → Security
    Settings → Security
    Settings → Browser Connect

    Identity Providers (SSO)

    Let your users sign in to Dispel with your existing identity provider. Connect Microsoft Entra ID, Okta, or PingIdentity over OAuth (OIDC) or SAML for single sign-on.

    Overview

    Connecting an identity provider (IdP) lets your users sign in to Dispel with the same enterprise credentials they already use everywhere else — single sign-on (SSO). Instead of managing a separate Dispel password, your IdP handles authentication and tells Dispel who the user is.

    Dispel supports four identity providers. Active Directory connects over LDAP(S); Microsoft Entra ID, Okta, and Ping Identity each connect over either OAuth (OIDC) or SAML:

    • Active Directory — Microsoft's on-premises directory service.

    • Microsoft Entra ID — Microsoft's cloud identity platform (formerly Azure AD).

    • — Okta's enterprise identity platform.

    • — Ping's federated identity platform.

    The protocol you'll use is determined by the provider you're connecting:

    • Active Directory connects over LDAP(S) only.

    • Microsoft Entra ID, Okta, and Ping Identity each support both OAuth (OIDC) and SAML. When you configure one of these, you'll be able to select between these two protocols. Only one can be active per provider at a time.

    For those three cloud providers, choose between OIDC and SAML based on how your IdP application is set up:

    Protocol
    What it is
    Choose it when

    Active Directory uses LDAP(S) — a protocol for querying and authenticating against a directory server, secured with TLS. Because AD supports only LDAP(S), there's no protocol selection step for it.

    Setting up SSO is a two-way exchange. You give Dispel details about your IdP, and — for SAML — you paste Dispel's service-provider details back into your IdP.

    You enter the following in Dispel:

    Field
    What to enter

    On the IdP side, register Dispel as an application and set its redirect URI to your Dispel address followed by /oauth/login-callback (for example, https://app.dispel.com/oauth/login-callback). If you're unsure of the exact address for your environment, confirm it with your Dispel representative.

    Dispel shows two read-only values at the top of the SAML form — paste these into your IdP's SAML application:

    Dispel provides
    Paste into your IdP as

    Use the Copy ID and Copy URL buttons next to each. Then enter the following in Dispel:

    Field
    What to enter

    Unlike the SSO flows, LDAP isn't a redirect-based handshake — Dispel connects directly to your directory and authenticates users against it. There's nothing to paste back into another system; all configuration lives in Dispel. The values below come from your Active Directory administrator.

    You enter the following in Dispel:

    Field
    What to enter

    The exact IdP-side steps differ by provider — see each provider's page for specifics. The overall flow is the same:

    1. Go to Settings → Integrations and click Connect on the provider's card.

    2. Select Authentication Protocol — OAuth or SAML.

    3. (SAML only) Copy Dispel's SP Entity ID and ACS URL into your IdP's SAML app.

    4. Fill in the connection fields with the values from your IdP, and choose an Organization Identifier.

    Connecting Active Directory? AD uses LDAP(S) and follows a different flow — Dispel connects directly to your directory rather than redirecting through an SSO handshake, and there's no protocol to choose. See the for the full walk-through.

    Once SSO is configured, users sign in with your IdP instead of a Dispel password:

    1. On the Dispel sign-in screen, the user enters your Organization Identifier.

    2. Dispel redirects them to your IdP to authenticate.

    3. On success, they're returned to Dispel and signed in.

    Dispel reads the user's email, first name, and last name from the IdP response.

    You can automatically place SSO users into Dispel groups based on their groups in your IdP. Dispel syncs group membership on a schedule, so access stays in step with your IdP. See .

    When SSO is in use, your IdP is responsible for authentication — including any MFA you enforce there. As a result, Dispel's email one-time codes are not applied to users who sign in via SSO. Keep this in mind when designing MFA requirements in the .

    To change providers, or to switch a provider between OAuth and SAML, Disconnect the current integration first, then connect the new one.

    Data Exports

    This page requires authentication

    This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

    Sign in to continue →

    Click Save settings.

  • (SAML only) Click Test connection. Dispel redirects you to your IdP to sign in, then shows the user attributes it received (email, first name, last name). If the test fails, check that the details match your IdP's SAML app and that the test user exists in your IdP and is invited to this organization.

  • OAuth (OIDC)

    An open standard for access delegation, commonly used for token-based authentication.

    Your IdP app is set up as an OIDC / OAuth application.

    SAML

    An XML-based framework for exchanging authentication and authorization data between parties.

    Your IdP app is set up as a SAML application, or your organization standardizes on SAML.

    Client URL

    The URL where OAuth tokens are sent — found in your IdP settings.

    Client ID

    Your IdP's unique identifier (often a URL or URN), from your IdP settings.

    Client Secret

    The client secret issued by your IdP.

    Organization Identifier

    A unique identifier you choose. Your users type this on the Dispel sign-in screen. Letters, numbers, dashes, and underscores only.

    Service Provider (SP) Entity ID

    The SP entity ID / audience.

    Assertion Consumer Service URL

    The ACS URL / reply URL / single sign-on URL.

    SSO URL

    The URL where the SAML assertion is sent — found in your IdP settings.

    Identity Provider Entity ID

    Your IdP's unique identifier (often a URL or URN).

    Base64 Signing Certificate

    The certificate your IdP uses to sign SAML assertions. Paste it, or use Upload Certificate (max 1 MB).

    Organization Identifier

    A unique identifier you choose. Your users type this on the Dispel sign-in screen.

    Sign-in identifier

    A unique identifier you choose. Your users type this on the Dispel sign-in screen.

    Active Directory domain

    Your AD DNS domain — e.g. corp.example.com.

    Domain controllers

    The hostname(s) of the domain controller(s) Dispel connects to over LDAPS (port 636) — e.g. dc01.corp.example.com.

    Certificate trust + CA certificate

    How Dispel validates the TLS connection, and (recommended) the CA certificate that issued your domain controllers' certificates. From your PKI or AD admin; PEM, CRT, or CER.

    Bind DN or UPN

    Where to find it. Sign in as an organization administrator and open Settings → Integrations (or the dedicated Settings → Authentication page). The providers appear in the Identity & Authentication (IdP / SSO) section. Click Connect on a provider to begin.

    One identity provider per organization. An organization can have a single active IdP at a time, using a single protocol. To switch providers — or switch an existing provider between OAuth and SAML — you must disconnect the current one first.

    Choosing a protocol

    What you provide, and what Dispel provides

    OAuth (OIDC)

    SAML

    LDAP(S)

    Setting up a provider

    Secrets are masked. After you save, secret fields (client secret, certificate) are masked. When editing later, leave a masked field unchanged to keep the stored value.

    How users sign in

    Users must be invited first. SSO authenticates a user, but it doesn't grant access on its own. A user must already be invited to your organization in Dispel before they can sign in via SSO. See .

    Group mapping

    SSO and multi-factor authentication

    Switching or disconnecting a provider

    Disconnecting forces a password reset. Removing an SSO integration means affected users can no longer sign in through the IdP — they'll need to reset their Dispel passwords to sign in again, and you'll need to re-enter all fields to reconnect.

    Frequently asked questions

    Can I use more than one identity provider at once?

    No. An organization has a single active IdP at a time. If you're already connected to one provider, the others are unavailable until you disconnect — you'll see a note that you're currently connected to another provider and must disconnect it first.

    Can I use both OAuth and SAML for the same provider?

    No. Only one authentication protocol is supported per identity provider at a time. To switch protocols, disconnect and reconnect with the other one.

    What is the Organization Identifier?

    It's a short, unique label you choose (letters, numbers, dashes, and underscores). Your users enter it on the Dispel sign-in screen so Dispel knows which IdP to send them to.

    Does a user automatically get an account on first SSO sign-in?

    Only if they've already been invited to your organization. SSO proves who a user is, but they must have an invitation in Dispel to gain access.

    Who can configure SSO?

    An organization administrator. Configuring or disconnecting an identity provider requires organization-edit permission.

    Okta
    PingIdentity
    Active Directory setup guide
    Group Mapping
    Policy Builder

    Security & Data Handling

    Where to find Dispel's security program, data-protection measures, data residency, sub-processors, and the shared-responsibility model for a security review.

    Facility Groups

    The read-only service account Dispel authenticates as — e.g. svc-dispel@corp.example.com.

    Bind password

    The service account's password.

    User search base

    The directory location (OU) to search for users — e.g. OU=Users,DC=corp,DC=example,DC=com.

    Group search base

    The directory location (OU) to search for groups.

    Login attribute

    The attribute users enter as their username — commonly sAMAccountName.

    Invite a User to Dispel

    This page requires authentication

    This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

    This page requires authentication

    This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

    Sign in to continue →
    Sign in to continue →

    Active Directory

    Use Active Directory as your identity provider so users sign in to Dispel with their Active Directory credentials over LDAPS.

    Configuring an Active Directory Integration

    Connect Dispel to your organization's Active Directory (AD) so your team can sign in with their existing corporate credentials, with access granted automatically based on the AD groups users already belong to.


    Before you begin

    These resources are necessary to enable users to sign in to Dispel via your Active Directory.

    • A read-only AD service account: Dispel uses this to look up users and groups. This should have least-privilege and does not need write access.

    • Your domain controller hostnames (for example dc01.corp.example.com), reachable from Dispel over LDAPS (port 636).

    • The CA certificate that issued your domain controllers' TLS certificates.

    • The organizational units (OUs) where your users and groups live.


    Navigate to Settings → Authentication → Active Directory in the Dispel dashboard.


    Fill in the Connection section.

    Field
    What it is
    Where to find it

    List the domain controllers Dispel should connect to. Add one per row; you can add several for redundancy.

    Field
    What it is
    Where to find it

    Tip: After you save and test, each controller shows a health status - Healthy, Unreachable, TLS failing, or Bind failing - so you can spot connection problems at a glance.


    Under Certificate trust, choose how Dispel validates your domain controllers' TLS certificate. Full validation is strongly recommended.

    Option
    What it means
    When to use it
    Field
    What it is
    Where to find it

    Under Service account, provide the read-only account Dispel uses to query your directory.

    Field
    What it is
    Where to find it

    Under Identity, tell Dispel where to find users and groups, and which attributes to read.

    Field
    What it is
    Where to find it

    Advanced (optional - expand to adjust):

    Field
    What it is
    Where to find it

    Click Test connection. Dispel binds with the service account and checks each domain controller.

    • A passing test unlocks group mapping and lets you enable the integration.

    • If a controller shows TLS failing, Bind failing, or Unreachable, see below.

    Note: If you change any connection settings later, the previous test result becomes Stale - re-test before enabling.


    Under Group access, map each Active Directory group to the Dispel group whose access it should grant. Users who don't fall into any mapped group can't sign in, so map at least one.

    Column
    What it is
    Where to find it

    Use Add mapping to add more rows. Members are kept in sync automatically: users added to a mapped AD group gain access, and users removed lose access.


    Before enabling, you can dry-run a real user's sign-in under Test user sign-in to confirm they'd be allowed to sign in and land in the right groups.

    Field
    What it is
    Where to find it

    Click Run test to see whether access would be granted or denied, and which groups resolve.


    When the connection test passes and at least one group is mapped, click Enable. Your users can now sign in with their Active Directory credentials using the sign-in identifier from Step 2.


    Once the integration is enabled, users sign in with their Active Directory credentials instead of a Dispel password:

    1. On the Dispel sign-in screen, the user enters your sign-in identifier, then their AD username and password.

    2. Dispel authenticates the credentials directly against your directory — there's no redirect to an external identity provider.

    3. On success, they're signed in.

    Dispel reads the user's email and display name from the directory, using the attributes you configured.


    Once the integration is enabled, Dispel automatically keeps Dispel group membership aligned with your mapped Active Directory groups on a recurring schedule - users added to a mapped group gain access, and users removed from a mapped group lose access with no manual steps.

    If you've just changed membership in Active Directory and want it reflected right away, use Sync now.

    • Sync now appears in the top-right of the Active Directory page header, and only after the integration is enabled.

    • Click it to run a sync immediately. While it's working, the button shows Syncing…, and the Last synced timestamp updates when it finishes.

    • You don't need to do this routinely - automatic syncs keep everything current on their own. Use it when you want a change applied without waiting for the next scheduled sync.


    • Apply Changes: save edits to an existing integration. Changing connection settings marks the test result stale; re-test before relying on it.

    • Disable: stop directory sign-in without deleting the configuration. Local and break-glass sign-in stay available; you can re-enable at any time.

    • Delete: remove the integration entirely, including domain controllers, certificate trust, and group mappings.


    Status / message
    What it usually means
    What to check

    Name

    A friendly label for this integration, shown only inside Dispel.

    Your choice - e.g. "Corporate AD" or "Plant Directory".

    Sign-in identifier

    The short, unique keyword your users enter when signing in with this directory. Use letters, numbers, and hyphens.

    Your choice - e.g. plant-directory. Must be unique across your integrations.

    Active Directory domain

    Your AD DNS domain name.

    Your AD/DNS domain, e.g. corp.example.com. Ask your AD administrator if unsure.

    Controller

    The hostname (or IP) of a domain controller, reached over LDAPS on port 636.

    e.g. dc01.corp.example.com. From your AD administrator or DNS. Make sure it's reachable from Dispel.

    Validate chain and hostname (recommended)

    Dispel verifies the certificate chain and that the hostname matches. Most secure.

    Almost always. Upload your CA certificate below.

    Skip hostname check

    The chain is still verified; only the hostname match is skipped.

    Only if your certificate's hostname doesn't match the address you connect to.

    Disable validation

    The connection is not authenticated and could be intercepted.

    Not recommended. Requires an explicit confirmation.

    CA certificate

    The public certificate of the authority that signed your domain controllers' certificates. Paste the PEM text or upload a file.

    From your PKI or AD administrator. Accepted formats: PEM, CRT, or CER.

    Bind DN or UPN

    The service account Dispel authenticates as.

    The account's UPN (e.g. svc-dispel@corp.example.com) or distinguished name (e.g. CN=svc-dispel,OU=Service Accounts,DC=corp,DC=example,DC=com). Use a read-only account.

    Bind password

    The service account's password.

    Set by whoever created the service account. (Once saved, it's hidden — enter a new value only to replace it.)

    User search base

    The OU (distinguished name) under which Dispel searches for users.

    e.g. OU=Users,DC=corp,DC=example,DC=com. From your AD structure (Active Directory Users and Computers).

    Group search base

    The OU under which Dispel searches for groups.

    e.g. OU=Groups,DC=corp,DC=example,DC=com. From your AD structure.

    Login attribute

    The AD attribute users type as their username when signing in.

    Choose from the discovered attributes - commonly sAMAccountName or userPrincipalName.

    Display name

    The attribute used for a user's display name.

    Usually displayName or cn.

    Email

    The attribute used for a user's email address.

    Usually mail or userPrincipalName.

    AD group

    The Active Directory group to read membership from.

    Start typing to search your directory's groups.

    Org group

    The Dispel group whose access those members receive.

    Pick from your existing Dispel groups.

    Username

    A real directory username to test with.

    Any AD user's login value (matching your chosen login attribute).

    Password

    That user's password.

    The user's own password. Used only for the test and never stored.

    Unreachable

    Dispel can't reach the domain controller.

    Hostname is correct and reachable from Dispel over port 636.

    TLS failing

    The certificate couldn't be validated.

    The correct CA certificate is uploaded (Step 4), and it matches your controllers' certificates.

    Bind failing

    The service account couldn't authenticate.

    The Bind DN/UPN and password are correct, the login/email attributes are correct, and the account is enabled.

    1. Open the Active Directory settings

    2. Name the integration and set the sign-in identifier

    3. Add your domain controllers

    4. Choose certificate trust

    5. Add the service account credentials

    6. Set the identity mapping

    7. Test the connection

    8. Map AD groups to Dispel groups

    9. (Optional) Test a user sign-in

    10. Enable the integration

    How users sign in

    Users must be invited first. Authenticating against AD confirms who a user is, but it doesn't grant access on its own. For Active Directory, invitations are created automatically when a user belongs to a mapped AD group — the group sync invites them (and revokes access when they're removed from the group). A user who isn't in any mapped group can't sign in.

    Keeping access in sync

    Managing the integration

    Troubleshooting

    Troubleshooting

    A user is denied

    The user isn't in any mapped group.

    Confirm they belong to a mapped AD group, and that the group mapping (Step 8) is correct.

    Okta

    Use Okta as your identity provider so users sign in to Dispel with their Okta credentials over OAuth (OIDC) or SAML.

    Overview

    Connect Okta — Okta's enterprise identity platform — as your organization's identity provider. Once connected, your users sign in to Dispel with their Okta credentials through single sign-on. You can connect Okta over OAuth (OIDC) or SAML.

    This page covers the Okta-specific setup. For the shared behavior that applies to every provider — how users sign in, group mapping, MFA, and disconnecting — see Identity Providers.

    Where to find it. Sign in as an organization administrator and open Settings → Integrations (or the dedicated Settings → Authentication page). Okta appears in the Identity & Authentication (IdP / SSO) section. Click Connect on its card to begin.

    Before you begin

    • You'll configure the IdP side in the Okta Admin Console, so you'll need administrative access there.

    • Decide on a protocol — OAuth (OIDC) or SAML. See Choosing a protocol.

    • Make sure the users who will sign in via Okta are already invited to your organization in Dispel. SSO authenticates users but doesn't create access on its own.

    1. In the Okta Admin Console, go to Applications → Create App Integration and choose OIDC — OpenID Connect.

    2. Set the sign-in redirect URI to your Dispel address followed by /oauth/login-callback — for example https://app.dispel.com/oauth/login-callback. Confirm the exact address for your environment with your Dispel representative if you're unsure.

    3. Assign the app to the users or groups who should have access.

    1. Click Connect on the Okta card and Select Authentication Protocol → OAuth.

    2. Fill in the fields:

    Field
    Value from Okta
    1. Click Save settings.

    1. In the Okta Admin Console, go to Applications → Create App Integration and choose SAML 2.0.

    2. In the SAML settings, paste the values Dispel shows at the top of its SAML form:

      • Single sign-on URL / Recipient / Destination ← Dispel's Assertion Consumer Service URL.

      • Audience URI (SP Entity ID) ← Dispel's Service Provider (SP) Entity ID

    1. Click Connect on the Okta card and Select Authentication Protocol → SAML.

    2. Copy the Service Provider (SP) Entity ID and Assertion Consumer Service URL shown at the top of the form (use Copy ID / Copy URL) into Okta, as above.

    3. Fill in the fields:

    Field
    Value from Okta
    1. Click Save settings.

    2. Click Test connection. Dispel redirects you to Okta to sign in, then shows the email and name it received. If the test fails, confirm the values match your Okta app and that the test user is invited to your organization.

    • Users sign in by entering your Organization Identifier on the Dispel sign-in screen and authenticating with Okta. See .

    • Map Okta groups to Dispel groups so membership stays in sync — see .

    • MFA enforced in Okta applies during sign-in; Dispel's email one-time codes don't apply to SSO users. See .

    • To switch protocols or providers, disconnect first. See .

    From the app's General tab, copy the Client ID and Client secret, and note your Okta domain / issuer.

    .
  • Finish creating the app, then open its Sign On tab and collect:

    • Identity Provider Single Sign-On URL → Dispel's SSO URL.

    • Identity Provider Issuer → Dispel's Identity Provider Entity ID.

    • The X.509 / signing certificate → Dispel's Base64 Signing Certificate.

  • Assign the app to the users or groups who should have access.

  • Client URL

    Your Okta OAuth/OIDC endpoint (issuer), e.g. https://your-org.okta.com.

    Client ID

    The application's Client ID.

    Client Secret

    The application's Client secret.

    Organization Identifier

    A unique identifier you choose; users type it on the sign-in screen.

    SSO URL

    The Identity Provider Single Sign-On URL.

    Identity Provider Entity ID

    The Identity Provider Issuer.

    Base64 Signing Certificate

    The Okta signing certificate. Paste it or use Upload Certificate.

    Organization Identifier

    A unique identifier you choose; users type it on the sign-in screen.

    One provider at a time. If your organization is already connected to another identity provider, disconnect it before connecting Okta.

    Connect with OAuth (OIDC)

    In Okta

    In Dispel

    Connect with SAML

    In Okta

    In Dispel

    After connecting

    Frequently asked questions

    Which protocol should I use with Okta?

    Either works. Use whichever matches the app you create in Okta — an OIDC app integration for OAuth, or a SAML 2.0 app integration for SAML.

    Do I need to assign users to the Okta app?

    Yes. Only users (or groups) assigned to the Okta app can authenticate through it. They must also be invited to your Dispel organization.

    My SAML test connection failed. What should I check?

    Confirm the SSO URL, Issuer, and certificate match your Okta app's Sign On settings, that you pasted Dispel's SP Entity ID and ACS URL into Okta's SAML settings, and that the test user is assigned to the Okta app and invited to your Dispel organization.

    How users sign in
    Group Mapping
    SSO and multi-factor authentication
    Switching or disconnecting a provider

    Shared Accounts

    Allow multiple individuals to securely access a single account while maintaining full attribution and audit trails

    This page requires authentication

    This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

    Sign in to continue →

    User & Entity Behavior Analytics

    A technical review of Dispel UEBA for risk factor analysis

    This page requires authentication

    This documentation is available to signed-in Dispel customers. Sign in with your Dispel account to view it.

    Sign in to continue →