NIS2 Directive
How Dispel maps to NIS2 Article 21(2), and what remains the customer’s responsibility.
Overview
NIS2 (Directive (EU) 2022/2555) requires essential and important entities to manage cybersecurity risk. Article 21(2) lists ten minimum measures, (a) to (j).
Dispel secures remote access to operational technology and IT systems. The table below shows, for each measure, what Dispel provides, what you configure in Dispel, and what remains your responsibility.
For more detail on your responsibilities, see Complementary User Entity Controls. Responsibilities also differ by deployment model; see Shared Responsibilities.
Dispel’s Universal Controls are mapped to NIS2. To see which ones pass for your organization, select NIS2 under Security → Compliance in the Dispel app.
Article 21(2) Mapping
(a) Risk analysis and information system security policies
Dispel maintains information security policies and runs periodic risk assessments, audited under SOC 2 Type II and ISO 27001.
Select the compliance frameworks that apply to you.
Include Dispel in your risk assessment, and decide which assets and zones it can reach.
(b) Incident handling
Dispel runs a formal incident response process, logs security events centrally, and notifies you of data breaches as set out in the Data Protection Addendum.
Allow Regions to record Browser Connect sessions. Add Session Forensics for audit record review.
Run your incident response plan, tell Dispel about suspected compromises, and meet your Article 23 reporting obligations.
(c) Business continuity, backup management, disaster recovery, and crisis management
For SaaS, Dispel keeps backups across availability zones and regularly tests its disaster recovery procedures.
—
Plan how you will operate if remote access is unavailable. For on-premises and customer-cloud deployments, back up and restore the Dispel platform yourself.
(d) Supply chain security
Dispel holds its own high- and critical-risk suppliers to equivalent security requirements, publishes its sub-processors, and provides SOC 2 Type II and ISO 27001 reports in the Trust Portal.
Require access windows for third-party roles.
Assess Dispel as a supplier. Sponsor, approve, and offboard contractor and vendor users.
(e) Security in acquisition, development, and maintenance, including vulnerability handling and disclosure
Dispel develops to IEC 62443-4-1, runs a Vulnerability Disclosure Program, and provides security updates for the support period in the Product Lifecycle Policy.
—
Apply Wicket ESI updates, plus platform updates for on-premises and customer-cloud deployments. Keep the systems that host Dispel components patched.
(f) Assessing the effectiveness of cybersecurity risk-management measures
Dispel Compliance shows which controls pass for your organization, with evidence for each. Dispel’s own security testing is described in the Technical and Organizational Measures.
Rerun assessments after changing settings.
Periodically review Dispel roles, settings, audit logs, and session recordings, and test the controls you run around Dispel.
(g) Basic cyber hygiene and cybersecurity training
Dispel is built on zero trust principles: deny-by-default access, micro-segmentation, and least privilege. SaaS deployments receive security updates automatically during scheduled maintenance windows. Dispel staff complete security awareness training at onboarding and periodically after that, and the Dispel Enterprise Academy trains your users and administrators.
—
Train your users and administrators, and keep endpoints that access Dispel hardened and patched.
(h) Cryptography and encryption
All remote access runs through encrypted tunnels. Data is encrypted in transit and at rest as described in the Technical and Organizational Measures.
—
Set your cryptography policy. For on-premises and customer-cloud deployments, store, rotate, and protect platform encryption keys.
(i) Human resources security, access control, and asset management
Dispel enforces role-based, deny-by-default access, and supports account disabling and identity-provider deprovisioning.
Limit the Organization Admin role, set Region ACL rules, register devices, and deactivate members who leave.
Run joiner, mover, and leaver processes in your identity provider, review access on a schedule, and keep an inventory of assets behind Dispel.
(j) Multi-factor or continuous authentication, secured communications, and emergency communication systems
Dispel supports two-factor authentication, SSO (SAML, OAuth, OIDC, or Microsoft), and re-authentication, and encrypts every remote session.
Require two-factor authentication or SSO for the whole organization.
Enforce MFA in your identity provider, and keep emergency communication channels that do not depend on Dispel.

