The NIS2 directive is transforming cybersecurity from formal compliance into an architectural standard. For technical leaders, this means that process resilience depends on data sovereignty and built-in security at the platform level. The architectural strategy today involves moving from "security as an add-on" to security as the foundation of the system.
Why NIS2 makes on-premises a strategic choice for BPM
According to Gartner, by 2030, more than 75% of European enterprises will move workloads to sovereign clouds or private data centers (Gartner: Top Strategic Technology Trends for 2026). This is driven by the need for physical and logical control over data. For BPM systems, on-premises deployment is becoming a strategic tool that minimizes third-party reliance and data leak risks.
Architectural isolation: separating logic from execution
A key conflict in modern IT architecture is the need for centralized process orchestration alongside strict data isolation. Attempts to implement security via custom code in every process create vulnerabilities. An effective solution is to separate business logic from the execution flow. This minimizes the attack surface because access rules are defined at the platform level rather than hardcoded into BPMN diagrams (in accordance with the ISO/IEC 19510:2013 standard).
Metadata as a foundation: RBAC and RLS
Resilience is achieved when security policies, such as RLS (Row-Level Security) and RBAC, are part of the platform's metadata. Using a metamodel allows for data isolation at the core level rather than in application code. For example, solutions built on the UnityBase platform use metadata mechanisms to manage access rights, which aligns with NIS2 requirements for logical data isolation.
Integration security and visibility
Detecting shadow routes that bypass corporate controls is a critical audit task. Process mining technologies allow for the reconstruction of real flows from event logs, identifying bottlenecks (Celonis: What is Process Mining). Integrating such tools with an immutable audit trail at the platform level ensures transparency without compromising data integrity.
Designing for resilience: practical criteria
The architect's goal is to build a system that is secure without hindering operational activities. The UnityBase platform provides tools for building such solutions, allowing for the orchestration of processes via Camunda BPM with strict adherence to security policies at the platform level.
Criteria for BPM system architectural resilience under NIS2
- Data localization: capability for deployment in an on-premises environment.
- Layer isolation: separation of business logic, data, and the orchestration layer.
- Auditability: maintenance of immutable event logs at the platform level.
- Access control: implementation of RLS via metadata rather than custom scripts.
- Visibility: monitoring of real flows (process mining) to detect deviations.
FAQ
How can NIS2 compliance be ensured when using legacy BPM systems?
It is advisable to move security policies to an external integration layer or an intermediary platform that controls access and performs auditing without modifying the core of the legacy system.
What are the architectural advantages of on-premises for BPM in the context of NIS2?
On-premises deployment provides full physical and logical control over data, which is key to meeting requirements for data sovereignty and isolation.
How can access control be implemented in BPM without excessive coding?
Using domain metadata allows for the centralized definition of RLS and RBAC policies, automating security checks without the need to code them into business processes.