Implementing information security pragmatically according to ISO 27001 and BSI
The ISMS model that the DORA extension builds on.
View datesThe requirements are known. In an audit, what counts is whether you can prove that you have implemented them. CRISAM® brings ICT risks, control objectives, incidents and service provider contracts together in one shared model, from assessment through evidence and reporting to export.
As of 22 September 2026
| Deviation | Reference | Rating | Status |
|---|---|---|---|
| Register of information incomplete | Art. 28 | open | |
| Exit strategy per critical service | Art. 28 | in progress | |
| Test plan for critical systems | Art. 24 | in progress | |
| Incident classification criteria | Art. 18 | done |
DORA is Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. It requires financial entities and their ICT third-party service providers to manage ICT risks, report major incidents, test resilience regularly and maintain all contractual arrangements on the use of ICT services in a register of information. The regulation applies directly in all EU member states and has applied since 17 January 2025.
It is specified in more detail by regulatory technical standards and implementing technical standards, RTS and ITS for short. These govern classification, reporting formats and the register of information in detail.
DORA is not a one-time project. The effort is ongoing, quarter after quarter.
KAIT, VAIT and ZAIT cease to apply.
DORA applies directly, without national transposition.
Major incidents must be reported. In hours, not weeks.
The register of information goes to the competent authority.
BAIT is repealed in full.
ICT risk management under Article 16 applies to additional supervised entities.
The scope does not end at your company boundary. It extends to ICT third-party service providers and their subcontractors.
Your contracts belong in your customers' register of information, and for critical or important functions this includes the subcontractors that deliver the service. Any provider the European Supervisory Authorities designate as a critical ICT third-party service provider is additionally subject to a dedicated Oversight Framework.
Instead of the full Articles 5 to 15, Article 16 provides for a simplified ICT risk management framework: for small and non-interconnected investment firms, payment institutions exempted pursuant to Directive (EU) 2015/2366, institutions exempted pursuant to Directive 2013/36/EU, electronic money institutions exempted pursuant to Directive 2009/110/EC and small institutions for occupational retirement provision.
Four of them require ongoing evidence, not one-time documents.
| Requirement area | Articles | Required evidence | How to map it in CRISAM® |
|---|---|---|---|
| ICT risk management | Art. 5 to 16 | ICT risk management framework, responsibility of the management body, digital operational resilience strategy, inventory of ICT assets, classification of critical or important functions | The DORA Knowledge Pack comes with over 55 building blocks and more than 700 control objectives, structured by company size and for ICT third-party service providers. Critical or important functions are classified, and the ICT services derived from them are documented. |
| ICT-related incident management, classification and reporting | Art. 17 to 23 | Incident management process, classification according to the criteria of Delegated Regulation (EU) 2024/1772, initial notification, intermediate report and final report to the competent authority | Incidents are recorded in an audit-proof manner and can be exported directly for regulatory reporting obligations. The history stays documented directly on the incident. |
| Digital operational resilience testing | Art. 24 to 27 | Testing program, tests at least yearly of all ICT systems and applications supporting critical or important functions, threat-led penetration testing every three years for significant financial entities | Findings and deviations are managed and tracked as measures, in the same model as the control objectives. The DORA extension is connected to the Audit module. |
| Managing of ICT third-party risk | Art. 28 to 44 | Register of information on all contractual arrangements on the use of ICT services, for critical or important functions including the subcontractors, yearly submission to the supervisory authority, minimum contractual content, exit strategies | The register of information can be built, maintained and exported based on the existing ISMS model and with content from the BCMS module. Reports for audits and evidence obligations are available in addition. |
| Information-sharing arrangements | Art. 45 | Voluntary: arrangements for exchanging cyber threat information and intelligence within trusted communities of financial entities | If you participate, you store the arrangement as evidence with the associated control objective. |
From classification to the register of information for the supervisory authority.
The wizard guides you through the classification and documents the reasoning. It stays stored in the system and is available in the audit.
Article 16 applies, among others, to small and non-interconnected investment firms, exempted payment institutions and electronic money institutions, and small institutions for occupational retirement provision.
Critical or important functionA function whose disruption would materially impair financial performance, soundness or continued compliance with the conditions of authorization.
EvidenceThe reasoning stays with the object and can be retrieved at any time in the audit.
The requirements catalog breaks the articles down into building blocks and calculates the compliance level. This shows you where the gaps are: for which control objective, in which article and how severe.
| Control objective | Reference | Actual | Target | Severity |
|---|---|---|---|---|
| Exit strategy per critical ICT service | Art. 28 | 1 | 4 | |
| Test plan for critical systems | Art. 24 | 2 | 4 | |
| Subcontractors in the register | Art. 28 | 2 | 4 | |
| Incident classification criteria | Art. 18 | 3 | 4 | |
| Inventory of ICT assets | Art. 8 | 3 | 4 |
Information can be collected in a targeted, decentralized way from the responsible subject matter owners. This significantly reduces the effort for baseline audits, reviews and supplier surveys.
Incidents are recorded in an audit-proof manner and exported for reporting. The deadlines are built in: four hours from classification, no later than 24 hours from detection, then 72 hours and one month.
| Report | Deadline | Status |
|---|---|---|
| Initial notification | 4 hours from classification, no later than 24 hours from becoming aware | |
| Intermediate report | 72 hours after the initial notification | |
| Final report | no later than one month after the latest intermediate report |
Findings become measures with an owner and a due date, managed in the same model as the control objectives. The report shows what is planned, what has been performed and what is still open.
| System or application | Test type | Performed | Findings | Status |
|---|---|---|---|---|
| Core banking system | Scenario-based | 12.03.2026 | 3 | |
| Payment platform | Penetration test | 28.04.2026 | 5 | |
| Online banking | Vulnerability scan | 02.07.2026 | 2 | |
| Card authorization | Recovery | 19.08.2026 | 1 | |
| Customer portal | Vulnerability scan | 05.09.2026 | 4 | |
| Regulatory reporting | Scenario-based | planned 11/2026 | 0 |
You build the register of information from the existing ISMS model and the content of the BCMS module, maintain it there and export it. Reports for audits and evidence obligations are available in addition.
| ICT third-party service provider | Service | Function | Subcontractors | Country | Status |
|---|---|---|---|---|---|
| Nord IT Services | Data center operations | critical | 2 | DE | |
| Pay Core | Card authorization | critical | 3 | AT | |
| Cloud Alpine | Cloud infrastructure | important | 4 | IE | |
| Secure Mail Group | Email security | important | 1 | DE | |
| Core Banking Solutions | Core banking system | critical | 2 | DE | |
| Identity Hub | Authentication | important | 0 | AT | |
| Data Vault | Archiving | not critical | 0 | DE | |
| Analytics Partner | Reporting | not critical | 1 | PL |
| Output | Purpose | Status |
|---|---|---|
| Register of information, structured file | Submission to the supervisory authority | ready |
| Register of information report | Internal audit and audits | ready |
| ICT incident report, export file | Report to the supervisory authority | ready |
ICT risk management framework, detection and recovery.
Positioning alongside NIS-2 and ISO/IEC 27001, report to the management body.
Review of evidence down to the individual case.
Register, contract content, subcontractors.
If you operate an information security management system in line with ISO/IEC 27001, you have already provided part of the DORA evidence. CRISAM® handles overlapping requirements by mapping the control objective questions to the individual standards.
One answered control objective question counts for DORA, ISO/IEC 27001 and NIS-2 at the same time.
Overlapping requirements can be managed together, especially in supply chains with many ICT third-party service providers.
CRISAM® complements your existing systems and connects them through interfaces.
The DORA extension is fully integrated into ISMS, Business Continuity Management, risk management and audit.
Under Article 1(2), DORA is a sector-specific legal act with regard to financial entities. The DORA provisions therefore take precedence over the NIS-2 provisions on cybersecurity risk management and reporting, and displace them to that extent. For financial entities, the DORA requirements therefore apply in these areas.
| Criterion | DORA | NIS-2 | ISO/IEC 27001 |
|---|---|---|---|
| Legal nature | EU regulation, directly applicable, no national transposition required | EU directive, national transposition required | International standard, voluntary and certifiable |
| Who is affected | The financial entities listed in Article 2 and their ICT third-party service providers | Essential and important entities in the sectors named in the directive | Any organization that wants to operate a management system or have it certified |
| Relationship to each other | Sector-specific legal act that takes precedence for financial entities | Displaced for financial entities in risk management and reporting | No conflict, provides the structure for both evidence paths |
| Reporting obligation | Initial notification within 4 hours of classification and no later than 24 hours from detection, intermediate report after 72 hours, final report within one month | Early warning within 24 hours, notification within 72 hours, final report within one month | No reporting obligation to authorities |
| Testing | At least yearly for ICT systems supporting critical or important functions, threat-led penetration testing every three years for significant financial entities | No comparable testing requirement, the effectiveness of the measures must be assessed | Internal audits and management review |
| Third parties | Register of information, minimum contractual content, exit strategies, Oversight Framework for critical ICT third-party service providers | Supply chain security as a risk management measure | Supplier relationships as controls in Annex A |
| Evidence | Evidence to the supervisory authority, certification is not provided for | Evidence to the competent national authority | Certificate from an accredited certification body |
| Supervision | BaFin and FMA, plus the European Supervisory Authorities for critical ICT third-party service providers | Competent national authorities | Accredited certification bodies |
KAIT, VAIT and ZAIT ceased to apply at the end of 16 January 2025. BAIT continues to apply on a transitional basis to supervised entities that have applied BAIT so far and are not yet required to operate ICT risk management under DORA. At the end of 31 December 2026, BAIT will be repealed in full. From 1 January 2027, Article 16 DORA applies to the supervised entities concerned. You can find an overview of all frameworks covered by CRISAM® under Standards and frameworks.
In the webinars you see live the models that the DORA extension is also built on.
The ISMS model that the DORA extension builds on.
View datesIn one version each for Germany and for Austria.
View datesWebinars and training sessions at a glance, plus the self-paced courses of the CRISAM® Academy and the product materials in the download center.
AcademyDownload centerThe first step depends on where you stand today.
Then you build on what you already have. The DORA extension builds on the existing ISMS model, and the register of information can be built specifically from it and from the BCMS module. Control objective questions you have already answered remain valid.
You are not starting from scratch. The DORA Knowledge Pack comes with over 55 building blocks and more than 700 control objectives, structured by company size. You work through an existing catalog instead of creating it yourself.
You deliver the evidence your customers need for their register of information. For this, the Knowledge Pack includes dedicated content for ICT third-party service providers.
For this you need the CRISAM® GRC Platform, the CRISAM® ISMS Module and the DORA Knowledge Pack. In the demo we discuss your starting point and show which of these you already have in place.
DORA is Regulation (EU) 2022/2554 on digital operational resilience for the financial sector. It requires financial entities and their ICT third-party service providers to manage ICT risks, report major incidents, test resilience regularly and maintain all contractual arrangements on the use of ICT services in a register of information. The regulation applies directly in all EU member states and has applied since 17 January 2025.
DORA applies to the financial entities listed in Article 2, including credit institutions, payment institutions and electronic money institutions, investment firms, insurance and reinsurance undertakings, institutions for occupational retirement provision and crypto-asset service providers. It also applies to ICT third-party service providers that provide services to these entities.
Article 16 provides for a simplified ICT risk management framework for certain smaller entities in place of Articles 5 to 15. It names small and non-interconnected investment firms, exempted payment institutions, institutions exempted pursuant to Directive 2013/36/EU, exempted electronic money institutions and small institutions for occupational retirement provision.
Under Delegated Regulation (EU) 2025/301, the initial notification is submitted within four hours from classification of the incident as major and no later than 24 hours from detection. The intermediate report follows 72 hours after the initial notification, even if the status has not changed. The final report must be submitted no later than one month after the latest intermediate report.
Under Article 28, the register of information covers all contractual arrangements on the use of ICT services provided by third-party service providers. For contracts that support critical or important functions, it also includes the subcontractors that ensure the delivery of the ICT service. The register must be submitted to the supervisory authority every year.
All ICT systems and applications supporting critical or important functions must be tested appropriately at least once a year. Significant financial entities additionally carry out threat-led penetration testing every three years. The criteria for this are set out in Article 26(8) and in Delegated Regulation (EU) 2025/1190.
Under Article 1(2), DORA is a sector-specific legal act with regard to financial entities. The DORA provisions therefore take precedence over the NIS-2 provisions on cybersecurity risk management and reporting, and displace them to that extent. For financial entities, the DORA requirements therefore apply in these areas.
KAIT, VAIT and ZAIT ceased to apply at the end of 16 January 2025. BAIT continues to apply on a transitional basis to supervised entities that have applied BAIT so far and are not yet required to operate ICT risk management under DORA. At the end of 31 December 2026, BAIT will be repealed in full, and from 1 January 2027, Article 16 DORA applies to the supervised entities concerned.
The regulatory information on this page comes from the following sources.
Status of this page: 22 September 2026. The information reflects the status of the sources named as of that date.
In the demo we walk through your case: applicability, gap analysis, incident reporting and register of information.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Embedded Content. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information