Lab · SIEM validation layer · DORA

Licence or service: how DORA classifies software.

A datasheet for financial entities: what the Digital Operational Resilience Act requires, whom it affects and where BaFin draws the line between a software licence and an ICT service.

General information, not legal advice. Applicability and classification must be assessed case by case. As of August 2026.

Legal act

DORA at a glance

Legal actRegulation (EU) 2022/2554 — Digital Operational Resilience Act (DORA)
Applicable since17 January 2025
Whom it affectsFinancial entities (banks, insurers, investment firms and others) and their ICT third-party service providers
Five pillarsICT risk management · ICT incident reporting · digital operational resilience testing · ICT third-party risk management · information sharing
Supervisor (DE)BaFin

DORA incident reporting is staged much like NIS2 reporting; for financial entities DORA takes precedence as the sector-specific rule: NIS2 incident reporting in practice →

Distinction

The form of procurement decides

Art. 3 No. 21 DORA defines ICT services deliberately broadly, and classifying a specific procurement remains the financial entity’s task. For the distinction between licence and Software-as-a-Service, BaFin’s DORA FAQ contains two statements:

“Pure software licences are typically usage rights that do not constitute an ICT service within the meaning of Art. 3 No. 21 DORA.”
BaFin, DORA FAQ on ICT third-party risk management, on isolated software procurement (German original, our translation), retrieved 10 October 2026
“Software-as-a-Service applications are an ICT service that falls under Art. 3 No. 21 DORA when procured on an ongoing basis.”
BaFin, DORA FAQ, on pure Software-as-a-Service (German original, our translation), retrieved 10 October 2026
Licence, operated in your own networkHosted service (SaaS)
Where the software runsinside the financial entity’s networkat the provider
Classification per BaFin FAQtypically a usage right, not an ICT service (Art. 3 No. 21)an ICT service when procured on an ongoing basis (Art. 3 No. 21)
Vendordoes not, to that extent, become an ICT third-party service providerfalls within the ICT third-party framework
Resulting dutiesas a rule no minimum contract contents under Art. 30, no register entry, no exit strategy (Art. 28)minimum contract contents (Art. 30), register entry (Art. 28(3)), exit strategy for critical or important functions (Art. 28(8))
BaFin also notes that maintenance and support contracts accompanying a licence can themselves be ICT services. Our reading of this: What counts is the actual form of procurement, not the label.
Classification

What this means for the Sentinel validation layer

The validation layer runs entirely inside the operator’s network. The deterministic check opens no outbound connection, and rule generation and the advisory second opinion can run on a locally operated model. In this mode a financial entity obtains software for its own use and no ongoing service, which corresponds to the case BaFin describes in the first quote.

Two things change this classification. If generation runs through a cloud service, that service has to be assessed separately. And an accompanying maintenance contract can itself be an ICT service. Both belong in the assessment of the individual case.

For evidence, the validation layer produces a report per rule: what was checked against Microsoft’s parser and the workspace schema, what could not be checked, and with what result. The report is created and stays inside your own network. How the check works →

Not legal advice. This datasheet is general information and does not replace legal counsel. Whether DORA applies to your organisation, and how a specific procurement is to be classified, is for your legal advisors and, where relevant, BaFin. The quoted statements come from the BaFin FAQ and Regulation (EU) 2022/2554. As of August 2026.