The IT circulars of the Federal Financial Supervisory Authority (BaFin) are being phased out and replaced by the European regulation DORA. Risk management under MaRisk remains in place and has become leaner with the amendment. For institutions that implement both frameworks, what matters is whether the requirements are linked in one shared model or sit in two separate repositories.
As of: 23 September 2026
| Risk | Category | Gross | Net |
|---|---|---|---|
| Failure of an ICT third-party service provider | Operational | ||
| Interest rate change in the banking book | Market price | ||
| Concentration in the loan portfolio | Counterparty default | ||
| Cyber incident involving customer data | Operational |
According to BaFin, the supervisory requirements for IT are essentially covered by the EU regulation DORA. To avoid double regulation, BaFin repealed its circulars KAIT, VAIT and ZAIT as of 17 January 2025, Chapter 11 of BAIT no longer applies, and BAIT will expire completely on 31 December 2026. What remains is risk management under the Minimum Requirements for Risk Management, MaRisk for short.
MaRisk applies in the version of Circular 06/2026 (BA) dated 30 Jun 2026. The amendment is more principles-based, and according to BaFin its complexity has been reduced significantly, with the length cut from 122 to around 80 pages.
Two developments are running in parallel: the IT circulars are being repealed, and risk management is being revised.
DORA applies. BaFin repeals the three circulars to avoid double regulation.
Institutions that apply Articles 5 to 15 or Article 16 of DORA are exempt from BAIT. Chapter 11 no longer applies.
Circular 06/2026 (BA). The amendment is more principles-based and has been shortened from 122 to around 80 pages.
BaFin publishes a separate circular for small and medium-sized investment firms.
After that, BaFin will no longer have a dedicated IT circular for banks.
From this date, additional institutions must meet the requirements of the regulation.
The information on the IT circulars comes from BaFin's announcement on the start of application of DORA; the information on the MaRisk amendment comes from the circular and the accompanying expert article.
Banks, insurers, asset management companies and payment institutions are affected, each in a different way. Since the amendment, the size of the institution also plays a role for MaRisk.
According to BaFin, the amendment introduces three size classes, essentially based on total assets: very small institutions with up to one billion euros, small institutions, and the remaining less significant institutions. The smaller the institution, the more leeway it has in applying the requirements.
BaFin cites stress tests as an example: very small institutions could now end up with five stress tests, some of them only annually instead of quarterly. For internal reporting, management decides on its own responsibility which partial reports have to be updated.
BaFin has published a separate circular for small and medium-sized investment firms. For these firms, the requirements are set out there, not in the version for banks.
Eight points that play a role in every audit, regardless of whether they concern risk management or IT.
| Requirement | Area | What matters | How you map it in CRISAM® |
|---|---|---|---|
| Maintain a risk inventory | Risk | A complete picture of the material risks, across categories and not only where something happened most recently | Risks can be identified and assessed in a structured way using wizards. Organizational structures are modeled flexibly from a risk perspective. |
| Assess appropriately | Risk | The assessment method has to match the significance of the risk. Where amounts matter, simply assigning classes is not enough | Depending on maturity level, qualitative and quantitative assessment methods are available, including across multiple periods. Monte Carlo simulations are available for the overall view. |
| Anchor controls | ICS | Controls have to be assigned to a risk, otherwise their effect cannot be assessed | Risks, controls, compliance requirements and audits are considered together. Controls are performed and tracked regularly, either once or on a recurring basis. |
| Connect ICT risks | IT | Since DORA, the IT requirements have been set out in the regulation. If ICT risks are managed separately, they are missing from the institution's overall view | The DORA extension is integrated into ISMS, business continuity management, risk management and audit. The mapping and assessment of the DORA requirements includes the associated RTS and ITS documents. |
| Keep an eye on service providers | IT | Even with outsourcing, the risk remains with the institution. It has to be clear which function is performed by which service provider | Critical or important functions are classified in a structured way, and the ICT services derived from them are documented traceably. The register of information can be built, maintained and exported. |
| Manage measures | Risk | Every measure needs an owner, a deadline and an effectiveness check | Risk mitigation measures are planned, implemented and monitored with workflow support. The gross and net view shows their effectiveness. |
| Report to management | Report | Management has to be informed in good time and in a form that supports decisions. Since the amendment, it decides for itself which partial reports are updated | Interactive dashboards show risks, workflows, measures and status. Management reports and individually configurable reports are aimed at decision-makers. |
| Stand up to audits | Evidence | Internal audit, auditors and supervisors ask not only about the result but also about how it was reached | All controls, measures, changes and results are documented centrally, versioned and kept in an auditable history. Audit and examination reports support internal and external audits. |
From the risk inventory to the documents that internal audit and auditors receive.
The wizard guides you through the capture. Whether the assessment is qualitative or quantitative depends on how the risk takes effect, not on the category it is assigned to.
The same risk appears in the risk inventory and in the ICT view. It is captured once and evaluated in both views.
Controls belong with the riskOnly the assignment shows how much of the gross assessment remains after the controls.
Responsibility and dateEvery risk has an owner and a review date. Both are part of the evidence.
Controls without a link to a risk create effort without telling you anything. Only the assignment shows which control reduces which risk and where no control applies.
| Control | Risk | Frequency | Last test | Effectiveness |
|---|---|---|---|---|
| Dual control for payment runs | Operational | monthly | 4 Sep 2026 | |
| Limit monitoring, banking book | Market price | daily | 4 Sep 2026 | |
| Review borrower units | Counterparty default | quarterly | 21 Aug 2026 | |
| Test fallback procedure | Operational | annually | 18 Feb 2026 | |
| Review access rights | Operational | semiannually | overdue | |
| Evaluate service provider reports | Operational | quarterly | overdue |
Since DORA, the IT requirements have been set out in the regulation. They are not managed separately but linked to the same objects as the other risks.
| Function | Service provider | Classification | Contract | Register |
|---|---|---|---|---|
| Payments | Service provider A | reviewed | complete | |
| Core banking system | Service provider B | reviewed | complete | |
| Customer portal | Service provider C | under review | partial | |
| Archiving | Service provider D | open | partial | |
| Reporting | internal | not required | complete |
| Item | Impact | Owner |
|---|---|---|
| Two contracts without reviewed recovery times | Evidence incomplete | Outsourcing officer |
| Resilience tests not in place for all critical functions | Gap in the testing program | Information security |
Every gap results in a measure with an owner and a deadline. The implementation status is documented on the same object as the finding.
Since the amendment, management decides for itself which partial reports are updated. This requires that every partial report can be updated independently.
| Partial report | Content | Frequency | Recipient | Status |
|---|---|---|---|---|
| Overall risk profile | Risks per category, net | quarterly | Management | |
| Operational risks | Loss events and measures | quarterly | Management | |
| ICT and outsourcing | Critical functions, incidents | quarterly | Management | |
| Stress tests | Scenarios and results | annually | Management | |
| Control effectiveness | Test results per control | semiannually | Internal audit | |
| Status of measures | Open items with deadline | monthly | Business units |
At the end, you hand over the status per topic area with the associated documents to internal audit, auditors and supervisors.
| Document | Content | As of | Owner | Status |
|---|---|---|---|---|
| Risk inventory | 142 risks with owners | 4 Sep 2026 | Risk control | |
| Control register | 318 controls linked to risks | 4 Sep 2026 | Compliance | |
| Register of information | Critical and important functions | 30 Jun 2026 | Outsourcing officer | |
| Incident documentation | ICT incidents with classification | ongoing | Information security | |
| Reports to management | Six ongoing partial reports | ongoing | Risk control | |
| Measures register | 26 open items with deadline | ongoing | Business units |
Overall responsibility, decisions on reporting scope and measures.
Inventory, assessment, stress tests, reports to management.
Controls, service provider relationships, register of information.
Review of appropriateness and effectiveness, support for external audits.
Risk management and ICT requirements refer to the same objects: processes, service providers, controls. In CRISAM®, you capture them only once.
The DORA extension is integrated into ISMS, business continuity management, risk management and audit. What DORA requires in detail is covered on its own page.
Risks, controls, compliance requirements and audits are considered together. This creates consistent views instead of parallel lists.
Internal audit derives its audit priorities from the same risk model instead of from a list of its own.
Recovery and emergency operations are the subject of business continuity management. The same plans also demonstrate operational resilience.
The two frameworks have different focuses. MaRisk governs the institution's risk management as a whole, DORA governs digital operational resilience. Since BaFin's IT circulars are being phased out, the IT requirements are set out in the regulation. What matters is therefore not which framework applies, but whether both build on the same objects.
| Criterion | MaRisk | DORA |
|---|---|---|
| Type | BaFin circular, most recently 06/2026 (BA) dated 30 Jun 2026 | Regulation of the European Union, directly applicable |
| Subject matter | Minimum requirements for risk management | Digital operational resilience for the financial sector |
| Tailoring | Principles-based, with three size classes and more leeway for small institutions | Uniform, supplemented by regulatory and implementing technical standards |
| IT and ICT | According to BaFin, the supervisory requirements for IT are essentially covered by DORA | ICT risk management, incidents, testing, third-party risk and the register of information |
| What happens to the predecessors | Remains in place and has been revised | KAIT, VAIT and ZAIT repealed, BAIT expires on 31 December 2026 |
| The end result | Risk management that internal audit, auditors and supervisors can follow | Evidence for the supervisory authority, including the register of information |
| Mapping in CRISAM® | Risks, controls, measures and reports on one platform, with an audit-proof history | Through the DORA extension, integrated into ISMS, business continuity management, risk management and audit |
Less in the frameworks themselves than at the interfaces between them. A service provider that operates a critical function is a case for the register of information and, at the same time, an operational risk. If the two are managed separately, contradictory data sets emerge, and internal audit will notice them at the latest. You can find an overview of all frameworks under Standards and frameworks.
The first step depends on where you stand today.
Then you start with the assignment. Existing data can be imported via a CSV or REST API interface. After that, every control is linked to the risk it is meant to reduce.
Then the DORA extension is the next step. The included Knowledge Pack provides over 55 building blocks and more than 700 control objectives, structured by company size and for ICT third-party service providers.
Then what matters is that every partial report can be updated independently. Dashboards and individually configurable reports can be tailored to each recipient and frequency.
For this you need the CRISAM® GRC Platform, depending on your starting point the CRISAM® IRM module or the CRISAM® ISMS module, and for the ICT side additionally the DORA Knowledge Pack. In the demo, we discuss your starting point and show which of these you already have in place.
According to BaFin, the supervisory requirements for IT are essentially covered by the EU regulation DORA. To avoid double regulation, BaFin repealed its circulars KAIT, VAIT and ZAIT as of 17 January 2025, Chapter 11 of BAIT no longer applies, and BAIT will expire completely on 31 December 2026. What remains is risk management under the Minimum Requirements for Risk Management, MaRisk for short.
The version of Circular 06/2026 (BA) dated 30 Jun 2026 applies. The amendment is more principles-based, and according to BaFin its complexity has been reduced significantly, with the length cut from 122 to around 80 pages. BaFin has published a separate circular for small and medium-sized investment firms.
According to BaFin, the amendment introduces three size classes, essentially based on total assets: very small institutions with up to one billion euros, small institutions, and the remaining less significant institutions. As an example, BaFin cites stress tests, where very small institutions could end up with five stress tests, some of them only annually instead of quarterly. For internal reporting, management decides on its own responsibility which partial reports have to be updated.
The two frameworks have different focuses. MaRisk governs the institution's risk management as a whole, DORA governs digital operational resilience. Since BaFin's IT circulars are being phased out, the IT requirements are set out in the regulation. What matters is therefore not which framework applies, but whether both build on the same objects.
It is being phased out. According to BaFin, institutions that apply Articles 5 to 15 or Article 16 of DORA have been exempt from the BAIT requirements since 17 January 2025, and Chapter 11 no longer applies. BAIT will be repealed completely as of 31 December 2026. From 1 January 2027, additional institutions must meet the requirements of the regulation.
No. BaFin repealed these three circulars as of 17 January 2025, the day from which DORA applies. According to BaFin, this is intended to avoid double regulation.
They are linked through the same objects. A service provider that operates a critical function is an entry in the register of information and, at the same time, an operational risk. In CRISAM®, risks, controls, compliance requirements and audits are considered together, and the DORA extension is integrated into ISMS, business continuity management, risk management and audit.
What matters is whether risk, control, service provider and evidence are linked in one shared model. CRISAM® assesses risks qualitatively and quantitatively in a gross and net view, manages controls with a risk link and effectiveness tests, steers measures with workflow support, responsibilities and deadlines, and documents all changes in a versioned and auditable way. For the ICT side, the DORA extension maps the requirements including the RTS and ITS documents and supports building, maintaining and exporting the register of information.
The information on the supervisory requirements on this page comes from the following publications of the Federal Financial Supervisory Authority (BaFin).
The information reflects the status of the sources listed as of the review date stated above.
In the demo, we walk through your case: risk inventory, controls linked to risks, ICT risks and service providers, measures with deadlines, and the documents for internal audit and auditors.
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